The flow
Starts it 3Model 1Logic 5Service 10
The steps in the order they run, from what starts it.
- 1Set Up Tables (run once)Manual triggerStarts it
- 2lookup_recordData Table ToolService
- 3read_call_logData Table ToolService
- 4add_noteTool WorkflowModel
- 5Every MondaySchedule triggerStarts it
- 6Create Tool Policy TableData TableService
- 7Compliance MCP ServerMcp triggerStarts it
- 8Set Audit PolicySetLogic
- 9Create Call Log TableData TableService
- 10Read The Call Log RowsData TableService
- 11Create Register TableData TableService
- 12Summarise The WeekCodeLogic
- 13Build The Allow ListCodeLogic
- 14Anything To Report?IfLogic
- 15Load Tools Into TableData TableService
- 16Post The Call AuditDiscordService
- 17Post The Quiet SummaryDiscordService
- 18Build The Demo RegisterCodeLogic
- 19Load Register Into TableData TableService
How it's built
- Starts on
- A clock
- Steps
- 19, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Discord, n8n data table
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Discord account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
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. 19 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 19 steps before you point it at anything that matters.