mailerpress/send-confirmation-email triggers the double-opt-in confirmation email for a pending contact.
Clicking it flips their subscription status from pending to subscribed.
At a glance
| Ability | mailerpress/send-confirmation-email |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Contacts |
| Requires | AcrossAI Pro, plus MailerPress active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Not idempotent — each call changes the row set, so re-running is not a no-op |
| Ships in | AcrossAI Pro 0.9.16 and later |
This sends real email to somebody who has not confirmed
This has an external side effect: an email is actually dispatched. It is not a preview. Resending to somebody who deliberately ignored the first one is unsolicited email to a person who has not consented — which is the situation the pending state exists to represent.
How it works
Pending contacts accumulate on every double-opt-in site. Somebody signed up, the confirmation arrived, and they never clicked — through disinterest, a spam filter, or simply not noticing.
A resend is legitimate for the second and third of those and not for the first. The pending state is the record of somebody not having consented, and repeatedly emailing them to ask again is the behaviour consent rules exist to prevent.
One resend to somebody who signed up last week is reasonable. A sweep of every pending contact from the last three years is not.
The contact must be pending. A subscribed contact does not need one and an unsubscribed contact must not be sent one.
Not idempotent — each call sends another email.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
contact_id | integer | Yes | The pending contact. |
What comes back
| Name | Type | What it is |
|---|---|---|
sent | boolean | Whether the confirmation was dispatched. |
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:
Resend the confirmation to that pending signup.
It resolves to one call:
{
"ability": "mailerpress/send-confirmation-email",
"parameters": {
"contact_id": 118
}
}Worth knowing
- Pending means they have not consented. Treat a resend accordingly.
- One resend to a recent signup is reasonable; a sweep of old ones is not.
- An unsubscribed contact must never be sent one.
- Not idempotent.
Related abilities
- MailerPress Get Contact By Email — check their status
- MailerPress Create Contact — which sends the first one
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category