mailerpress/get-template fetches a single template by ID, including its stored HTML and JSON body.
Use it before mailerpress/create-campaign to see what a template actually contains.
At a glance
| Ability | mailerpress/get-template |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Templates |
| 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
Templates carry the same two-artifact structure as campaigns: a block-editor JSON tree and a compiled HTML body. A template with one and not the other produces campaigns with the same gap.
So a campaign built from a template with no compiled HTML starts life unable to send, and the problem originated in the template rather than in the campaign.
That makes this read worth doing before building rather than after — the same artifact check mailerpress/check-campaign-send-readiness performs for campaigns, done by eye for the template.
The categories come back too, which on a site with many near-duplicate categories is how you work out which one a template is actually filed under.
The body is the largest part of the response, which is why the listing omits it.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | The template. |
What comes back
| Name | Type | What it is |
|---|---|---|
template | object | Name, categories, usage type and the stored HTML and JSON body. |
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:
What is in that template?
It resolves to one call:
{
"ability": "mailerpress/get-template",
"parameters": {
"id": 5
}
}Worth knowing
- Templates have the same two-artifact structure as campaigns.
- A template missing its compiled HTML produces campaigns that cannot send.
- Check before building, not after.
- The body is why the listing omits it.
Related abilities
- MailerPress Save Template Content — fix a missing artifact
- MailerPress Create Campaign — build from it
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category