mailerpress-pro/get-outgoing-webhook-settings returns the consolidated outgoing-webhook settings: the event catalogue, the configurations, and whether async delivery is enabled.
The global secret is masked to *** when one is set.
At a glance
| Ability | mailerpress-pro/get-outgoing-webhook-settings |
| Toolset | MailerPress Pro — toolset/mailerpress-pro |
| Group | MailerPress Pro › Webhooks |
| Requires | AcrossAI Pro, plus MailerPress with its Pro add-on active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
Outgoing webhooks are the opposite direction from incoming ones: MailerPress calls out when something happens, rather than being called.
That makes this a data-flow read. Every configured outgoing webhook is contact data leaving the site on an event, and the destinations are worth knowing for the same reasons the incoming doors are.
The async flag matters operationally. With async delivery on, webhook calls are queued and fired in the background, so a slow or failing destination does not hold up the action that triggered it. With it off, a destination that hangs slows down whatever MailerPress was doing.
The masked global secret tells you a shared signing secret exists without revealing it — which is the fact you need when debugging a receiving end that rejects signatures.
Read-only.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
events | array | The event catalogue. |
configs | array | The configured outgoing webhooks. |
async_enabled | boolean | Whether delivery is queued rather than inline. |
global_secret | string | Masked when set. |
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:
Where does MailerPress send data when events happen?
It resolves to one call:
{
"ability": "mailerpress-pro/get-outgoing-webhook-settings",
"parameters": {}
}Worth knowing
- Every outgoing webhook is contact data leaving the site.
- Async off means a slow destination slows MailerPress down.
- The global secret is masked but its presence is reported.
- Read-only.
Related abilities
- MailerPress Pro Webhook Event Catalogue — the events in detail
- MailerPress Pro List Webhooks — the incoming direction
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category