Four settings are writable: the from address, the from name, and the two flags deciding whether those override what individual plugins ask for.
That is the whole surface, and the narrowness is the design.
At a glance
| Ability | email/update-delivery-settings |
| Toolset | Email Delivery — toolset/wp-mail-smtp |
| Group | Email Delivery › Delivery |
| Requires | WP Mail SMTP, active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
Why the mailer is not writable here
Switching the mailer without the matching credentials stops all email on the site — including password resets, which is how you would normally get back in to fix it. It is a change that wants a settings screen in front of a human, not an API call.
No credential can be written here either. An API key arriving through a chat transcript is a key that has been logged somewhere, and there is no version of that which is fine. Use WP Mail SMTP’s own settings screen.
What is left is the part that is safe to automate and genuinely useful: correcting a from address after a domain move, or turning forcing on so one misbehaving plugin stops sending as something else.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
from_email | string | No | Address the site sends from. |
from_name | string | No | Name the site sends as. |
from_email_force | boolean | No | Force this address over what individual plugins ask for. |
from_name_force | boolean | No | Force this name over what individual plugins ask for. |
What comes back
| Name | Type | What it is |
|---|---|---|
settings | object | The delivery settings after the write. |
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:
We moved to a new domain — change the from address to hello@newdomain.com and force it.
It resolves to one call:
{
"ability": "email/update-delivery-settings",
"parameters": {
"from_email": "hello@newdomain.com",
"from_email_force": true
}
}Worth knowing
- Idempotent — writing the same values twice leaves the same configuration.
- A from address on a domain the mailer is not authorised to send for will be rejected by the provider, not by this call. Follow with
email/send-test-email. - Forcing the address is usually right for deliverability and occasionally wrong for transactional mail that deliberately sends as the customer.
Related abilities
- Get Email Delivery Settings — read the current sender first
- Send a Test Email — confirm the new address actually sends
- Diagnose Email Delivery — check nothing else is broken
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category