30 days free. No credit card. Full access from the moment you connect your site.

Start free trial

MailerPress Pro Webhook Event Catalogue

mailerpress-pro/list-webhook-events enumerates every outgoing webhook event type with its name, description and sample payload shape.

Read it before authoring a webhook, so you know both which events to subscribe to and what the receiving end will get.

At a glance

Abilitymailerpress-pro/list-webhook-events
ToolsetMailerPress Pro — toolset/mailerpress-pro
GroupMailerPress Pro › Webhooks
RequiresAcrossAI Pro, plus MailerPress with its Pro add-on active on the site
Capabilitymanage_options
SafetyRead-only — changes nothing
RepeatableIdempotent — running it twice leaves the same result
Ships inAcrossAI Pro 0.9.16 and later

How it works

The sample payload is the more useful half. Subscribing to an event is easy; building something that consumes it requires knowing the shape, and discovering that shape by triggering the event and inspecting what arrives is a slow way to learn.

The event names are also not guessable in the way people assume. “Contact subscribed” and “contact added” may both exist and mean different things — one being a confirmed opt-in and the other a record being created.

Subscribing to the wrong one produces an integration that works and fires at the wrong moments, which is worse than one that does not fire.

The descriptions are what separate them.

Read-only and cheap.

Input

This ability takes no input.

What comes back

NameTypeWhat it is
eventsarrayEach event with its name, description and sample payload shape.
successbooleanWhether the call completed.
messagestringA one-line summary of what happened, suitable for showing a human.
error_codestringPresent 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 events can we subscribe to?

It resolves to one call:

{
  "ability": "mailerpress-pro/list-webhook-events",
  "parameters": {}
}

Worth knowing

  • The sample payload is what the receiving end has to parse.
  • Similar event names can mean materially different moments.
  • Subscribing to the wrong event produces a working integration firing wrongly.
  • Read-only.

Related abilities


Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager

Browse the rest: Every ability, by category


Keep reading