The flow
Starts it 1Service 6
The steps in the order they run, from what starts it.
- 1Create Shipment from QuoteHttp Request ToolService
- 2Retrieve Shipment DetailsHttp Request ToolService
- 3Cancel ShipmentHttp Request ToolService
- 4Download Shipping LabelHttp Request ToolService
- 5Generate Shipping QuoteHttp Request ToolService
- 6Retrieve Shipping QuoteHttp Request ToolService
- 7Logistics MCP ServerMcp triggerStarts it
How it's built
- Starts on
- An event in a connected app
- Steps
- 7
- Size
- Small: readable in one sitting
- 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 an event in a connected app.
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?
Not long. At 7 steps it can be read in one sitting and changed without fear.
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.
Before you run itNothing 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 7 steps before you point it at anything that matters.