mailerpress/create-list creates a new MailerPress subscriber list.
Lists group contacts for targeted campaign sends.
At a glance
| Ability | mailerpress/create-list |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Lists |
| 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
A new list is empty and nothing routes to it. Signups reach the default list unless a form names this one, and existing contacts join through mailerpress/update-contact or the bulk equivalent.
So creating a list is the start of a piece of setup rather than the whole of it, and a list created and never routed to stays empty indefinitely.
The choice between a list and a tag is worth making deliberately. A list represents something a person subscribed to and is the right unit for consent; a tag represents something you decided about them and is the right unit for segmentation.
Sites that use lists for both end up with people on lists they never chose, which matters when the unsubscribe link is per list.
Not idempotent — names are not unique, so two calls make two lists with the same name.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
name | string | Yes | The list name. |
description | string | No | What the list is for. |
What comes back
| Name | Type | What it is |
|---|---|---|
list | object | The created list. |
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:
Create a list for product announcements.
It resolves to one call:
{
"ability": "mailerpress/create-list",
"parameters": {
"name": "Product announcements"
}
}Worth knowing
- A new list is empty and nothing routes to it.
- Lists are for consent; tags are for segmentation.
- Names are not unique.
- Not idempotent.
Related abilities
- MailerPress Set Default List — route signups here
- MailerPress Create Tag — the other grouping mechanism
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category