The flow
Starts it 1Logic 6Service 8
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2Fetch Pending OrdersHttp RequestService
- 3Fetch Customer SLA DataHttp RequestService
- 4Calculate Priority ScoresCodeLogic
- 5Check if SLA CriticalIfLogic
- 6Create Urgent Picking TaskHttp RequestService
- 7Batch Normal OrdersSplit In BatchesLogic
- 8Alert Warehouse ManagerHttp RequestService
- 9Generate Picking ScheduleCodeLogic
- 10Create Bulk Picking TasksHttp RequestService
- 11Generate Dispatch ScheduleCodeLogic
- 12Schedule Dispatches in TMSHttp RequestService
- 13Update Order StatusesHttp RequestService
- 14Generate Summary ReportCodeLogic
- 15Send Summary NotificationHttp RequestService
How it's built
- Starts on
- A clock
- Steps
- 15, with 1 branch, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- 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 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. 15 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 15 steps before you point it at anything that matters.