The flow
Starts it 2Model 1Logic 12Service 5
The steps in the order they run, from what starts it.
- 1Code ToolTool CodeModel
- 2WebhookWebhookStarts it
- 3MCP Server TriggerMcp triggerStarts it
- 4JS - Validate Tool CallCodeLogic
- 5IF - Tool Call Valid?IfLogic
- 6JS - Log Call (Pre-Execution)CodeLogic
- 7Respond - Invalid Tool CallNo OpLogic
- 8Switch - Route By Tool CategorySwitchLogic
- 9Switch - Route To Execution ToolSwitchLogic
- 10Slack - Request Approval (Destructive Tool)SlackService
- 11HTTP - Execute: Deploy ServiceHttp RequestService
- 12HTTP - Execute: Query Production DatabaseHttp RequestService
- 13HTTP - Execute: Search Knowledge BaseHttp RequestService
- 14HTTP - Execute: Issue RefundHttp RequestService
- 15Wait - For Approval ResponseWaitLogic
- 16JS - Merge Execution ResultCodeLogic
- 17IF - Approved?IfLogic
- 18JS - Log Call (Post-Execution)CodeLogic
- 19Respond - Approval DeniedNo OpLogic
- 20Respond - Tool Result (Success)No OpLogic
How it's built
- Starts on
- Another system calling it
- Steps
- 20, with 4 branches, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Slack 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. 20 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 20 steps before you point it at anything that matters.