The flow
Starts it 1Logic 6Service 7
The steps in the order they run, from what starts it.
- 1Daily Trigger - 6 AMSchedule triggerStarts it
- 2Get Product FeedHttp RequestService
- 3Data Quality ChecksCodeLogic
- 4Split Products1Item ListsLogic
- 5Optimize TitleHttp RequestService
- 6Generate DescriptionHttp RequestService
- 7Assign Custom LabelsCodeLogic
- 8Aggregate ProductsAggregateLogic
- 9Upload to Merchant Center (Content API v2.1)Http RequestService
- 10Check Product Status (NEW API)Http RequestService
- 11Analyze Product IssuesCodeLogic
- 12IF Disapprovals FoundIfLogic
- 13Alert - DisapprovalsSlackService
- 14Success SummarySlackService
How it's built
- Starts on
- A clock
- Steps
- 14, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Slack account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
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.