The flow
Starts it 2Logic 9Service 7
The steps in the order they run, from what starts it.
- 1Handle Incoming MessageWebhookStarts it
- 2Handle Control RequestWebhookStarts it
- 3Normalize Message InputCodeLogic
- 4Normalize Command InputCodeLogic
- 5Configure Session ParametersCodeLogic
- 6Route by Request TypeSwitchLogic
- 7Fetch Latest SessionData TableService
- 8Fetch Session for ControlData TableService
- 9Evaluate Session StateCodeLogic
- 10Execute Session CommandCodeLogic
- 11Route by Session StatusSwitchLogic
- 12Modify Session StateData TableService
- 13Create New Session RecordData TableService
- 14Log Activity UpdateData TableService
- 15Expire Old SessionData TableService
- 16Restore to Active SessionData TableService
- 17Build Session ContextCodeLogic
- 18Generate Control ResultCodeLogic
How it's built
- Starts on
- Another system calling it
- Steps
- 18, with 2 branches
- Size
- Medium: a working afternoon
- Connects to
- n8n data table
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on another system calling 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?
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.
Nothing 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.