The flow
Starts it 1Logic 11Service 5
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2Define WeeksCodeLogic
- 3If4IfLogic
- 4Brand/NB PullHttp RequestService
- 5Total Metrics PullHttp RequestService
- 6Brand/NB Pull1Http RequestService
- 7Total Metrics Pull1Http RequestService
- 8Brand Filter1CodeLogic
- 9Flatten9CodeLogic
- 10Brand FilterCodeLogic
- 11Flatten8CodeLogic
- 12Merge 2 Weeks AgoMergeLogic
- 13Merge Last WeekMergeLogic
- 14Merge Time PeriodsMergeLogic
- 15Add Brand NameCodeLogic
- 16Generate Brand Performance TableCodeLogic
- 17Weekly GSC Metric EmailGmailService
How it's built
- Starts on
- A clock
- Steps
- 17, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Gmail
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Gmail 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. 17 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 17 steps before you point it at anything that matters.