mailerpress/bulk-delete-contacts deletes multiple contacts in one call.
It fires the delete webhook per contact, which is worth knowing before running it.
Before you run it
Every contact in the list is deleted with their engagement history, and the delete webhook fires once per contact — so an integration downstream receives a burst of delete events and acts on them. confirm_count must match the ID array length exactly, which is the guard against a list that matched more than intended.
At a glance
| Ability | mailerpress/bulk-delete-contacts |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Contacts |
| Requires | AcrossAI Pro, plus MailerPress active on the site |
| Capability | manage_options |
| Safety | Destructive and irreversible — deletes many contacts and fires the delete webhook per contact. Requires confirm_count. |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
The webhooks are the part that reaches beyond this site. An outgoing webhook configured for contact deletion fires once per contact, so deleting four hundred contacts sends four hundred events to whatever is listening.
On a CRM integration that means four hundred deletions there too, which may be intended and may be a surprise.
mailerpress-pro/get-outgoing-webhook-settings shows what is subscribed.
The count guard is the same as the bulk update’s and catches the same failure: a list assembled from a query that matched more broadly than expected.
Engagement history goes with each contact, as with the single deletion — and at bulk scale that is a substantial amount of sending history removed at once.
Idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
ids | array | Yes | The contacts to delete. |
confirm_count | integer | Yes | Must equal the length of ids. |
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 | integer | How many contacts were 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 these contacts.
It resolves to one call:
{
"ability": "mailerpress/bulk-delete-contacts",
"parameters": {
"ids": [118, 119],
"confirm_count": 2,
"confirm": true
}
}Worth knowing
- The delete webhook fires once per contact, reaching downstream integrations.
- The count guard catches an over-broad list.
- Engagement history goes too, at scale.
- Idempotent.
Related abilities
- MailerPress Pro Outgoing Webhook Settings — what receives the events
- MailerPress Bulk Update Contacts — unsubscribe instead
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category