mailerpress/create-campaign creates a new MailerPress campaign. It starts in draft status.
Only title is required.
At a glance
| Ability | mailerpress/create-campaign |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Campaigns & Sending |
| Requires | AcrossAI Pro, plus MailerPress active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Not idempotent — each call changes the row set, so re-running is not a no-op |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
campaign_type chooses the kind: newsletter, automated, wp_email, wc_email or confirm_email.
That choice is structural rather than cosmetic. An automated campaign is what a workflow sends; the transactional kinds are what MailerPress Pro attaches to WordPress and WooCommerce email types; a newsletter is the ordinary broadcast.
Rich content goes under meta.json as a block tree and meta.emailConfig as the subject and email type.
A campaign created with a block tree and no compiled HTML sends nothing. mailerpress/save-campaign-content is where the compiled artifact is written, and mailerpress/check-campaign-send-readiness is how you confirm it exists.
Not idempotent — each call creates a campaign.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
title | string | Yes | The campaign name, shown to administrators. |
campaign_type | string | No | newsletter, automated, wp_email, wc_email or confirm_email. |
meta | object | No | Rich content: json for the block tree, emailConfig for subject and email type. |
What comes back
| Name | Type | What it is |
|---|---|---|
campaign | object | The created campaign. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
Create a newsletter campaign for the product update.
It resolves to one call:
{
"ability": "mailerpress/create-campaign",
"parameters": {
"title": "September product update",
"campaign_type": "newsletter"
}
}Worth knowing
- The type is structural — an automated campaign is what a workflow sends.
- A block tree without compiled HTML sends nothing.
- Starts as a draft, which is correct.
- Not idempotent.
Related abilities
- MailerPress Save Campaign Content — write the content
- MailerPress List Templates — start from a template instead
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category