The flow
Starts it 2Logic 13Service 10
The steps in the order they run, from what starts it.
- 1Flow TriggerExecute Workflow triggerStarts it
- 2Test TriggerChat triggerStarts it
- 3Delete Chat MemoryPostgresService
- 4InputSetLogic
- 5Test FieldsSetLogic
- 6If Not ZeroIfLogic
- 7Wait OutputSetLogic
- 8BookingPostgresService
- 9Reset Session 2RedisService
- 10Wait Call BackExecute WorkflowLogic
- 11If BookingIfLogic
- 12Cancel OutputSetLogic
- 13Delete Provider NumberRedisService
- 14Delete Route DataRedisService
- 15Set Open BookingPostgresService
- 16Error OutputSetLogic
- 17Call BackExecute WorkflowLogic
- 18Reset SessionRedisService
- 19Save User MemoryPostgresService
- 20Create EventGoogle CalendarService
- 21SwitchSwitchLogic
- 22Sync Booking Google CalPostgresService
- 23ChineseSetLogic
- 24JapaneseSetLogic
- 25EnglishSetLogic
How it's built
- Starts on
- Someone opening a chat with it
- Steps
- 25, with 3 branches
- Size
- Large: read it before trusting it with anything live
- Connects to
- Google Calendar, Postgres, Redis
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Google Calendar, Postgres and Redis accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on someone opening a chat with it.
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?
Take your time. At 25 steps it is large: read it before trusting it with anything live.
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 25 steps before you point it at anything that matters.