mailerpress-pro/list-webhooks returns every registered incoming webhook configuration.
Secrets are masked to *** in every response. MailerPress never returns a raw secret value after it is stored, which means these reads can tell you that a secret exists and never what it is.
At a glance
| Ability | mailerpress-pro/list-webhooks |
| 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
An incoming webhook is a door into the contact list: something outside the site posts to it and contacts are created or changed. That makes the inventory a security read as much as a configuration one.
The useful question is usually “what can write to our contacts”, and the answer is this list. A webhook configured during an integration trial two years ago is still a door.
The masking is not an inconvenience to work around. A secret that could be read back could be read by anything that could make this call, and MailerPress’s decision to store them one-way is the right one — which does mean a lost secret is regenerated rather than recovered.
Incoming webhooks are separate from outgoing ones. mailerpress-pro/get-outgoing-webhook-settings covers the other direction.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
webhooks | array | Each webhook with its ID, configuration and a masked secret. |
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:
What can write into our MailerPress contacts?
It resolves to one call:
{
"ability": "mailerpress-pro/list-webhooks",
"parameters": {}
}Worth knowing
- Each incoming webhook is a door into the contact list.
- Secrets are masked and cannot be read back, by design.
- Old integration webhooks are still live doors.
- Incoming and outgoing webhooks are separate systems.
Related abilities
- MailerPress Pro Save Webhook — create or change one
- MailerPress Pro Delete Webhook — close a door
- MailerPress Pro Outgoing Webhook Settings — the other direction
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category