The flow
Starts it 1Service 11
The steps in the order they run, from what starts it.
- 1Retrieve Item DetailsHttp Request ToolService
- 2Retrieve Item by Legacy IDHttp Request ToolService
- 3Retrieve Items in GroupHttp Request ToolService
- 4Retrieve Item by IDHttp Request ToolService
- 5Check Item CompatibilityHttp Request ToolService
- 6Search Item SummariesHttp Request ToolService
- 7Search Items by ImageHttp Request ToolService
- 8Retrieve Shopping CartHttp Request ToolService
- 9Add Item to CartHttp Request ToolService
- 10Remove Item from CartHttp Request ToolService
- 11Update Cart Item QuantityHttp Request ToolService
- 12Browse MCP ServerMcp triggerStarts it
How it's built
- Starts on
- An event in a connected app
- Steps
- 12
- 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 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?
Plan an afternoon. 12 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 12 steps before you point it at anything that matters.