Agent setup guide
Newsletter Growth Report
Every Monday in Slack: your Mailchimp audience size and change, the week's sends, opens and clicks added up in code, and one suggestion.
What it does
Every Monday in Slack: your Mailchimp audience size and change, the week's sends, opens and clicks added up in code, and one suggestion.
- Every Monday, reads your audience's newest sent Mailchimp campaigns and keeps the ones sent in the last 7 days, in code.
- Works out in code each campaign's open and click rate (from Mailchimp's rates) and the week's emails sent, unique opens and unique clicks.
- Compares your audience size (as Mailchimp reports it on your newest campaign) with the last report's, in code.
- AI writes a one-line headline, names the campaign with the best open rate and suggests one thing to try, without restating the numbers.
- Posts the report to your Slack channel.
What it needs
- A paid plan (agents run live on paid plans).
- An AI provider key (Settings → AI Providers).
- Mailchimp and Slack, connected in Settings → Integrations.
What it doesn't do
- Mailchimp only: Kit and beehiiv stats aren't read by our connections.
- New subscribers and unsubscribes aren't shown separately: only the net change in audience size between reports (the first report has nothing to compare with).
- It reads the 20 newest sent campaigns; it doesn't read automations or per-link clicks.
- Numbers are exactly what Mailchimp reports; it doesn't send or change anything.
Availability and plans
Available
Its workflow is built and tested, and every app it needs is live. You can get it and set it up now.
Included free on the Enterprise plan; on other paid plans it's a one-time purchase per workspace (the price is on the Agents page). The Agents page in the app always shows its current status.
Before you start
- A paid plan: agents run live, and the Free plan only runs Dry Runs.
- An AI provider key (OpenAI, Anthropic, Google and more) in Settings → AI Providers. AI usage is billed by your provider.
- These apps, connected in Settings → Integrations: Mailchimp and Slack.
- Nothing to send: the agent runs on a schedule.
- About 10 minutes.
Set it up step by step
Get the agent first (buy it, or it's already yours when your plan includes it), then in Agents → My agents press “Set up this agent”. That creates the agent's workflow in your workspace (it counts towards your plan's workflow limit) and opens the canvas with a setup checklist above it. Each item links to the exact place to go and ticks itself off when it's done.
1. Connect your AI provider
The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.
2. Connect Mailchimp
Connect Mailchimp with an API key (Settings → Integrations → Mailchimp).
3. Connect Slack
Connect the Slack workspace for the report (Settings → Integrations → Slack).
4. Pick your audience
Open “Read your sent campaigns” and pick the account and your audience id.
| Setting | What to enter | In step |
|---|---|---|
| Mailchimp account | The Mailchimp account with your newsletter. Pick your connected Mailchimp account. | “Read your sent campaigns” |
| Mailchimp audience id | Your newsletter's audience id (Audience → Settings → Audience name and defaults → Audience ID), so the size is always the same audience's. | “Read your sent campaigns” |
5. Describe your newsletter
Open “One suggestion” and replace the placeholder.
| Setting | What to enter | In step |
|---|---|---|
| Your newsletter | Replace the placeholder with your newsletter, its readers, how often you send and what you want to improve. It starts as “[YOUR NEWSLETTER, WHO IT'S FOR, HOW OFTEN YOU SEND AND WHAT YOU'RE TRYING TO IMPROVE (OPENS, CLICKS, GROWTH)]” until you replace it. | “One suggestion” |
6. Pick the Slack channel
Open “Post the report” and pick the workspace and channel.
| Setting | What to enter | In step |
|---|---|---|
| Slack account | The Slack workspace for the report. Pick your connected Slack account. | “Post the report” |
| Slack channel | Where the weekly report goes, e.g. #marketing. | “Post the report” |
7. Test it with Dry Run
Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
8. Switch the trigger on
Open the trigger, set your time zone and switch the schedule on. It runs every Monday at 8:00.
How it works
The agent is a normal workflow with 13 steps (1 AI step). You can open, edit and monitor it like any other workflow.
- Mondays at 8:00 — Runs on a schedule (cron 0 8 * * 1, UTC — change it in the trigger's settings). Runs every Monday morning and covers the campaigns sent in the last 7 days. Set your time zone on the trigger.
- Read your sent campaigns — Mailchimp: List campaigns. Lists your audience's 20 newest sent Mailchimp campaigns with what Mailchimp reports for each: emails sent, opens, clicks, rates and the audience size.
- Keep the last 7 days — Step. In code, not AI: keeps the campaigns sent in the last 7 days (today included, in your time zone).
- Add up the week — Step. In code, not AI: open and click rates per campaign (from Mailchimp's own rates), and the week's emails sent, unique opens and unique clicks with the overall rates.
- Last week's audience size — Recalls what it remembered earlier (memory “newsletter-growth-report”). Reads the audience size remembered from the last report.
- Remember this week's audience size — Remembers it for later runs (memory “newsletter-growth-report”, kept 60 days). Stores the audience size Mailchimp reports on your newest sent campaign, next to last week's (kept 60 days).
- Audience change — Step. In code, not AI: this week's audience size minus last report's.
- Each campaign this week — Repeats the steps below for each item (up to 20 per run). Lists this week's campaigns with their numbers (up to 20).
- [For each item — “Each campaign this week”] Listed — Kept in the run history. Nothing is changed in Mailchimp.
- List the campaigns — Step. In code: one line per campaign with Mailchimp's numbers.
- One suggestion — AI step (runs on your AI provider key). AI reads the week's numbers (computed in code) and writes a one-line headline and one concrete suggestion, without restating the numbers.
- Post the report — Slack: Post a message. Posts the numbers (from code) and the suggestion to your Slack channel.
- Report posted — Kept in the run history. The run history keeps every report.
Test it with Dry Run
Press Dry Run in the canvas. The agent runs on the sample data stored on its trigger (the “Sample data for Dry Run” box), so you can check every step's output before anything is live.
- Nothing is sent or written: app actions, emails and Slack posts are simulated, and AI steps don't call your AI provider.
- For-each loops repeat only the first 3 items.
- Memory steps don't read or write stored memory: a recall finds nothing, and a save only shows what it would store.
Go live
- Open the trigger, set your time zone and switch the schedule on. It runs every Monday at 8:00.
- Scheduled runs start only once the schedule is activated, and can't repeat faster than your plan's minimum interval.
- The setup checklist adds a “paid plan” item before activation: live runs need a paid plan (the Free plan only runs Dry Runs).
- When every checklist item is done and the trigger is on, the checklist says “Live — this agent is running”. Follow its runs in the workflow's History tab and in Analytics → Agents.
Questions
Does it show new subscribers and unsubscribes?
Not separately: our Mailchimp connection doesn't read those counts. It shows your audience size as Mailchimp reports it on your newest campaign and the net change since the last report, worked out in code.
What about Kit or beehiiv?
This report is for Mailchimp: our Kit and beehiiv connections can list broadcasts and posts but don't read their opens or clicks.
Can the AI get the numbers wrong?
The AI doesn't handle the numbers: they come from Mailchimp and are added up in code, and the AI is told not to restate them. It only writes the headline and the suggestion.
Troubleshooting
- “No AI provider connected” or a rejected key: connect or fix the key in Settings → AI Providers, then press Test there.
- A checklist item stays unticked: the setting is still empty or still contains its placeholder text. Open the step from the checklist and fill it in.
- An app step fails with “Needs reconnect”: the account's access was revoked or expired. Reconnect it in Settings → Integrations.
- Slack says the app isn't in the channel: in Slack, type /invite @Fluxo Flow in that channel (always needed for private channels).
- It didn't run at the expected time: the schedule must be activated, and its time is in the trigger's timezone.
- A step failed: open the run in History and check that step in the Trace tab for the error and what it received.
Generated from the agent's own workflow, so it always matches what the agent does. Last updated .