The flow
Starts it 1Model 2Logic 8Service 4
The steps in the order they run, from what starts it.
- 1Schedule - Poll Active ShipmentsSchedule triggerStarts it
- 2Anthropic - Risk Classification ModelLm Chat AnthropicModel
- 3Fetch Active Shipments & Route HistoryHttp RequestService
- 4Fetch Live IoT Sensor ReadingsHttp RequestService
- 5AI - Generate Batch Risk ClassificationAgentModel
- 6Merge - Combine Shipment & Sensor DataMergeLogic
- 7JS - Parse AI Output & Format Predictive Recall ReportCodeLogic
- 8JS - Build Cold-Chain Excursion ProfileCodeLogic
- 9Wait For Rate LimitWaitLogic
- 10JS - Run Spoilage Risk Monte CarloCodeLogic
- 11IF - High Risk Batch?IfLogic
- 12Wait For Simulation BufferWaitLogic
- 13Send Urgent Recall Alert EmailEmail SendService
- 14Wait For ResultWaitLogic
- 15Send Batch Risk Report EmailEmail SendService
How it's built
- Starts on
- A clock
- Steps
- 15, with 1 branch, 3 loops or waits
- Size
- Medium: a working afternoon
- Connects to
- Email
- Model
- Claude
Questions
What does it need to run?
An n8n account, plus your own Email account, and a key for Claude. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
Yes. It calls Claude. Model calls are billed by the provider, not by n8n.
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.