mailerpress-pro/delete-segment permanently deletes a segment. It requires confirm_name matching the segment’s current name.
No contacts are affected.
Before you run it
No contacts are deleted — a segment is a query, not a membership — but anything referring to the segment by name stops resolving, including campaigns configured to send to it. The conditions themselves are gone and there is no copy; a segment built from a dozen conditions is real work to reconstruct.
At a glance
| Ability | mailerpress-pro/delete-segment |
| Toolset | MailerPress Pro — toolset/mailerpress-pro |
| Group | MailerPress Pro › Segments |
| Requires | AcrossAI Pro, plus MailerPress with its Pro add-on active on the site |
| Capability | manage_options |
| Safety | Destructive — requires confirm_name matching the segment’s current name. |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
The name guard is checked at delete time rather than against a name you were given earlier, which also catches the case where somebody renamed the segment between your read and your write.
What breaks is references. Segments are addressed by name, so a campaign or automation pointing at the deleted segment has nothing to resolve — and depending on where that reference sits, the failure may not surface until a send.
Checking what uses a segment before deleting is worth doing, and there is no single call that answers it — campaigns and workflows both reference segments.
The conditions are the other loss. A carefully built segment is a piece of audience logic somebody reasoned about, and nothing keeps a copy.
Idempotent: deleting one already gone is a no-op.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | The segment ID. |
confirm_name | string | Yes | Must match the segment’s current name. The guard against ID-only mass deletion. |
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 |
|---|---|---|
id | integer | The segment 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 the old lapsed-customers segment.
It resolves to one call:
{
"ability": "mailerpress-pro/delete-segment",
"parameters": {
"id": 4,
"confirm_name": "Lapsed customers",
"confirm": true
}
}Worth knowing
- No contacts are deleted.
- References by name stop resolving, possibly not until a send.
- The conditions are gone with no copy.
- Idempotent.
Related abilities
- MailerPress Pro List Segments — read the conditions first
- MailerPress Pro Create Segment — rebuild it
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category