mailerpress/delete-list permanently deletes a subscriber list and every contact-membership row that references it. It requires confirm_name matching the list’s current name.
Nobody is deleted. Their membership is.
Before you run it
The list and every membership row go. The contacts themselves survive — nobody is deleted — but everybody who was on this list is now on one fewer, and a contact whose only list this was becomes unreachable by list-targeted campaigns while still appearing subscribed. Check first what depends on it: mailerpress/find-workflows-using is the only thing that surfaces automation dependencies.
At a glance
| Ability | mailerpress/delete-list |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Lists |
| Requires | AcrossAI Pro, plus MailerPress active on the site |
| Capability | manage_options |
| Safety | Destructive — deletes the list and every membership 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
A contact whose only list this was remains subscribed and becomes unreachable by any list-targeted campaign — which is a state that looks fine on the contact record and sends them nothing.
That is worth checking before deleting a list with a large membership, because there is no report afterwards that distinguishes those contacts from anybody else.
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 joining this list, or branching on membership of it, stops working when the list goes — and the failure surfaces as an automation that quietly does nothing.
Deleting the default list is worth particular care: the site then has no default until another is set, and unrouted signups have nowhere to go.
Idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | The list. |
confirm_name | string | Yes | Must match the list’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 list was removed. |
memberships_removed | integer | How many contact memberships 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 the old campaign list.
It resolves to one call:
{
"ability": "mailerpress/delete-list",
"parameters": {
"id": 9,
"confirm_name": "Spring promo 2024",
"confirm": true
}
}Worth knowing
- Contacts survive; a contact whose only list this was becomes unreachable.
- Workflows referencing the list stop working, silently.
- Deleting the default leaves signups with nowhere to go.
- Idempotent.
Related abilities
- MailerPress Find Workflows Using — check dependencies first
- MailerPress Set Default List — set a new default first
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category