mailerpress-pro/delete-custom-field permanently deletes a contact custom-field definition and every value stored against it. It requires confirm_field_key matching the key.
The values are the part that matters.
Before you run it
This deletes the definition and every value stored against it, across every contact. On a list of fifty thousand people that is fifty thousand values, gone at once with no copy. Anything referencing the field — a segment condition, a personalisation token in a campaign — stops working, and a personalisation token with no field behind it renders empty in a sent email.
At a glance
| Ability | mailerpress-pro/delete-custom-field |
| Toolset | MailerPress Pro — toolset/mailerpress-pro |
| Group | MailerPress Pro › Contact Custom Fields |
| Requires | AcrossAI Pro, plus MailerPress with its Pro add-on active on the site |
| Capability | manage_options |
| Safety | Destructive — deletes the definition and every stored value. Requires confirm_field_key. |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
A field definition on its own is cheap to recreate. The values are not — they arrived from signup forms, imports and integrations over however long the field has existed, and nothing else on the site holds them.
So the confirmation is on the key rather than a boolean, and the key is the same string the data is filed under. Typing it is a moment of looking at exactly which field this is.
The downstream breakage is worth checking first. A segment condition on a deleted field stops matching, and a personalisation token for it renders empty — which means a campaign that greeted people by company name now greets them by nothing, visibly, in a real email.
There is no soft-delete. To take a field out of use while keeping the data, stop writing to it and remove it from forms; the definition can stay.
Idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
field_key | string | Yes | The field to delete. |
confirm_field_key | string | Yes | Must match field_key exactly. The guardrail. |
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 |
|---|---|---|
field_key | string | The field removed. |
values_deleted | integer | How many stored values 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 unused signup-source field.
It resolves to one call:
{
"ability": "mailerpress-pro/delete-custom-field",
"parameters": {
"field_key": "signup_source",
"confirm_field_key": "signup_source",
"confirm": true
}
}Worth knowing
- Every stored value goes, across every contact.
- Segment conditions on the field stop matching.
- A personalisation token for it renders empty in sent email.
- There is no soft-delete — leaving the definition unused is the alternative.
Related abilities
- MailerPress Pro List Custom Fields — confirm which field
- MailerPress Pro List Segments — check what references it
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category