mailerpress/import-contacts batch-imports contacts. The data payload matches MailerPress’s own importer shape: tags, lists, a count, a status, a field mapping and the rows.
It is dispatched via Action Scheduler, so it returns before it finishes.
At a glance
| Ability | mailerpress/import-contacts |
| 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 |
How it works
Poll progress with mailerpress/track-import-progress. An import of any size runs in chunks over time rather than in the request.
The status in the payload sets what the imported contacts start as. That is the most consequential field in the whole call: importing as subscribed skips confirmation entirely.
Doing that to a list of addresses somebody has not confirmed is how a site starts sending unsolicited email at scale, and MailerPress will not stop you.
The mapping connects columns in the rows to contact fields and custom fields. A mapping that is slightly wrong imports data into the wrong field for every row, which is tedious to unpick afterwards.
Failed chunks are usually validation errors on individual rows, and mailerpress/retry-import-batch re-queues just those.
Not idempotent — running the same import twice creates duplicates or errors depending on the addresses.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
data | object | Yes | MailerPress importer shape: tags, lists, count, status, mapping and rows. |
What comes back
| Name | Type | What it is |
|---|---|---|
batch_id | integer | The import batch, for polling progress. |
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:
Import this contact list.
It resolves to one call:
{
"ability": "mailerpress/import-contacts",
"parameters": {
"data": {
"lists": [3],
"status": "subscribed",
"count": 250,
"mapping": {},
"rows": []
}
}
}Worth knowing
- Importing as subscribed skips confirmation entirely. Consider whether that is lawful.
- A wrong mapping imports every row into the wrong field.
- Runs in chunks over time; poll for progress.
- Not idempotent.
Related abilities
- MailerPress Track Import Progress — watch it run
- MailerPress Retry Import Batch — fix failed chunks
- MailerPress Check Email Validity — deduplicate first
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category