mailerpress/rename-tag renames an existing MailerPress tag.
It accepts name for consistency with the other rename abilities; MailerPress reads it as title, translated at the dispatch boundary.
At a glance
| Ability | mailerpress/rename-tag |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Tags |
| 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
Before renaming or deleting a tag or list, mailerpress/find-workflows-using is the only thing that surfaces which automations depend on it. The ID is stored under four different JSON shapes, so scanning by eye reliably misses cases.
For tags that matters more than for lists, because workflow conditions reference tags by name more often — a condition checking “has tag: trial-user” against a renamed tag stops matching, and the automation carries on running while doing nothing.
Nothing errors. The workflow executes, the condition evaluates false for everybody, and the branch nobody takes is silently empty.
So passing both the ID and the name to mailerpress/find-workflows-using before renaming is the check, because it catches name-matched conditions as well as ID-matched ones.
Contact assignments follow the tag record rather than the name, so renaming does not disturb who has it.
Idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | The tag. |
name | string | Yes | The new name. |
What comes back
| Name | Type | What it is |
|---|---|---|
tag | object | The tag after the rename. |
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 tag.
It resolves to one call:
{
"ability": "mailerpress/rename-tag",
"parameters": {
"id": 7,
"name": "trial-user"
}
}Worth knowing
- Name-matched workflow conditions stop matching and nothing errors.
- Pass both ID and name to the dependency check.
- Contact assignments follow the record, not the name.
- Idempotent.
Related abilities
- MailerPress Find Workflows Using — check before renaming
- MailerPress List Tags — the current names
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category