mailerpress/delete-campaign deletes a single campaign record, its send batches and its stored HTML content. It requires confirm_name matching the stored name.
The batches are the loss people do not anticipate.
Before you run it
The campaign, its send batches and its stored content all go, permanently. The batches are the part worth pausing on: they carry the engagement statistics for every send of that campaign, and deleting them removes the record of how it performed. Moving the campaign to trash through mailerpress/update-campaign-status takes it out of the way reversibly.
At a glance
| Ability | mailerpress/delete-campaign |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Campaigns & Sending |
| Requires | AcrossAI Pro, plus MailerPress active on the site |
| Capability | manage_options |
| Safety | Destructive and irreversible — deletes the campaign, its send batches and its stored content. Requires confirm_name. |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
A send batch holds the engagement statistics for that send — opens, clicks, unsubscribes, and the per-recipient log. Deleting the campaign deletes them, which removes the historical record of how it performed.
On a site that reports on campaign performance over time, that is a gap in the history rather than a tidy-up.
The trash status is the alternative: mailerpress/update-campaign-status with trash takes the campaign out of the working list and keeps everything.
The name guard is checked against the stored name, so a stale name from an earlier read fails rather than deleting something that was renamed since.
Idempotent in the sense that deleting an already-deleted campaign is a no-op.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | The campaign ID. |
confirm_name | string | Yes | Must exactly match the campaign’s stored name. |
confirm | boolean | Yes — must be true | The irreversibility gate. Without it the call is refused before anything is touched. |
What comes back
| Name | Type | What it is |
|---|---|---|
deleted | boolean | Whether the campaign was removed. |
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:
Delete that old campaign permanently.
It resolves to one call:
{
"ability": "mailerpress/delete-campaign",
"parameters": {
"id": 44,
"confirm_name": "September product update",
"confirm": true
}
}Worth knowing
- The send batches and their statistics go too.
- That leaves a gap in performance history, not just a shorter list.
- Trashing keeps everything and takes it out of the way.
- The name is checked live, catching renames.
Related abilities
- MailerPress Update Campaign Status — trash it instead
- MailerPress Get Campaign Batches — what would be lost
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category