The flow
Starts it 1Logic 10Service 9
The steps in the order they run, from what starts it.
- 1Start WorkflowManual triggerStarts it
- 2Set API Token and Input ParametersSetLogic
- 3Get Product Details v1Http RequestService
- 4Get Product Details v4Http RequestService
- 5Get Product Details v5Http RequestService
- 6Get Product Details v9Http RequestService
- 7Get Product Comments v3Http RequestService
- 8Get Shop Product List v1Http RequestService
- 9Get Shop Product List v2Http RequestService
- 10Get Shop Product List v3Http RequestService
- 11Search Products by Keyword v1Http RequestService
- 12Output - Get Product Details v1SetLogic
- 13Output - Get Product Details v4SetLogic
- 14Output - Get Product Details v5SetLogic
- 15Output - Get Product Details v9SetLogic
- 16Output - Get Product Comments v3SetLogic
- 17Output - Get Shop Product List v1SetLogic
- 18Output - Get Shop Product List v2SetLogic
- 19Output - Get Shop Product List v3SetLogic
- 20Output - Search Products by Keyword v1SetLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 20
- 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. 20 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 20 steps before you point it at anything that matters.