The flow
Starts it 1Service 15
The steps in the order they run, from what starts it.
- 1Search OrdersHttp Request ToolService
- 2Retrieve Order DetailsHttp Request ToolService
- 3Issue Order RefundHttp Request ToolService
- 4List Order FulfillmentsHttp Request ToolService
- 5Create Shipping FulfillmentHttp Request ToolService
- 6Retrieve Fulfillment DetailsHttp Request ToolService
- 7Retrieve Dispute DetailsHttp Request ToolService
- 8Accept Payment DisputeHttp Request ToolService
- 9Retrieve Dispute ActivityHttp Request ToolService
- 10Add Dispute EvidenceHttp Request ToolService
- 11Contest Payment DisputeHttp Request ToolService
- 12Retrieve Evidence FileHttp Request ToolService
- 13Update Dispute EvidenceHttp Request ToolService
- 14Upload Evidence FileHttp Request ToolService
- 15Search Payment DisputesHttp Request ToolService
- 16Fulfillment MCP ServerMcp triggerStarts it
How it's built
- Starts on
- An event in a connected app
- Steps
- 16
- 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. 16 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.
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 16 steps before you point it at anything that matters.