mailerpress/check-email-validity tests whether an email already exists as a contact on this site, returning a simple {exists: bool}.
Use it before mailerpress/create-contact to avoid duplicate errors.
At a glance
| Ability | mailerpress/check-email-validity |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Contacts |
| Requires | AcrossAI Pro, plus MailerPress active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
A duplicate create is an error rather than a silent merge, which is correct and makes bulk contact creation fail partway through unless duplicates are filtered first.
So this is the import-preparation call: check a list of addresses, split into new and existing, create the first and update the second.
exclude_id skips one contact, which matters when checking an address against a contact being renamed — otherwise a contact’s own address counts as a collision with itself.
It reports existence rather than deliverability. An address that exists as a contact may be unsubscribed or bounced, and this says nothing about that.
For the record behind an existing address, mailerpress/get-contact-by-email returns it.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
email | string | Yes | The address to check. |
exclude_id | integer | No | Skip this contact — useful when checking against a contact being renamed. |
What comes back
| Name | Type | What it is |
|---|---|---|
exists | boolean | Whether the address is already a contact. |
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:
Do we already have this email?
It resolves to one call:
{
"ability": "mailerpress/check-email-validity",
"parameters": {
"email": "sam@example.com"
}
}Worth knowing
- A duplicate create errors rather than merging.
exclude_idstops a contact colliding with itself during a rename.- Existence is not deliverability — the contact may be bounced.
- Read-only.
Related abilities
- MailerPress Create Contact — what this precedes
- MailerPress Import Contacts — the bulk path
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category