mailerpress/delete-workflow destructively deletes a workflow along with its steps and associated A/B tests. It requires confirm_name matching the workflow’s current name.
The in-flight contacts are the consequence people do not picture.
Before you run it
The workflow, its steps and its A/B tests all go. Contacts currently in flight through the automation lose whatever was coming next, mid-sequence — somebody two emails into a five-email onboarding sequence simply stops receiving it. Disabling with mailerpress/update-workflow-status stops new entries while letting in-flight contacts finish.
At a glance
| Ability | mailerpress/delete-workflow |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Workflows |
| Requires | AcrossAI Pro, plus MailerPress active on the site |
| Capability | manage_options |
| Safety | Destructive — deletes the workflow, its steps and its A/B tests. 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 workflow with active jobs has contacts partway through it. Deleting the workflow ends their sequence wherever they happen to be, which on an onboarding automation means somebody receives two of five emails and nothing more.
mailerpress/get-workflow-stats reports the active job count, which is how many people that is.
Disabling is the alternative and behaves differently in exactly the useful way: it stops new contacts entering while letting those already inside finish.
The A/B test results go too, which on a workflow that has been running a test for weeks is the result of that test discarded.
The name guard is checked live, so a stale name fails rather than deleting a workflow renamed since your read.
Idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | The workflow. |
confirm_name | string | Yes | Must match the workflow’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 workflow was removed. |
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 old automation.
It resolves to one call:
{
"ability": "mailerpress/delete-workflow",
"parameters": {
"id": 21,
"confirm_name": "Onboarding sequence",
"confirm": true
}
}Worth knowing
- In-flight contacts stop mid-sequence.
- Disabling lets them finish and stops new entries.
- A/B test results are discarded with it.
- The name is checked live.
Related abilities
- MailerPress Update Workflow Status — disable it instead
- MailerPress Get Workflow Stats — how many are in flight
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category