The flow
Starts it 1Logic 10Service 10
The steps in the order they run, from what starts it.
- 1Daily 07:00Schedule triggerStarts it
- 2SettingsSetLogic
- 3Split CampaignsSplit OutLogic
- 4Each CampaignSplit In BatchesLogic
- 5HeyReach: CampaignHttp RequestService
- 6HeyReach: Overall StatsHttp RequestService
- 7HeyReach: ConversationsHttp RequestService
- 8Wait for HeyReachMergeLogic
- 9Build Analyze RequestCodeLogic
- 10Twain: Analyze CampaignHttp RequestService
- 11Build DigestCodeLogic
- 12Slack: Analyze errorSlackService
- 13Has applyable changes?IfLogic
- 14Next campaignSetLogic
- 15Slack: Digest + approvalSlackService
- 16Worth posting?IfLogic
- 17Approved?IfLogic
- 18Slack: Digest (no changes)SlackService
- 19Twain: Apply Agent UpdateHttp RequestService
- 20Slack: Changes appliedSlackService
- 21Slack: Apply errorSlackService
How it's built
- Starts on
- A clock
- Steps
- 21, with 3 branches, 1 loop or waits
- Size
- Large: read it before trusting it with anything live
- 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?
Take your time. At 21 steps it is large: read it before trusting it with anything live.
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 21 steps before you point it at anything that matters.