mailerpress/update-campaign-settings updates just the campaign’s emailConfig blob: sender name and address, subject, email type and tracking flags.
MailerPress deep-merges the payload into the stored config.
At a glance
| Ability | mailerpress/update-campaign-settings |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Campaigns & Sending |
| Requires | AcrossAI Pro, plus MailerPress active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
The deep merge is what makes this safe for partial writes. Changing the sender address does not clear the tracking flags, which a whole-blob write would.
The sender is the field most likely to be wrong and least likely to be noticed before a send. A campaign with no sender configured cannot be batched at all; one with the wrong sender sends successfully from the wrong address, which is worse.
Tracking flags decide whether opens and clicks are recorded. A campaign sent with tracking off produces no statistics, and there is no way to recover them afterwards — the data was never collected.
That is worth checking before a send you intend to measure.
The subject can be set here or through mailerpress/update-campaign, since both write the same blob.
Idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | The campaign ID. |
emailConfig | object | Yes | Sender name and address, subject, email type and tracking flags. Deep-merged. |
What comes back
| Name | Type | What it is |
|---|---|---|
emailConfig | object | The config after the merge. |
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:
Set the sender address on that campaign.
It resolves to one call:
{
"ability": "mailerpress/update-campaign-settings",
"parameters": {
"id": 44,
"emailConfig": { "sender_email": "hello@example.com" }
}
}Worth knowing
- Deep-merged, so partial writes are safe.
- No sender means the send cannot be batched; a wrong one sends from the wrong address.
- Tracking off means no statistics, unrecoverably.
- Idempotent.
Related abilities
- MailerPress Create Campaign Batch — which needs the sender
- MailerPress Get Campaign — read the current config
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category