mailerpress/find-workflows-using returns every automation that references a given tag or list, in a trigger, an action or a condition, with the exact steps involved.
Call it before renaming or deleting a tag or list.
At a glance
| Ability | mailerpress/find-workflows-using |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Workflows |
| Requires | AcrossAI Pro, plus MailerPress active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
The ID is stored under four different JSON shapes inside workflow node settings, depending on where and how it is referenced. Scanning by eye reliably misses cases, and nothing in MailerPress surfaces the dependency at all.
So a tag deleted without this check breaks automations silently: the trigger stops firing, or the condition evaluates false for everybody, and the workflow carries on looking healthy.
Passing name as well as id catches the other case — conditions that reference a tag or list by name rather than by ID, which survive an ID-based search and break on a rename.
The step-level detail is what makes the result actionable. Knowing a workflow references a tag is a warning; knowing which step does is a fix.
This is the single most important read in the MailerPress suite for avoiding silent breakage, and it has no equivalent in the plugin’s own interface.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
type | string | Yes | tag or list. |
id | integer | Yes | The tag or list ID. |
name | string | No | Also match conditions referencing it by name. Worth passing before a rename. |
What comes back
| Name | Type | What it is |
|---|---|---|
workflows | array | Each referencing automation, with the exact steps involved. |
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:
What automations use this tag?
It resolves to one call:
{
"ability": "mailerpress/find-workflows-using",
"parameters": {
"type": "tag",
"id": 7,
"name": "trial-user"
}
}Worth knowing
- The ID is stored under four JSON shapes. Eye-scanning misses cases.
- Nothing in MailerPress surfaces this dependency.
- Pass the name too, to catch name-matched conditions before a rename.
- Step-level detail turns a warning into a fix.
Related abilities
- MailerPress Delete Tag — what this protects against
- MailerPress Delete List — and the list equivalent
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category