The flow
Starts it 3Logic 9Service 7
The steps in the order they run, from what starts it.
- 1Daily Check 9 AMSchedule triggerStarts it
- 2Manual TriggerWebhookStarts it
- 3Error TriggerError triggerStarts it
- 4Get Overdue InvoicesHttp RequestService
- 5Format ErrorCodeLogic
- 6Has Invoices?IfLogic
- 7Slack Error AlertSlackService
- 8Process EachSplit In BatchesLogic
- 9Check Reminded TodayCodeLogic
- 10Build SummaryCodeLogic
- 11Not Reminded?IfLogic
- 12Post Daily SummarySlackService
- 13Calculate UrgencyCodeLogic
- 14Prepare EmailCodeLogic
- 15Route by UrgencySwitchLogic
- 16Slack Critical AlertSlackService
- 17Send ReminderGmailService
- 18Update Reminder CountHttp RequestService
- 19Log AttemptHttp RequestService
How it's built
- Starts on
- Another system calling it
- Steps
- 19, with 3 branches, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Gmail, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Gmail and Slack accounts. 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. 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.