HumationHuman + Automation
Back to Catalog

Transcribe & summarize GoHighLevel call recordings

BelenBelen
371 views
2/3/2026
GitLabTeamsWebhookAutomationRepository
Official Page

This n8n template automatically transcribes GoHighLevel (GHL) call recordings and creates an AI-generated summary that is added as a note directly to the related contact in your GHL CRM.

It’s designed for real estate investors, agencies, and sales teams that handle a large volume of client calls and want to keep detailed, searchable notes without spending hours on manual transcription.

Who’s it for

  • Sales and acquisitions teams that want instant call notes in their CRM
  • Real estate wholesalers or agencies using GoHighLevel for deal flow
  • Support and QA teams that need summarized transcripts for review
  • Any business owner who wants to automatically document client conversations

How it works

  1. A HighLevel automation workflow triggers when a call is marked “Completed” and automatically sends a webhook to n8n.
  2. The n8n workflow receives this webhook and waits briefly to ensure the call recording is ready.
  3. It retrieves the conversation and message IDs from the webhook payload.
  4. The call recording is fetched from GHL’s API.
  5. An AI transcription node converts the audio to text.
  6. A summarization node condenses the transcript into bullet points or a concise paragraph.
  7. A Code node formats the AI output into proper JSON for GHL’s “Create Note” endpoint.
  8. Finally, an HTTP Request node posts the summary to the contact’s record in GHL.

How to set up

  1. Add your GoHighLevel OAuth credential and connect your agency account.
  2. Add your AI credential (e.g., OpenAI, Anthropic, or Gemini).
  3. Replace the sample webhook URL with your n8n endpoint.
  4. Test with a recent call and confirm the summary appears in the contact timeline.

Requirements

  • GoHighLevel account with API and OAuth access
  • AI service for transcription and summarization (e.g., OpenAI Whisper + GPT)

Customizing this workflow

You can tailor this automation for your specific team or workflow:

  • Add sentiment analysis or keyword extraction to the summary.
  • Change the AI prompt to focus on “action items,” “objections,” or “next steps.”
  • Send summaries to Slack, Notion, or Google Sheets for reporting.
  • Trigger follow-up tasks automatically in your CRM based on keywords.

Good to know

  • AI transcription and summarization costs vary by provider — check your LLM’s pricing.
  • GoHighLevel’s recording availability may take up to 1 minute after the call ends; adjust the delay accordingly.
  • For OAuth setup help, refer to GHL’s OAuth documentation.

Happy automating! ⚙️

n8n Workflow: Transcribe and Summarize GoHighLevel Call Recordings

This n8n workflow provides a robust solution for automating the transcription and summarization of call recordings, likely originating from a platform like GoHighLevel. It acts as an API endpoint, receiving call recording data, processing it through OpenAI for transcription and summarization, and then outputting the results.

What it does

This workflow automates the following steps:

  1. Receives Call Recording Data: It starts by listening for incoming HTTP POST requests at a defined webhook URL, expecting a JSON payload containing information about a call recording, including its URL.
  2. Extracts Recording URL: It processes the incoming data to extract the recordingUrl from the payload.
  3. Transcribes Audio: It sends the recordingUrl to OpenAI's Whisper model to transcribe the audio into text.
  4. Summarizes Transcription: It then takes the full transcription and sends it to OpenAI's GPT model to generate a concise summary.
  5. Outputs Results: The workflow concludes by returning the original input data along with the generated transcription and summary as a JSON response.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance (cloud or self-hosted).
  • OpenAI API Key: An API key for OpenAI with access to the Whisper (for transcription) and GPT (for summarization) models. This key needs to be configured as an n8n credential.
  • GoHighLevel (or similar platform): A platform that can send call recording data (e.g., via a webhook) to an external URL. The workflow expects a recordingUrl field in the incoming JSON payload.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON file for this workflow.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the "Import from JSON" button and paste the workflow JSON or upload the file.
  2. Configure Credentials:
    • Locate the "OpenAI" node.
    • Click on the "Credential" field and select your existing OpenAI API Key credential, or create a new one if you haven't already.
  3. Activate the Webhook:
    • Locate the "Webhook" node.
    • Copy the "Webhook URL" displayed in the node's settings.
    • Activate the workflow by toggling the "Active" switch in the top right corner of the n8n editor.
  4. Configure External System:
    • In your GoHighLevel (or other call recording platform), set up a webhook that triggers when a call recording is available.
    • Configure this webhook to send a POST request to the n8n Webhook URL you copied in the previous step.
    • Ensure the payload sent by your external system includes a field named recordingUrl containing the direct URL to the audio file.
  5. Test the Workflow:
    • Make a test call or trigger a recording event in your external system.
    • Observe the execution in n8n to ensure it runs successfully and processes the recording.

This workflow provides a powerful foundation for integrating AI-driven transcription and summarization into your call management processes.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247