mailerpress/send-test-email dispatches a test rendering of a campaign to a list of email addresses.
This has an external side effect: an email is actually dispatched. It is not a preview.
At a glance
| Ability | mailerpress/send-test-email |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Campaigns & Sending |
| 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
This has an external side effect: an email is actually dispatched. It is not a preview. Use addresses you control. A test to a real subscriber’s address is indistinguishable from the campaign itself as far as they are concerned.
How it works
A test send is the only way to see what actually arrives. Rendering and previewing prove the HTML is right; only a real send proves it survives the provider, the spam filters and the receiving client.
Email clients mangle HTML in ways no preview reproduces — Outlook in particular — so a campaign that previews perfectly can arrive broken.
Deliverability is the other thing only a real send surfaces. A campaign landing in spam from the site’s sending domain is a problem to find before the list gets it.
The parameters are the destinations, the rendered HTML and the subject — so this sends what you give it rather than what is stored. Testing a stored campaign means fetching mailerpress/get-campaign-send-html and passing that, which also tests the artifact rather than the editor version.
Not idempotent — each call sends.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
contacts | array | Yes | The destination email addresses. |
htmlContent | string | Yes | The rendered HTML to send. |
subject | string | Yes | The subject line. |
What comes back
| Name | Type | What it is |
|---|---|---|
sent | boolean | Whether the dispatch was accepted. |
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:
Send me a test of that campaign.
It resolves to one call:
{
"ability": "mailerpress/send-test-email",
"parameters": {
"contacts": ["me@example.com"],
"htmlContent": "<html>…</html>",
"subject": "September product update"
}
}Worth knowing
- Only a real send proves rendering in clients and deliverability.
- Pass the compiled artifact, not the editor version, to test what would ship.
- Use addresses you control.
- Not idempotent.
Related abilities
- MailerPress Get Campaign Send HTML — get the real artifact
- MailerPress Preview Campaign For Contact — the non-sending check
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category