The flow
Starts it 1Logic 11Service 5
The steps in the order they run, from what starts it.
- 1Hourly Campaign CheckSchedule triggerStarts it
- 2Fetch Active Campaigns DataHttp RequestService
- 3Validate Campaign DataIfLogic
- 4Campaign Fetch Error HandlerNo OpLogic
- 5Calculate Campaign MetricsCodeLogic
- 6Store Updated Campaign MetricsHttp RequestService
- 7Aggregate Campaign StatisticsAggregateLogic
- 8Identify High-Performing CampaignsIfLogic
- 9Metrics Update Error HandlerNo OpLogic
- 10Format Daily Report DataCodeLogic
- 11Retrieve Top Performing ContentHttp RequestService
- 12Send Daily Performance Report EmailEmail SendService
- 13Generate A/B Test VariationsCodeLogic
- 14Content Fetch Error HandlerNo OpLogic
- 15Email Send Error HandlerNo OpLogic
- 16Save A/B Test Content to DatabaseHttp RequestService
- 17A/B Test Storage Error HandlerNo OpLogic
How it's built
- Starts on
- A clock
- Steps
- 17, with 2 branches
- Size
- Medium: a working afternoon
- Connects to
- Email
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Email 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.