The flow
Starts it 1Service 8
The steps in the order they run, from what starts it.
- 1Get Sales Tax JurisdictionsHttp Request ToolService
- 2Get Automotive Parts PoliciesHttp Request ToolService
- 3Get Producer Responsibility PoliciesHttp Request ToolService
- 4Get Hazardous Materials LabelsHttp Request ToolService
- 5Get Item Condition PoliciesHttp Request ToolService
- 6Get Listing Structure PoliciesHttp Request ToolService
- 7Get Negotiated Price PoliciesHttp Request ToolService
- 8Get Return Policy GuidelinesHttp Request ToolService
- 9Metadata MCP ServerMcp triggerStarts it
How it's built
- Starts on
- An event in a connected app
- Steps
- 9
- 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. 9 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 9 steps before you point it at anything that matters.