mailerpress/update-template updates template metadata: name, categories and optionally the usage type.
MailerPress requires name and at least one entry in categories on every update. The endpoint does not accept partial updates.
At a glance
| Ability | mailerpress/update-template |
| 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
So changing the categories means sending the name too, and changing the name means sending the categories. A read-then-write is unavoidable, which makes mailerpress/get-template or the listing the required first call.
That requirement also makes it easy to lose categories by accident: sending a name change with a single category replaces the full category list with that one.
Unknown category names are auto-created here as on creation, so a typo during a rename both loses the old categories and invents a new one.
The content body is not updated here. mailerpress/save-template-content handles that, which keeps the metadata write and the body write separate — and means a metadata update cannot disturb the artifacts.
Idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | The template. |
name | string | Yes | Required even when unchanged. |
categories | array | Yes | At least one. Required even when unchanged, and replaces the list. |
usage_type | string | No | What kind of email the template is for. |
What comes back
| Name | Type | What it is |
|---|---|---|
template | object | The template after the write. |
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:
Rename that template.
It resolves to one call:
{
"ability": "mailerpress/update-template",
"parameters": {
"id": 5,
"name": "Monthly newsletter (2026)",
"categories": ["Newsletters"]
}
}Worth knowing
- No partial updates — both fields are always required.
- Sending one category replaces the full list.
- A typo during a rename both loses categories and creates one.
- The body is a separate ability, so metadata writes cannot disturb it.
Related abilities
- MailerPress Get Template — read the current values first
- MailerPress Save Template Content — the body
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category