The flow
Starts it 1Logic 8Service 5
The steps in the order they run, from what starts it.
- 1When clicking ‘Execute workflow’Manual triggerStarts it
- 2Configure store settingsSetLogic
- 3Fetch publication channelsHttp RequestService
- 4Fetch Lightspeed categoriesHttp RequestService
- 5Split categories into itemsSplit OutLogic
- 6Filter visible categoriesIfLogic
- 7Process each categorySplit In BatchesLogic
- 8Create Shopify collectionHttp RequestService
- 9Verify collection createdIfLogic
- 10Create URL redirectHttp RequestService
- 11Error: Migration step failedStop And ErrorLogic
- 12Verify redirect createdIfLogic
- 13Publish collection to channelsHttp RequestService
- 14Verify publish successIfLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 14, with 4 branches, 1 loop or waits
- 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. 14 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 14 steps before you point it at anything that matters.