Back to Catalog

Automate restaurant marketing & booking with Excel, VAPI voice agent & calendar

Oneclick AI SquadOneclick AI Squad
7653 views
2/3/2026
Official Page

This n8n template demonstrates how to create a comprehensive marketing automation and booking system that combines Excel-based lead management with voice-powered customer interactions. The system utilizes VAPI for voice communication and Excel/Google Sheets for data management, making it ideal for restaurants seeking to automate marketing campaigns and streamline booking processes through intelligent voice AI technology.

Good to know

  • Voice processing requires active VAPI subscription with per-minute billing
  • Excel operations are handled in real-time with immediate data synchronization
  • The system can handle multiple simultaneous voice calls and lead processing
  • All customer data is stored securely in Excel with proper formatting and validation
  • Marketing campaigns can be scheduled and automated based on lead data

How it works

Lead Management & Marketing Automation Workflow

  1. New Lead Trigger: Excel triggers capture new leads when customers are added to the lead management spreadsheet
  2. Lead Preparation: The system processes and formats lead data, extracting relevant details (name, phone, preferences, booking history)
  3. Campaign Loop: Automated loop processes through multiple leads for batch marketing campaigns
  4. Voice Marketing Call: VAPI initiates personalized voice calls to leads with tailored restaurant offers and booking invitations
  5. Response Tracking: All call results and lead responses are logged back to Excel for campaign analysis

Booking & Order Processing Workflow

  1. Voice Response Capture: VAPI webhook triggers when customers respond to marketing calls or make direct booking requests
  2. Response Storage: Customer responses and booking preferences are immediately saved to Excel sheets
  3. Information Extraction: System processes natural language responses to extract booking details (party size, preferred times, special requests)
  4. Calendar Integration: Booking information is automatically scheduled in restaurant management systems
  5. Confirmation Loop: Automated follow-up voice messages confirm bookings and provide additional restaurant information

Excel Sheet Structure

Lead Management Sheet

| Column | Description | |--------|-------------| | lead_id | Unique identifier for each lead | | customer_name | Customer's full name | | phone_number | Primary contact number | | email | Customer email address | | last_visit_date | Date of last restaurant visit | | preferred_cuisine | Customer's food preferences | | party_size_typical | Usual number of guests | | preferred_time_slot | Preferred dining times | | marketing_consent | Permission for marketing calls | | lead_source | How customer was acquired | | lead_status | Current status (new, contacted, converted, inactive) | | last_contact_date | Date of last marketing contact | | notes | Additional customer information | | created_at | Lead creation timestamp |

Booking Responses Sheet

| Column | Description | |--------|-------------| | response_id | Unique response identifier | | customer_name | Customer's name from call | | phone_number | Contact number used for call | | booking_requested | Whether customer wants to book | | party_size | Number of guests requested | | preferred_date | Requested booking date | | preferred_time | Requested time slot | | special_requests | Dietary restrictions or special occasions | | call_duration | Length of VAPI call | | call_outcome | Result of marketing call | | follow_up_needed | Whether additional contact is required | | booking_confirmed | Final booking confirmation status | | created_at | Response timestamp |

Campaign Tracking Sheet

| Column | Description | |--------|-------------| | campaign_id | Unique campaign identifier | | campaign_name | Descriptive campaign title | | target_audience | Lead segments targeted | | total_leads | Number of leads contacted | | successful_calls | Calls that connected | | bookings_generated | Number of bookings from campaign | | conversion_rate | Percentage of leads converted | | campaign_cost | Total VAPI usage cost | | roi | Return on investment | | start_date | Campaign launch date | | end_date | Campaign completion date | | status | Campaign status (active, completed, paused) |

How to use

  1. Setup: Import the workflow into your n8n instance and configure VAPI credentials
  2. Excel Configuration: Set up Excel/Google Sheets with the required sheet structure provided above
  3. Lead Import: Populate the Lead Management sheet with customer data from various sources
  4. Campaign Setup: Configure marketing message templates in VAPI nodes to match your restaurant's branding
  5. Testing: Test voice commands such as "I'd like to book a table for tonight" or "What are your specials?"
  6. Automation: Enable triggers to automatically process new leads and schedule marketing campaigns
  7. Monitoring: Track campaign performance through the Campaign Tracking sheet and adjust strategies accordingly

