Campaign Monitor automation · runs weekly
Re-send a Campaign Monitor campaign to people who did not open it
A sale email goes out on Tuesday, 35% of the people who got it open it, and the rest never see the offer. Reaching them again means building a segment from the report, drafting a second email and scheduling it.
Cotlet does it in your own Campaign Monitor account with list_campaigns, get_campaign_report, create_segment_from_campaign, create_campaign_draft and schedule_campaign, called by your AI agent, an n8n workflow or a script.
Hosted · nothing to install or maintain
Can Campaign Monitor do this on its own?
Campaign Monitor builds a non-opener segment from the Snapshot page and lets you send to it, but every step is manual (checked 22 Oct 2026). Its A/B test compares two versions of one campaign and is not a second send to people who skipped the first. The API can create the segment rule and a draft, but there is no official MCP server, so it takes your own key and code.
How you do it in Campaign Monitor today
- Open Campaigns > Sent and click the campaign. The report opens on the Snapshot page and needs the reports permission.
- Click Create Segment and choose Email not opened. If the campaign went to several lists, pick the list, then click Create.
- The segment builder opens, where you can rename the segment or edit its rules. The Not opened tab of Recipient activity exports the same people.
- Back in Campaigns, choose Create a campaign > Single campaign, name it and work through the checklist: Add subject, Add sender, Select recipients, and a design through Reuse a past email or Import HTML.
- The Assistant checks the campaign for problems, and Schedule for later with Confirm schedule queues it. All of it repeats for the next campaign.
How to re-send a Campaign Monitor campaign to people who did not open it
Take last Tuesday's Autumn sale campaign, make a segment of everyone who did not open it, draft a new email with the subject "Still thinking about it?" and schedule it for Thursday at 9:00. - 01
Pick the campaign
list_campaigns with status sent and a sent_from date finds the campaign by name. get_campaign_report reads Delivered and Opened, so the agent can skip a campaign that was sent more recently than the wait you gave in the prompt.
- 02
Make the audience
create_segment_from_campaign runs with audience not_opened, the same choice as Email not opened on the Snapshot page. A campaign that went to several lists needs list_id, so the agent asks which list instead of guessing.
- 03
Write the second email
create_campaign_draft uses the sender of the first campaign, the new subject from your prompt and the new segment as recipients. Body HTML comes from your prompt or a file. The draft reaches nobody until it is scheduled.
- 04
Leave time for the segment
The vendor's API docs say to wait about an hour after creating a segment before sending to it. The agent sets send_at at least that far ahead and tells you the time it chose.
- 05
Schedule it
schedule_campaign waits for your OK by default. If the app asks for payment before a send to more than 5 recipients, the call stops and returns payment_required; Cotlet never enters card details.
What you get back
Autumn sale: delivered 8,400, opened 2,940 (35.0%)
Segment "Autumn sale: not opened" created on list Customers
Draft "Autumn sale, second chance" ready, subject "Still thinking about it?"
Scheduled for Thu 2026-10-29 09:00 to the segment (about 5,460 people) Other ways to ask
- Every Wednesday, make a segment of people who did not open Tuesday's newsletter and list it without sending anything.
- Segment people who clicked any link in the webinar invite and draft a reminder for them.
- Draft a re-send to non-openers of the last three campaigns and wait for my OK on each one.
What Campaign Monitor allows, and what to know first
- The Create Segment pop-up on the Snapshot page offers three choices: Email opened, Has any link clicked and Email not opened.
- Campaign Monitor says open rates are estimates and Apple Mail Privacy Protection can raise them, so some people counted as openers never read the email.
- A segment belongs to one list. Campaign Monitor does not allow a segment across lists, so a campaign sent to two lists needs a segment on each.
- In Select recipients a segment shows under its list, and Exclude removes the people of a chosen list or segment from the send.
- The Assistant on the campaign checklist surfaces issues that would stop the send, so the agent reads it before scheduling.
schedule_campaign asks for your OK by default. To run it weekly without you, switch confirmation off for that tool in your dashboard.
Sources: Campaign Monitor Help: Campaigns · Campaign Monitor Help: Email campaign reports · Campaign Monitor Help: List segmentation · Campaign Monitor API: Segments
Call create_segment_from_campaign from a script
curl -X POST https://cotlet.dev/api/v1/campaign-monitor/campaigns/c8e1d4a07b3f4a9e8d2c5b6a7f901234/segment-from-campaigns \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"audience":"not_opened","list_id":"f2a9b7c1d3e44f08a6b5c4d3e2f10987","name":"Autumn sale: not opened"}' {
"segment_id": "9e2b5d8a1c7f4630b4a9d2e5f8c13706",
"name": "Autumn sale: not opened",
"list_id": "f2a9b7c1d3e44f08a6b5c4d3e2f10987",
"rule": "Email not opened",
"source_campaign_id": "c8e1d4a07b3f4a9e8d2c5b6a7f901234"
} MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is campaign_monitor_write → create_segment_from_campaign. Example data.
Schedule it in n8n, Make, Zapier or cronCampaign Monitor tools this automation uses
| Tool | Parameters |
|---|---|
| list_campaigns | status, sent_from, sent_to, cursor, limit |
| get_campaign_report | campaign_id |
| create_segment_from_campaign | campaign_id, audience, list_id, name |
| create_campaign_draft | name, subject, preview_text, from_name, from_email, reply_to, list_ids, segment_ids, html |
| schedule_campaign | campaign_id, send_at, confirmation_emails |
Frequently asked questions
Is it safe to connect Campaign Monitor to Cotlet?
Yes. You sign in to Campaign Monitor yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Campaign Monitor once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.
Give your agent access to Campaign Monitor.
Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Campaign Monitor.