The flow
Starts it 1Logic 9Service 8
The steps in the order they run, from what starts it.
- 1New Calendly BookingCalendly triggerStarts it
- 2Wait for Calendar SyncWaitLogic
- 3Extract Booking DataSetLogic
- 4Find Matching Calendar EventGoogle CalendarService
- 5Find CRM ContactAirtableService
- 6Match Calendar EventFilterLogic
- 7Contact Found?IfLogic
- 8Keep First Calendar MatchLimitLogic
- 9Update Existing CRM ContactAirtableService
- 10Create CRM ContactAirtableService
- 11Extract Google Event IDSetLogic
- 12Prepare Meeting DataSetLogic
- 13Add Calendar AttendeesGoogle CalendarService
- 14Check for Duplicate MeetingAirtableService
- 15Meeting Already Logged?IfLogic
- 16Skip Duplicate MeetingNo OpLogic
- 17Create CRM MeetingAirtableService
- 18Notify Team in SlackSlackService
How it's built
- Starts on
- An event in a connected app
- Steps
- 18, with 2 branches, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Airtable, Google Calendar, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Airtable, Google Calendar and Slack accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 18 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Before you run itNothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 18 steps before you point it at anything that matters.