mailerpress/get-campaign fetches a single campaign: its name, subject, status, content, sender information and scheduling metadata.
The content it returns is the block tree, not the compiled HTML.
At a glance
| Ability | mailerpress/get-campaign |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Campaigns & Sending |
| Requires | AcrossAI Pro, plus MailerPress active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
A campaign holds its content twice: a block-editor JSON tree, which is what the editor shows, and a compiled HTML artifact, which is what recipients receive. They are stored separately and can disagree.
So this read tells you what the editor would show and not what a recipient would receive. For that, mailerpress/get-campaign-send-html returns the compiled artifact.
Those two disagreeing is the central failure mode of campaign editing, and mailerpress/check-campaign-send-readiness is the ability that checks for it directly.
The sender information matters as much as the content. A campaign with no sender configured cannot be batched, and the failure arrives at send time rather than at save time.
The scheduling metadata says when a scheduled campaign will go, which on a campaign scheduled weeks ago is worth confirming before anybody edits it.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | The campaign ID. |
What comes back
| Name | Type | What it is |
|---|---|---|
campaign | object | Name, subject, status, block content, sender information and scheduling. |
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:
Show me that campaign.
It resolves to one call:
{
"ability": "mailerpress/get-campaign",
"parameters": {
"id": 44
}
}Worth knowing
- This is the editor’s content. The compiled HTML is a separate read.
- The two disagreeing is the main way campaign edits go wrong.
- No sender configured means the send fails at batch time.
- Read-only.
Related abilities
- MailerPress Get Campaign Send HTML — what recipients get
- MailerPress Check Campaign Send Readiness — whether the two agree
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category