The flow
Starts it 1Logic 9Service 3
The steps in the order they run, from what starts it.
- 1Every Morning at 8amSchedule triggerStarts it
- 2Fetch Overdue Invoices from Clio APIHttp RequestService
- 3Normalize and Triage Overdue InvoicesCodeLogic
- 4If Invoice Is Due TodayIfLogic
- 5If Escalation by Partner NeededIfLogic
- 6Skip No Invoices Due TodayNo OpLogic
- 7Build Escalation Alert for PartnerCodeLogic
- 8Build Client Invoice Reminder EmailCodeLogic
- 9Send Alert for 60+ Day Overdue InvoiceEmail SendService
- 10Execute Compliance Check WorkflowExecute WorkflowLogic
- 11If Reminder Sending ApprovedIfLogic
- 12Send Client Invoice Reminder EmailEmail SendService
- 13Skip Reminder Due to Client Opt-OutNo OpLogic
How it's built
- Starts on
- A clock
- Steps
- 13, with 3 branches
- Size
- Medium: a working afternoon
- Connects to
- Email
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Email 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. 13 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 13 steps before you point it at anything that matters.