Back to Catalog

Automate AI phone booking & CRM updates with GPT-4, VAPI.ai, and GHL

Sam YassineSam Yassine
1529 views
2/3/2026
Official Page

Automate AI-driven appointment booking with phone call confirmations, real-time lead validation, CRM updates, and email notifications—powered by n8n, OpenAI, VAPI.ai, and GoHighLevel.

Tools & Services Used

  • GoHighLevel (CRM & appointment management)

  • VAPI.ai (AI phone calls)

  • OpenAI (GPT-4 for lead validation and post-call analysis)

  • Email Service (transactional email notifications)

  • n8n (Self-hosted required for Community Nodes)

Workflow Overview

This automation performs the following steps:

  • Trigger: A new lead arrives via the GHL Webhook.

  • Validation: OpenAI (GPT-4) checks lead quality and relevance.

  • AI Phone Call: VAPI.ai initiates an automated call to confirm appointment details.

  • Post-Call Analysis: OpenAI interprets the call result (booking_made=YES/NO).

Conditional Actions:

If YES: Updates GoHighLevel CRM and sends confirmation emails to the client and owner.

If NO: Alerts the owner via email about the failed booking.

Prerequisites

Active accounts and API keys for:

  • GoHighLevel (webhook setup)
  • VAPI.ai (phone call API)
  • OpenAI (GPT-4 access)
  • Email service (e.g., SMTP, SendGrid, or Gmail)

How to Use This Template

Step 1: Import the Template

Import the JSON into your self-hosted n8n instance (requires Community Nodes like @n8n/n8n-nodes-langchain).

Step 2: Configure Credentials

GHL Webhook: Replace YOUR_WEBHOOK_ID with your GoHighLevel webhook ID.

OpenAI Nodes: Add your OpenAI API key (replace placeholder BxLbA94QZt0ifZsC).

VAPI Call Node: Ensure the VAPI.ai endpoint (https://api.vapi.ai/call/phone) has valid API credentials.

Email Nodes: Configure SMTP or API credentials for your email service.

Step 3: Enable Disabled Nodes

Activate the Post-call Analysis node if needed (disabled by default).

Finding Your GHL Webhook ID In GoHighLevel, navigate to Automations → Webhooks.

Create a new webhook and copy its unique ID into the GHL Webhook node.

Initial Test Run

Simulate a Lead: Manually trigger the GHL webhook with test lead data.

Debugging:

Verify OpenAI validates the lead.

Check if VAPI.ai initiates a call (use a test phone number).

Confirm CRM updates and emails are sent conditionally.

Production Prep:

Enable error-handling loops for failed calls.

Adjust GPT-4 prompts for stricter validation.

Use Cases

  • Medical Clinics: Reduce no-shows with automated appointment confirmations.

  • Salons/Spas: Streamline booking updates and client reminders.

  • Consultants: Sync client meetings to CRM in real time.

Disclaimer

Requires self-hosted n8n (Community Nodes are unsupported on n8n Cloud).

Test phone call and email nodes extensively before scaling.

Automate AI Phone Booking & CRM Updates with GPT-4, VAPI.AI, and GHL

This n8n workflow automates the process of handling incoming phone calls, leveraging AI to understand the conversation, determining if a booking is needed, and updating a CRM system accordingly. It integrates VAPI.AI for call transcription and AI interaction, GPT-4 (via OpenAI) for sophisticated decision-making, and GHL (GoHighLevel) for CRM updates.

What it does

This workflow streamlines your customer interaction and CRM management by:

  1. Receiving Call Data: It starts by listening for incoming call data via a webhook, likely from a VAPI.AI integration or a similar call handling service.
  2. AI-Powered Conversation Analysis: It uses an AI Agent powered by an OpenAI Chat Model (GPT-4) and a Simple Memory to analyze the call transcript. This agent is configured to understand the conversation context and determine if a booking is required.
  3. Conditional Logic for Booking: It employs an 'If' node to check the AI Agent's output. If the AI determines that a booking is needed, the workflow proceeds down the 'True' branch.
  4. Booking and CRM Update (Conditional):
    • If Booking Needed: It makes an HTTP Request to an external API (likely GHL or a booking system) to create or update a booking.
    • If No Booking Needed: It sends an email, potentially as a notification or a follow-up, indicating that no booking was made.
  5. General CRM Update: Regardless of whether a booking was made, it performs another HTTP Request to update the CRM, ensuring the call details and AI analysis are logged.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Webhook Endpoint: An external system (e.g., VAPI.AI) configured to send call data to the n8n webhook.
  • OpenAI API Key: For the OpenAI Chat Model (GPT-4) and OpenAI nodes.
  • VAPI.AI Account (Implied): Based on the directory name, VAPI.AI is likely used to provide the call data to the webhook.
  • GoHighLevel (GHL) Account (Implied): Based on the directory name, GHL is likely the CRM being updated via HTTP requests. You'll need API access and relevant endpoints.
  • SMTP Credentials: For the "Send Email" node, if the 'False' branch of the 'If' node is utilized.

Setup/Usage

  1. Import the Workflow: Download the JSON provided and import it into your n8n instance.
  2. Configure Webhook:
    • Activate the "Webhook" node and copy its URL.
    • Configure your external call handling system (e.g., VAPI.AI) to send call data (transcripts, caller info, etc.) to this URL.
  3. Configure Credentials:
    • OpenAI: Set up your OpenAI API credentials in n8n for the "OpenAI Chat Model" and "OpenAI" nodes.
    • HTTP Request (CRM/Booking): Update the "HTTP Request" nodes with the correct API endpoints, authentication (e.g., API keys, tokens), and payload structure for your CRM (GHL) and/or booking system.
    • Send Email: If you plan to use the email notification, configure your SMTP credentials for the "Send Email" node.
  4. Customize AI Agent:
    • Review the "AI Agent" node's prompt and tool definitions to ensure it accurately understands your booking criteria and interaction logic.
    • Adjust the "Simple Memory" settings if needed for conversational context.
  5. Adjust 'If' Logic:
    • Modify the conditions in the "If" node to precisely match how you want to interpret the AI Agent's output for booking decisions.
  6. Activate Workflow: Once all configurations are complete, activate the workflow.

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