mailerpress/check-campaign-send-readiness reports whether a campaign would actually send, and whether what it would send matches what the editor shows.
Omit the ID to audit every campaign at once.
At a glance
| Ability | mailerpress/check-campaign-send-readiness |
| 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
No compiled HTML at all. The campaign exists, the editor shows content, and the artifact is empty — so a send delivers nothing.
A JSON block tree stored where HTML should be. That happens when a write put the wrong artifact in the wrong place, and the result is recipients receiving raw JSON.
Content authored with nothing compiled. The block tree is current and the artifact was never built from it.
MailerPress warns about none of these. Each produces a campaign that looks ready and is not.
One honest limitation: MailerPress stores no timestamp for the compiled artifact, so true staleness cannot be proven. This reports what is verifiable and says so where it is not — a campaign can have both artifacts present, agreeing in shape, and still have an older compile.
Auditing every campaign at once is the useful mode before a sending window.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | No | One campaign. Omit to audit every campaign. |
What comes back
| Name | Type | What it is |
|---|---|---|
results | array | Per campaign: whether it would send, and any failure found. |
notes | array | Where a check could not be conclusive and why. |
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:
Are any of our campaigns broken?
It resolves to one call:
{
"ability": "mailerpress/check-campaign-send-readiness",
"parameters": {}
}Worth knowing
- Three failure modes MailerPress gives no warning about.
- No artifact timestamp exists, so staleness cannot be proven — and it says so.
- Auditing everything at once is the pre-send mode.
- Read-only.
Related abilities
- MailerPress Get Campaign Send HTML — inspect the artifact
- MailerPress Save Campaign Content — fix it
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category