The flow
Starts it 1Logic 16Service 5
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2Load active shipmentsData TableService
- 3Active onlyFilterLogic
- 4Switch by carrierSwitchLogic
- 5FEDEX · Check BreakerCodeLogic
- 6UPS · Check BreakerCodeLogic
- 7DHL · Check BreakerCodeLogic
- 8Unknown carrierSetLogic
- 9FEDEX · IF allowedIfLogic
- 10UPS · IF allowedIfLogic
- 11DHL · IF allowedIfLogic
- 12MergeMergeLogic
- 13FEDEX · Track APIHttp RequestService
- 14FEDEX · SkippedSetLogic
- 15UPS · Track APIHttp RequestService
- 16UPS · SkippedSetLogic
- 17DHL · Track APIHttp RequestService
- 18DHL · SkippedSetLogic
- 19Persist → Data Table (upsert)Data TableService
- 20FEDEX · Normalize + BreakerCodeLogic
- 21UPS · Normalize + BreakerCodeLogic
- 22DHL · Normalize + BreakerCodeLogic
How it's built
- Starts on
- A clock
- Steps
- 22, with 4 branches
- Size
- Large: read it before trusting it with anything live
- Connects to
- n8n data table
- 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?
Take your time. At 22 steps it is large: read it before trusting it with anything live.
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 22 steps before you point it at anything that matters.