[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)

# Schedule a weekly Privy email campaign

> Create a Privy email from your Saved Template, pick the segment and schedule the send in recipient time zones every week. Hosted, nothing to maintain.

Source: https://cotlet.dev/integrations/privy-api-mcp-server/schedule-weekly-email-campaign

The weekly newsletter is the same routine every Monday: new campaign, template, subject, segment, schedule. It takes 10 clicks and slips when the week gets busy.

Cotlet does it in your own Privy account with list\_segments, list\_campaigns, create\_email\_campaign, send\_email\_campaign and unschedule\_campaign, called by your AI agent, an n8n workflow or a script.

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

Hosted · nothing to install or maintain

## Can Privy do this on its own?

Privy's API and read-only MCP list campaigns and their data but cannot create or send one (checked 23 Oct 2026). Its Zapier app works on contacts only. Scheduling happens in the dashboard.

## How you do it in Privy today

1. Go to Campaigns, click Send email in the upper right, name the campaign, click Continue and pick a template from Privy Templates or Saved Templates.
2. The drag-and-drop editor saves changes by itself. When the design is done, click Subject.
3. Enter the Subject Line and optional Preview Text. From Business Name, From Email and Reply To Email default to Settings: Business Information, Sender Options and Sending Domain. Click Recipients.
4. Choose one or more segments, optionally exclude one, and click Review. Test there sends the email to up to 5 addresses.
5. Click Schedule, choose the day and time, turn on Send in recipient's timezone if you want it, and click Confirm.

## How to schedule a weekly Privy email campaign

Prompt

```
Every Monday, create a campaign from my Saved Template "Weekly picks" with the subject "Five picks for your weekend", send it to Engaged Contacts and schedule it for Tuesday at 9:00 in recipient time zones.
```

1. 01  
### Check the audience  
list\_segments returns each segment's id and mailable\_count. The agent uses the segment you named, and stops if its mailable\_count is 0 or the name does not exist.
2. 02  
### Skip a week that is already queued  
list\_campaigns with status scheduled shows what is waiting. If a campaign with this week's title is there, the agent reports it and creates nothing, so a rerun never double-books the list.
3. 03  
### Create the draft  
create\_email\_campaign sets the template, subject, preview text and segments. The email body is the template as saved, because the tool does not edit the design, so keep a Saved Template you update each week.
4. 04  
### Schedule it  
send\_email\_campaign sets the day and time, with recipient time zones if you asked for them. You confirm each call by default, and the audience is fixed when you do.
5. 05  
### Undo a mistake  
If you spot a wrong subject before delivery is prepared, unschedule\_campaign moves the campaign back to draft. Once preparation starts, only Cancel send in Privy stops it.

### What you get back

Example data

```
Campaign: Weekly picks, 27 Oct
Template: Weekly picks, audience Engaged Contacts (6310 mailable)
Scheduled Tue 27 Oct, 09:00 in recipient time zones
Already scheduled this week: none
```

### Other ways to ask

- Create next week's campaign as a draft and show me the subject and audience, but do not schedule it.
- Every Friday, send the Fall lookbook template to Current Customers at 17:00 in my time zone.
- Schedule the same template to Engaged Contacts and exclude the Unengaged Contacts segment.

## What Privy allows, and what to know first

- Send in recipient's timezone spreads delivery over about 24 hours, and contacts with no known time zone get the email at the chosen time in your business time zone.
- Privy says a scheduled email may go out a couple of minutes before the scheduled time.
- The audience is set when you approve the send, and Privy rechecks exclusions before each recipient's delivery window.
- Unschedule Campaign works only before preparation starts. After that, time zone sends stop with Cancel send, and emails already sent cannot be recalled, so the campaign can show Partially sent.
- A contact in more than one selected segment receives the email once.

send\_email\_campaign asks for your OK by default. To run it weekly without you, switch confirmation off for that tool in your dashboard.

Sources: [Privy Help: Send an Email Campaign](https://help.privy.com/docs/learn/email-campaigns/send-an-email-campaign.md) · [Privy Help: Use Custom and Smart Segments](https://help.privy.com/docs/learn/email-campaigns/segmentation.md) · [Privy Help: API Overview](https://help.privy.com/docs/api-reference/overview)

## Call create\_email\_campaign from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/privy/email-campaigns \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Weekly picks, 27 Oct","template":"Weekly picks","subject_line":"Five picks for your weekend","preview_text":"New arrivals and one restock","segment_ids":["seg_2b11"]}'
```

Example response

```
{
"campaign_id": "cmp_6c15",
"title": "Weekly picks, 27 Oct",
"status": "draft",
"template": "Weekly picks",
"subject_line": "Five picks for your weekend",
"audience": {
"included_segments": [
"Engaged Contacts"
],
"excluded_segments": []
}
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is privy\_write → create\_email\_campaign. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/privy-api-mcp-server.md#automations)

## Privy tools this automation uses

__Cotlet Privy tools used to schedule a weekly Privy email campaign__
| Tool | Parameters |
| ----------------------- | --------------------------------------------------------------------------------- |
| list\_segments | page, per\_page |
| list\_campaigns | status, channel, page, per\_page |
| create\_email\_campaign | name, template, subject\_line, preview\_text, segment\_ids, exclude\_segment\_ids |
| send\_email\_campaign | campaign\_id, send\_at, recipient\_timezone |
| unschedule\_campaign | campaign\_id |

[All 13 Privy tools with descriptions](https://cotlet.dev/integrations/privy-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Privy to Cotlet?

Yes. You sign in to Privy yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Privy 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 Privy automations

- [Resend a Privy email to people who did not open it](https://cotlet.dev/integrations/privy-api-mcp-server/resend-campaign-to-non-openers.md)
- [Pause low-converting Privy popups](https://cotlet.dev/integrations/privy-api-mcp-server/pause-low-converting-popups.md)
- [Privy API and MCP server: every tool](https://cotlet.dev/integrations/privy-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Privy.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Privy.

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

---

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.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

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.