Automate call scheduling with Voice AI receptionist using Vapi, Google Calendar & Airtable
Who is this template for?
This template is ideal for small businesses, agencies, and solo professionals who want to automate appointment scheduling and caller follow-up through a voice-based AI receptionist. If you’re using tools like Google Calendar, Airtable, and Vapi (Twilio), this setup is for you.
What problem does this workflow solve?
Manual call handling, appointment booking, and email coordination can be time-consuming and prone to errors. This workflow solves that by automating the receptionist role: answering calls, checking calendar availability, managing appointments, and storing call summaries—all without human intervention.
What this workflow does
This Agent Receptionist manages inbound voice calls and scheduling tasks using Vapi and Google Calendar. It checks availability, books or updates calendar events, sends email confirmations, and logs call details into Airtable. The workflow includes built-in logic for slot management, email triggers, and storing call transcripts.
Setup Instructions
Duplicate Airtable Base: Use this Airtable base templateBASE LINK
Import Workflow: Load provided JSON into your n8n instance.
Credentials: Connect your Google Calendar and Airtable credentials in n8n.
Activate Workflow: Enable workflow to get live webhook URLs.
Vapi Configuration:
Paste provided system prompt into Vapi Assistant.
Link the appropriate webhook URLs from n8n (GetSlots, BookSlots, UpdateSlots, CancelSlots, and end-of-call report).
Disclaimer
Optimized for cloud-hosted n8n instances. Self-hosted users should verify webhook and credential setups.
Automate Call Scheduling with Voice AI Receptionist using Vapi, Google Calendar & Airtable
This n8n workflow automates the process of scheduling calls with a Voice AI Receptionist (likely Vapi, though not explicitly in the JSON) and managing these appointments in Google Calendar and Airtable. It acts as a backend for a voice AI system, handling the data received from a call and integrating it with your scheduling and CRM tools.
What it does
This workflow streamlines the appointment scheduling process by:
- Receiving Call Data: Listens for incoming POST requests, likely from a Voice AI platform (e.g., Vapi) after a call is completed. This webhook is expected to contain details about the call and the user's intent.
- Extracting and Formatting Data: Processes the received data to extract relevant information for scheduling, such as the event title, start and end times, and attendee email. It uses a "Set" node to structure this data for subsequent steps.
- Conditional Logic for Scheduling: Checks if an
attendeeEmailis present in the received data.- If an email is present:
- Creates a Google Calendar Event: Schedules a new event in Google Calendar with the extracted details, including the attendee.
- Adds Record to Airtable: Creates a new record in a specified Airtable base and table, storing the call details and the newly created Google Calendar event ID.
- If no email is present:
- Responds to Webhook: Sends a response back to the originating webhook, indicating that no email was provided and therefore no event was scheduled. This allows the Voice AI to potentially prompt the user for an email or handle the scenario appropriately.
- If an email is present:
- Responds to Webhook: After processing (either scheduling or noting the absence of an email), sends a final response back to the initial webhook, indicating the outcome of the operation.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Webhook URL: A configured webhook endpoint from your Voice AI platform (e.g., Vapi) that can send POST requests to the n8n Webhook trigger.
- Google Calendar Account: A Google account with access to Google Calendar.
- Google Calendar Credentials: Configured Google OAuth2 credentials in n8n for the Google Calendar node.
- Airtable Account: An Airtable account.
- Airtable Base and Table: A specific Airtable Base and Table where call scheduling records will be stored.
- Airtable Credentials: Configured Airtable API Key credentials in n8n.
Setup/Usage
- Import the Workflow:
- Copy the provided JSON code.
- In your n8n instance, go to "Workflows" and click "New".
- Click the "Import from JSON" button and paste the workflow JSON.
- Configure Credentials:
- Google Calendar:
- Locate the "Google Calendar" node.
- Click on the "Credential" field and select an existing Google OAuth2 credential or create a new one. Follow the n8n documentation for setting up Google OAuth2 credentials if needed.
- Airtable:
- Locate the "Airtable" node.
- Click on the "Credential" field and select an existing Airtable API Key credential or create a new one.
- Google Calendar:
- Configure Nodes:
- Webhook: The "Webhook" node is pre-configured to listen for POST requests. Copy the "Webhook URL" displayed in the node settings after activating the workflow and configure your Voice AI platform to send data to this URL.
- Edit Fields (Set): This node is responsible for parsing and formatting the incoming data. Review its configuration to ensure it correctly extracts
eventName,startTime,endTime, andattendeeEmailfrom your Voice AI's payload. Adjust the expressions if your incoming data structure differs. - Google Calendar:
- Ensure the "Calendar ID" is set to the desired calendar where events should be created (e.g.,
primaryfor your main calendar). - Verify that the expressions for "Event Name", "Start Date & Time", "End Date & Time", and "Attendees" correctly map to the output of the "Edit Fields" node.
- Ensure the "Calendar ID" is set to the desired calendar where events should be created (e.g.,
- Airtable:
- Enter your "Base ID" and "Table Name".
- Map the fields in the "Airtable" node to the corresponding columns in your Airtable table (e.g.,
Event Name,Start Time,End Time,Attendee Email,Google Calendar Event ID).
- Respond to Webhook: Review the response body to ensure it provides useful feedback to your Voice AI platform.
- Activate the Workflow: Once all credentials and nodes are configured, activate the workflow by toggling the "Active" switch in the top right corner of the n8n editor.
This workflow provides a robust foundation for integrating a Voice AI receptionist with your scheduling and CRM systems, ensuring that appointments are automatically logged and managed.
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.
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
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