Newsletter list health
By Toolspoke
Monthly check of your Mailchimp audiences for unsubscribes, cleaned addresses and bounce spikes, posted to Slack with last month's sends.
Needs a Toolspoke account. You choose which project it installs into.
- Mailchimp + Slack
- Required integrations
- Runs on a schedule
- First Monday of each month at 9am by default
- Post one message
- What its last step does
- Some actions can delete
- 1 of 31 actions in its tools
On this page
The short version
- What it is
- A ready-made Toolspoke agent that tells you once a month how healthy your Mailchimp list is.
- What it reads
- Audience sizes, last month's unsubscribed and cleaned counts, and the reports for the last three months of sends.
- Where it posts
- One Slack channel, one section per audience.
- What it flags
- List decay, sends with a bounce rate above 2% or twice the usual, abuse complaints and falling open or click rates.
- How often
- The first Monday of each month at 9am once you switch it on.
- What it never does
- Add, remove, unsubscribe or change a contact, or post anyone's email address.
- What you need
- A Toolspoke account, a Mailchimp API key and a Slack workspace.
What Newsletter list health will never do
Newsletter list health is told never to add, remove or change a contact, and never to post anyone's address. With read access to Mailchimp it cannot change a contact at all.
Newsletter list health will never
- Add, update, unsubscribe, archive or clean a contact, or change a tag or merge field.
- Post an email address or any person's name.
- Send, schedule or edit a campaign.
- Post to anyone directly, or edit an earlier post.
Why it does not clean the list
Unsubscribing or removing people is a decision about consent and about your audience. Mailchimp already cleans hard bounces itself. Anything more is yours to decide.
Why it posts counts, not people
A Slack channel is not the place for subscribers' addresses. Every figure in the summary is a count or a rate.
Why it never sends
The Mailchimp connector cannot send, schedule or delete a campaign, so the agent cannot either. That is a property of the connector.
These are written into Newsletter list health's instructions. They guide the agent, but they are not a permission. What it is allowed to touch is set by the access you grant.
Newsletter list health reads your list and your reports. Every change to who gets your email stays with you.
What Newsletter list health does
Newsletter list health is an AI agent that reads your Mailchimp audiences and last month's campaign reports on the first Monday of each month and posts one summary to Slack: how much of the list was lost, whether bounces jumped and how engagement moved.
Lists decay slowly enough that nobody notices. A few hundred people unsubscribe, a few hundred addresses bounce and are cleaned, and one send to an old segment drives bounces up for everything after it.
Each campaign report shows its own numbers. None of them shows the month.
Newsletter list health puts the month together. It reads each audience's size and the people who left it, the bounce and complaint rate of every send, and the open and click rates against the two months before and the industry average Mailchimp gives.
In practice, on the first Monday of each month you get:
- How much of each audience unsubscribed or was cleaned last month
- Any send whose bounce rate spiked, with its date and segment
- Any send that drew abuse complaints
- Open and click rates against the months before and the industry
How it works
Newsletter list health works in four steps each month: it reads each audience, counts who left, reads the sends and posts one summary. All of it comes from the agent's written instructions, which you can read and edit after you install it.
Step 1: Read each audience
It takes the size and counts from the audience's own stats.
Step 2: Count who left
It counts last month's unsubscribed and cleaned contacts, as numbers only.
Step 3: Read the sends
It reads every report from the last three months for bounces, complaints and engagement.
Step 4: Post the summary
It posts one message, spikes and complaints first.
It counts, it does not list people
It reads get_audience for each audience's size and counts. For last month's movement it calls list_members with a status and a date and a limit of one, and reads the total. It needs the number, never the addresses.
It reads each send's report
It finds the last three months of sends with list_campaigns and reads each with get_campaign_report: emails sent, opens, clicks, hard and soft bounces, unsubscribes, abuse reports and the industry averages.
It uses your threshold
A bounce spike is a send above 2% of emails sent, or twice the previous two months' average, unless you choose another level. Any default it used is named in the post.
It reports and stops
It never cleans the list or unsubscribes anyone. Deciding what to do about a segment is yours. The limits are under what it will never do.
What a monthly summary looks like
A message from Newsletter list health is one Slack post per month, one section per audience, with the problems first.
Fieldnote
Channels
- # newsletter
- # marketing
- # growth
- # general
# newsletter
October, against August and September. 1 audience, 6 sends read. Bounce spike means over 2%, the default.
Spikes and complaints
- Autumn offer, lapsed customers, sent 21 October. Bounces 4.8% of 9,800 sent (412 hard). 3 abuse reports.
Fieldnote readers, 32,400 contacts
- Decay: 388 unsubscribed and 224 cleaned last month, 1.9% of the list. August and September averaged 1.1%.
- Engagement: opens 38.6%, clicks 4.4%. Steady on the two months before, above the industry average of 31% and 2.9%.
The sends
Weekly letters #139 to #142, a product update and the autumn offer. All reports read.
- Spikes and complaints
Sends whose bounces jumped or that drew abuse reports, with the date and segment. These are what hurt deliverability for the next send.
- Each audience
Its size, how much of it was lost last month against the months before, and how engagement moved.
- The sends
Which campaigns were read, so the summary is never mistaken for more or less than it covers.
When the list is healthy
If nothing stands out, Newsletter list health still posts the sizes and rates in a few lines, so the month is on record.
A failed run is different. If Mailchimp cannot be read, it posts that once. If a send has no report yet, it says so and leaves it out.
Who uses Newsletter list health
Newsletter list health suits anyone who sends a regular newsletter or campaigns from Mailchimp. The examples use made-up names.
A newsletter writer
Clara Jensen writes a weekly letter. Once a month she sees how many readers she kept and whether the letter still lands.
An email marketer running offers
Rafael Costa sends offers to older segments. The bounce line tells him which one to stop mailing before it damages the rest.
A founder watching the audience grow
Mei Chen counts the newsletter as a growth channel. The decay figure tells her what new sign-ups have to make up each month.
A marketing lead reporting up
Ahmed Rahman gives a monthly update. The summary is the email part of it, with the industry comparison already done.
What Newsletter list health connects to
Newsletter list health connects to two tools: it reads Mailchimp and posts one message to Slack. You connect each one yourself, and Toolspoke stores the connection encrypted, so the agent never sees the credential.
Mailchimp
RequiredRead Mailchimp audiences, members, campaigns, reports, segments, tags and templates.
Authentication: API key
Slack
RequiredSearch conversations and send messages to your workspace.
Authentication: Bot token
| Tool | What Newsletter list health does | What it cannot do |
|---|---|---|
| Mailchimp | Reads audiences, member counts, campaigns and reports (list_audiences, get_audience, list_members, list_campaigns, get_campaign_report). | Send, schedule or delete a campaign: the connector has no such action. It can add or update a contact if you give it more than read access, which this agent's instructions forbid. |
| Slack | Posts one message to the channel you chose (send_message). | Delete messages: the connector has no delete action. It can edit and schedule messages, and the agent is told to do neither. |
The only Mailchimp action that changes anything is add_or_update_member, and it is a write. Give this agent read access to Mailchimp and it cannot add, unsubscribe or change a contact. With wider access, that is an instruction, not a lock. The access control guide explains how.
Mailchimp's API key gives full access to the account on Mailchimp's side. Toolspoke's grant is what keeps this agent to reads.
The agent reads counts rather than lists of people, and never posts an email address or a name.
When Newsletter list health runs
Newsletter list health runs on the first Monday of each month at 9am, but only after you switch its schedule on. It arrives switched off, so nothing runs and nothing is charged until you decide.
- Each run covers last calendar month against the two before.
- Every chosen audience gets its own section.
- When nothing stands out, it still posts the sizes and rates.
- If Mailchimp cannot be read, it posts that once.
Each run uses model credit from your workspace balance, so it makes one run a month. The Mailchimp and Slack calls themselves are free.
Your copy is an ordinary agent in your project. You can pause its schedule there, run it once on demand, make it weekly and edit its instructions. The agent's page lists recent runs and their cost.
How to set up Newsletter list health
To get a monthly list check, add Newsletter list health to a Toolspoke project, connect Mailchimp and Slack, choose the channel and switch on the schedule. Nothing runs until the last step.
Step 1: Create a Toolspoke account or sign in
Choose Use this agent. If you are new, you will be asked to sign up first, and you come straight back to this agent afterwards.
Step 2: Add it to a project
Pick the project it should live in. You get your own editable copy, and you can see the two tools it brings before anything connects.
Step 3: Connect Mailchimp with read access
Create an API key in Mailchimp and paste it with your data centre. Give the agent read access, so it cannot change a contact.
Step 4: Connect Slack
Choose Sign in with Slack and approve the Toolspoke app. For a private channel, add the Toolspoke bot to it first.
Step 5: Choose the channel and audiences
Name the channel, and the audiences to check if not all of them. Set a bounce level if 2% is not right for you.
Step 6: Switch on the schedule
The schedule arrives switched off. Run it once to see a summary, then switch it on.
Make Newsletter list health fit your list
Newsletter list health's instructions are plain English and you can edit them after you install it. Installing copies the agent, so your edits stay with your copy. Open the agent in Toolspoke and tell the builder what to change, and it rewrites the instructions.
Paste any sentence below into the builder chat, or say the same thing in your own words.
Run every Monday and cover the previous week against the four before.
This changes the schedule as well as the instructions, and the builder edits both.
Treat any send above 1% bounces as a spike.
Only check the audience called Fieldnote readers.
Report the open rate of sends to the segment Lapsed customers on its own line.
Say whether the list grew by at least 500 contacts last month.
None of these edits needs more access or touches the Never rules. They change what Newsletter list health is told, not what the connections allow.
How it compares to other options
Newsletter list health beats the alternatives when you want the month put together across every send and audience, in Slack. It loses to them when you want a live dashboard to explore.
| Compared on | Newsletter list health | Mailchimp's reports | A deliverability tool | A monthly spreadsheet |
|---|---|---|---|---|
| The whole month in one place | Yes | Per campaign | Yes | If you build it |
| Flags bounce spikes | Yes | You spot them | Yes | If you check |
| Arrives in Slack | Yes | No | Sometimes | No |
| Can change contacts | No, with read access | Yes, by you | Some clean lists | No |
| Inbox placement testing | No | No | Yes | No |
| Setup effort | Connect two accounts | None | A subscription and DNS setup | An hour a month |
Mailchimp's own reports are the better choice for digging into one campaign: who clicked what, which links, which devices.
A deliverability tool is better when you need to know whether mail lands in the inbox or in spam. Newsletter list health reads what Mailchimp reports; it cannot test placement.
Frequently asked questions
Can Newsletter list health unsubscribe or remove people?
Not with read access. The only Mailchimp action that changes a contact is add_or_update_member, a write, which a read-only grant cannot reach. With wider access, the agent is told never to (how access works).
Can it send a campaign?
No. The Mailchimp connector has no action that sends, schedules or deletes a campaign.
Does it read my subscribers' details?
It asks for counts, not lists: one row and the total. It never posts an email address or a name.
What counts as a bounce spike?
A send whose bounces were more than 2% of emails sent, or twice the previous two months' average. You can change the level.
Can it run every week instead?
Yes. Ask the builder to run it weekly and it changes both the schedule and the windows.
Does it work with Klaviyo?
This agent reads Mailchimp. Email campaign report reads Klaviyo campaigns and flows each week.
Is Newsletter list health free?
It has no price of its own, and every Toolspoke plan includes agents. Tool calls cost nothing, but each run draws on your usage balance. Pricing has the details.
Know how your list is doing every month
Connect Mailchimp with read access and Slack, choose the channel and switch on the schedule. Your first summary lands at 9am on the first Monday of the month.