mailerpress/delete-tag permanently deletes a tag and every contact-tag row that references it. It requires confirm_name matching the tag’s current name.
The automation consequence is the one that matters.
Before you run it
The tag and every contact-tag row go. Contacts survive, but any workflow triggered by this tag, or branching on it, stops working — and nothing reports that. The automation keeps running and the branch is simply never taken. mailerpress/find-workflows-using is the only thing that surfaces the dependency, and it should be run with both the ID and the name.
At a glance
| Ability | mailerpress/delete-tag |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Tags |
| Requires | AcrossAI Pro, plus MailerPress active on the site |
| Capability | manage_options |
| Safety | Destructive — deletes the tag and every contact-tag row referencing it. Requires confirm_name. |
| 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.
A workflow triggered by this tag being applied has lost its trigger — it will never fire again, and nothing says so. A workflow branching on the tag evaluates that branch false for everybody, so contacts flow down the other path.
Both failures are silent and both look like the automation working correctly with nobody qualifying.
That is the reason to check dependencies before rather than diagnose after: afterwards, the tag is gone and the workflow references an ID that resolves to nothing.
Segments on Pro installs can also reference tags, and those stop matching in the same way.
Contacts themselves are unaffected beyond losing the tag.
Idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | The tag. |
confirm_name | string | Yes | Must match the tag’s current name. |
confirm | boolean | Yes — must be true | The irreversibility gate. Without it the call is refused before anything is touched. |
What comes back
| Name | Type | What it is |
|---|---|---|
deleted | boolean | Whether the tag was removed. |
assignments_removed | integer | How many contact-tag rows went with it. |
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:
Delete that unused tag.
It resolves to one call:
{
"ability": "mailerpress/delete-tag",
"parameters": {
"id": 7,
"confirm_name": "spring-promo",
"confirm": true
}
}Worth knowing
- Workflows triggered by or branching on the tag fail silently.
- Both failures look like an automation with nobody qualifying.
- Segments referencing the tag stop matching too.
- Check dependencies before, not after.
Related abilities
- MailerPress Find Workflows Using — the required check
- MailerPress List Tags — confirm which tag
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category