The system can handle multiple concurrent voice calls and scales with your restaurant's marketing needs.

Requirements

  • VAPI account for voice processing and natural language understanding
  • Excel/Google Sheets for storing lead, booking, and campaign data
  • n8n instance with Excel/Sheets and VAPI integrations enabled
  • Valid phone numbers for lead contact and compliance with local calling regulations

Customising this workflow

  • Multi-location Support: Adapt voice AI automation for restaurant chains with location-specific offers
  • Seasonal Campaigns: Try popular use-cases such as holiday promotions, special event marketing, or loyalty program outreach
  • Integration Options: The workflow can be extended to include CRM integration, SMS follow-ups, and social media campaign coordination
  • Advanced Analytics: Add nodes for detailed campaign performance analysis and customer segmentation

n8n Workflow: Automate Restaurant Marketing & Booking with Excel, Vapi Voice Agent & Calendar

This n8n workflow automates the process of managing restaurant bookings and marketing by integrating Google Sheets, a Vapi voice agent (via HTTP Request), and Google Calendar. It allows for real-time interaction, data management, and calendar scheduling based on customer input.

What it does

This workflow streamlines restaurant operations by:

  1. Receiving Voice Input: Listens for incoming booking requests or marketing inquiries via a webhook, likely from a Vapi voice agent.
  2. Processing Voice Data: Extracts relevant information from the voice agent's output, such as customer name, booking details, or marketing preferences.
  3. Updating Google Sheets: Records the extracted customer and booking/marketing data into a designated Google Sheet for centralized management.
  4. Creating Calendar Events: Schedules new booking events in a Google Calendar based on the confirmed details.
  5. Responding to the Voice Agent: Sends a confirmation or further instructions back to the Vapi voice agent, completing the interactive loop.
  6. Batch Processing (Optional): If multiple items are processed, it can loop through them to ensure each is handled individually.
  7. Data Transformation: Utilizes a "Set" node to structure and modify data as needed before sending it to other services.
  8. Custom Logic: Incorporates a "Code" node for executing custom JavaScript logic, allowing for flexible data manipulation or conditional processing.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance to import and execute the workflow.
  • Google Sheets Account: Configured with a spreadsheet to store customer and booking/marketing data.
    • Google Sheets Credential: An n8n Google Sheets credential (OAuth 2.0 or Service Account) with read/write access to your spreadsheet.
  • Google Calendar Account: A Google Calendar to create booking events.
    • Google Calendar Credential: An n8n Google Calendar credential (OAuth 2.0 or Service Account) with permission to create events.
  • Vapi Voice Agent (or similar API): An external service (like Vapi) that can send data to the initial Webhook and receive responses. This implies an API key or authentication might be needed for the HTTP Request node, though not explicitly defined in the provided JSON.

Setup/Usage

  1. 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.
  2. Configure Credentials:
    • Locate the "Google Sheets" and "Google Calendar" nodes.
    • Click on each node and select or create new Google credentials (OAuth2 is recommended for broader access). Ensure these credentials have the necessary permissions for Sheets (read/write) and Calendar (create events).
  3. Configure Webhook:
    • The "Webhook" node acts as the trigger. Copy its URL.
    • Configure your Vapi voice agent (or other external system) to send POST requests to this URL with the relevant customer and booking data in the request body.
  4. Configure Google Sheets Node:
    • Specify the "Spreadsheet ID" and "Sheet Name" where you want to store the data.
    • Ensure the "Operation" is set to "Append Row" or "Update Row" as per your requirement.
  5. Configure Google Calendar Node:
    • Specify the "Calendar ID" where events should be created.
    • Map the incoming data to the event fields (e.g., summary, start date, end date, attendees).
  6. Review and Activate:
    • Examine the "Edit Fields (Set)" and "Code" nodes to understand how data is transformed. Adjust the logic in the "Code" node if your incoming data structure differs or if you require custom processing.
    • Activate the workflow by toggling the "Active" switch in the top right corner of the workflow editor.

This workflow provides a robust foundation for automating restaurant interactions, from initial voice contact to structured data storage and calendar management.

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