mailerpress/send-raw-email sends a one-off transactional email through MailerPress’s currently active provider.
It bypasses campaigns entirely — it just delivers the HTML you give it to the address you give it.
At a glance
| Ability | mailerpress/send-raw-email |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Settings & Delivery |
| 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 bypasses campaigns, tracking and consent
This has an external side effect: an email is actually dispatched. It is not a preview. It bypasses campaigns entirely — there is no record in the campaign history, no tracking, and no unsubscribe handling unless the HTML includes it. Sending marketing content this way routes around every consent mechanism MailerPress has.
How it works
The legitimate use is transactional: a one-off notification, a manual resend of something a system should have sent, a test of the sending path.
It is genuinely useful for that last one. A raw send that arrives proves the provider is working, independently of anything campaign-related.
What it is not is a way to email subscribers. There is no campaign record, no tracking, no unsubscribe link unless the HTML carries one, and no check against the recipient’s subscription status.
So sending marketing content this way reaches people who unsubscribed, with no way for them to unsubscribe again — which is the outcome consent rules exist to prevent.
The optional key selects a specific provider by service key rather than the active one, which is how you test a newly connected provider before switching to it.
Not idempotent — each call sends.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
to | string | Yes | The recipient address. |
subject | string | Yes | The subject line. |
html | string | Yes | The email body. |
key | string | No | Select a specific provider by service key. Defaults to the active provider. |
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 a test email through our provider.
It resolves to one call:
{
"ability": "mailerpress/send-raw-email",
"parameters": {
"to": "me@example.com",
"subject": "Provider test",
"html": "<p>Testing the sending path.</p>"
}
}Worth knowing
- No campaign record, no tracking, no unsubscribe handling.
- It does not check the recipient’s subscription status.
- Excellent for testing the provider; wrong for anything marketing.
- The key parameter tests a provider before switching to it.
Related abilities
- MailerPress Manage Settings — which provider is active
- MailerPress Send Test Email — the campaign-aware test
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category