[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Re-send a Campaign Monitor campaign to people who did not open it

> Build a segment of Campaign Monitor subscribers who skipped a campaign, draft a new subject line for them and schedule the send. Runs weekly.

Source: https://cotlet.dev/integrations/campaign-monitor-api-mcp-server/re-engage-non-openers

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.

[Sign up free](https://cotlet.dev/app/signup?app=campaign-monitor) [All Campaign Monitor tools](https://cotlet.dev/integrations/campaign-monitor-api-mcp-server.md)

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

1. Open Campaigns > Sent and click the campaign. The report opens on the Snapshot page and needs the reports permission.
2. Click Create Segment and choose Email not opened. If the campaign went to several lists, pick the list, then click Create.
3. 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.
4. 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.
5. 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

Prompt

```
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.
```

1. 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.
2. 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.
3. 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.
4. 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.
5. 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

Example data

```
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](https://help.campaignmonitor.com/s/article/campaigns) · [Campaign Monitor Help: Email campaign reports](https://help.campaignmonitor.com/articles/Knowledge/terms-used-campaign-reports) · [Campaign Monitor Help: List segmentation](https://help.campaignmonitor.com/s/article/list-segmentation) · [Campaign Monitor API: Segments](https://www.campaignmonitor.com/api/v3-3/segments/)

## Call create\_segment\_from\_campaign from a script

curl

```
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"}'
```

Example response

```
{
"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 cron](https://cotlet.dev/integrations/campaign-monitor-api-mcp-server.md#automations)

## Campaign Monitor tools this automation uses

__Cotlet Campaign Monitor tools used to re-send a Campaign Monitor campaign to people who did not open it__
| 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 |

[All 13 Campaign Monitor tools with descriptions](https://cotlet.dev/integrations/campaign-monitor-api-mcp-server.md#tools)

## 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.

## More Campaign Monitor automations

- [Weekly Campaign Monitor campaign report in your chat](https://cotlet.dev/integrations/campaign-monitor-api-mcp-server/weekly-campaign-report.md)
- [Turn Campaign Monitor journeys on and off with an AI agent](https://cotlet.dev/integrations/campaign-monitor-api-mcp-server/turn-journeys-on-and-off.md)
- [Campaign Monitor API and MCP server: every tool](https://cotlet.dev/integrations/campaign-monitor-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## 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.

[Sign up free](https://cotlet.dev/app/signup?app=campaign-monitor)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.