a mailchimp bot for the moments before and after a send
find out what would stop a campaign from going out before launch morning. a mailchimp bot in dusk can read the send checklist and the email itself.
after the send, it can bring back delivery figures and clicks by link. keep the bot on reporting duty while you make the call to send.

what a bot can do in Mailchimp
use the campaign id from the edition you mean. a draft, a test idea and last week’s send can have nearly identical names. have the bot show the title and status before reading the content or reporting numbers.
| action | dusk bot treats it as | what you would use it for |
|---|---|---|
| List campaigns | read | find the edition in the right audience and date window |
| Get campaign info | read | confirm the chosen campaign and its status |
| Get campaign send checklist | read | separate errors blocking a send from optional warnings |
| Get campaign content | read | compare the plain-text copy with the html version |
| Get campaign report | read | read delivery and engagement totals for the sent campaign |
| List campaign click details | read | rank tracked destinations by the click metric you choose |
| Get campaign link details | read | read total and unique clicks for an individual tracked destination |
composio, the connection service behind dusk bot's apps, lists 278 Mailchimp actions (version 20261116_00, read 20 november 20264). dusk bot treats 142 as reads, 5 as sends and 131 as changes.
only actions starting with a read word (get, list, search) count as reads, so a read-only bot can't call the rest. a send reaches people or moves money, like add subscriber to workflow email, and waits for your Allow unless you set a daily amount.
connect Mailchimp
- open Connected apps in the sidebar.
- pick Mailchimp and sign in on Mailchimp's own page, so your password goes to them and never to a bot.
- choose which bots may use it, and whether each may only read or may also change things. your bookkeeper doesn't need your Mailchimp.
- ask in plain words. reading and drafting happen freely; sending asks you first.
give the reporting bot an exact list of read actions. connect mailchimp, choose your bot and select the reads above. give it the newsletter audience and the campaign id for a recent send. ask for the most-clicked destination before scheduling regular reports.
routines to copy
treat launch prep and results as different jobs. a campaign can pass the send checklist and still have the wrong offer in its copy. use the first two routines before launch and the last one after readers have had a chance to click.
launch blockers
every thursday at 3, find the newest draft for my newsletter audience. read its send checklist. give me the campaign id and the errors i have to fix. put optional warnings on a separate line. leave it as a draft.thursdays at 3 pm · errors that block launch and warnings that need judgment
offer in both versions
every friday at 9, open the newest newsletter draft. compare the offer, deadline and main destination in its html and plain-text copy. quote any mismatch here with its location. flag either version if it is empty. leave the copy alone.fridays at 9 am · differences a reader would notice between email versions
where readers went
every monday at noon, find last week’s sent newsletter for my audience. get its report and tracked link details. list delivery totals and rank the destinations by unique clicks. name the metric. separate the main offer from footer links. if nothing went out, skip the ranking.mondays at noon · delivery figures and a ranked list of destinations
what it asks you first
keep resend off the action list too. send campaign asks first by default. resend campaign can also deliver mail, but dusk classifies that action as a change. the send rule does not cover it. a reporting bot only needs the named reads.
careful with Full access: a bot there with no sending rule can send up to 25 a day without asking. give it Ask every time.
what it cannot do
- measure a draft’s performance. mailchimp can return zeros for a draft. read the status before treating zero as a result.
- rank links without tracking data. the click detail action lists tracked links for sent campaigns. a missing link has no figure to rank.
- explain a reader’s intent from a click. a click shows a destination. it does not tell you whether the reader liked the offer.
deciding if the campaign is ready
reserve the final read for someone who knows the offer. a send checklist can identify a missing requirement. it cannot decide whether the discount in the email matches what you meant to promise. if your only job is to press send on an approved edition, do that in mailchimp.
what it looks like
a fictional example.
before
grace bell has a newsletter draft ready for review. the html offers free shipping through friday. the plain-text copy says thursday.after the bot
offer mismatch: the two versions give readers different deadlines. confirm the intended day before changing the copy or sending the campaign.an illustration with made-up names and numbers.
questions
can i find which newsletter link got the most attention?
choose the click metric first. ask for unique clicks per destination and the campaign id. repeated clicks by one reader can change a ranking based on total clicks.
does the bot need my subscriber list for a weekly report?
campaign totals and link results are enough for these routines. leave individual subscriber lookups off its action list.
sources
drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].
give a mailchimp campaign a day before reading the results
a google sheets bot that flags low stock by row
a hubspot assistant for the customer handover
add new airtable rows without rewriting existing records
turn your notes into a comment on the right asana task
ask what an asana task actually says