mailerpress/save-template-content persists the block-editor JSON body and the compiled HTML for a template.
It is the template analogue of mailerpress/save-campaign-content, with the same two-artifact problem.
At a glance
| Ability | mailerpress/save-template-content |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Templates |
| Requires | AcrossAI Pro, plus MailerPress active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
A template holds both a JSON tree and compiled HTML, and writing one without the other leaves them disagreeing — the same failure as on campaigns, one level further upstream.
That is worse at the template level, because the inconsistency propagates. Every campaign built from a template with a stale artifact inherits the stale artifact, and the problem multiplies quietly across however many campaigns were created.
So writing both is the rule here for the same reason it is on campaigns, with more at stake.
A template’s HTML is not what a campaign sends — the campaign takes a snapshot at creation and has its own artifacts thereafter. Fixing a template does not fix existing campaigns.
Which means a template fix is a fix for future campaigns only, and the existing ones need fixing individually.
Idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | The template. |
content | object | No | The block-editor JSON body. |
html | string | No | The compiled HTML. |
What comes back
| Name | Type | What it is |
|---|---|---|
saved | array | Which artifacts were written. |
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:
Save the template content.
It resolves to one call:
{
"ability": "mailerpress/save-template-content",
"parameters": {
"id": 5,
"content": {},
"html": "<html>…</html>"
}
}Worth knowing
- Write both. A stale template artifact propagates into every campaign built from it.
- Fixing a template does not fix campaigns already created from it.
- The same two-artifact rule as campaigns, one level upstream.
- Idempotent.
Related abilities
- MailerPress Save Campaign Content — the campaign equivalent
- MailerPress Get Template — check the current artifacts
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category