Create replay-safe client kickoff bookings with Google Calendar, Gmail and data tables

by Kuliberda Labs ✓ · 0 views · created 2026-08-26 · Support Chatbot

What this workflow does

This workflow has 53 nodes and runs when an HTTP POST request hits its webhook URL (plus 2 other triggers). Along the way it connects Google Calendar and Gmail.

How it runs

Trigger: When an HTTP POST request hits its webhook URL (plus 2 other triggers).

1. Validate Intake Token (Code): runs custom JavaScript code
2. Find Unresolved Booking Intents (Data table): get (row)
3. Select Fixture Scenario (Code): runs custom JavaScript code
4. Intake Authorized? (If): checks a condition and branches into true / false
5. Build Reconcile Candidates (Code): runs custom JavaScript code
6. Route Booking Fixture (Switch): routes items into 7 branches
7. Normalize Booking Request (Code): runs custom JavaScript code
8. Build Unauthorized Response (Code): runs custom JavaScript code
9. Provider Lookup Safe? (If): checks a condition and branches into true / false
10. Fixture Available (Code): runs custom JavaScript code

…plus 40 more steps. See the full node list below.

Services it uses

Google CalendarGmail

Before you upgrade to n8n 3.0

Nodes used (10)

• Webhookn8n-nodes-base.webhook
• Coden8n-nodes-base.code
• Ifn8n-nodes-base.if
• Respond to Webhookn8n-nodes-base.respondToWebhook
• Data tablen8n-nodes-base.dataTable
• Google Calendarn8n-nodes-base.googleCalendar
• Gmailn8n-nodes-base.gmail
• Schedule Triggern8n-nodes-base.scheduleTrigger
• Manual Triggern8n-nodes-base.manualTrigger
• Switchn8n-nodes-base.switch

From the author

Quick overview Create kickoff events only after durable intent, confirm them from Google Calendar readback, hold changed requests for review, and prepare customer communication as Gmail drafts. How it works 1. Authenticates the POST webhook with the…

View the original on n8n.io → Check your own copy