mailerpress/create-tag creates a new MailerPress tag for contact segmentation and workflow-automation triggers.
Tags are cheap to create and hard to remove cleanly, which is worth knowing at this end.
At a glance
| Ability | mailerpress/create-tag |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Tags |
| Requires | AcrossAI Pro, plus MailerPress active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Not idempotent — each call changes the row set, so re-running is not a no-op |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
A tag becomes load-bearing the moment a workflow keys on it. After that, deleting or renaming it breaks automation in ways nothing surfaces — which is why mailerpress/find-workflows-using exists.
So the naming is worth a moment. A tag named for a campaign — spring-promo — dates badly; one named for the thing it means — trial-user — does not.
The difference between a tag and a list is intent. A list is something a person subscribed to and carries consent weight; a tag is something you decided about them and does not.
Using tags to record consent, or lists to record attributes, produces a system where neither answers its own question properly.
Not idempotent — names are not unique, so two calls make two tags with the same name, which is a genuinely confusing state.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
name | string | Yes | The tag name. |
What comes back
| Name | Type | What it is |
|---|---|---|
tag | object | The created tag. |
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:
Create a tag for trial users.
It resolves to one call:
{
"ability": "mailerpress/create-tag",
"parameters": {
"name": "trial-user"
}
}Worth knowing
- A tag becomes load-bearing as soon as a workflow keys on it.
- Name for what it means, not for the campaign that created it.
- Tags are attributes; lists are consent.
- Names are not unique — two tags with one name is possible and confusing.
Related abilities
- MailerPress List Tags — check it does not exist
- MailerPress Create List — the consent-bearing alternative
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category