mailerpress/list-workflow-actions lists every registered workflow action handler with its keys, label, description and settings schema.
The settings schema is the useful part.
At a glance
| Ability | mailerpress/list-workflow-actions |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Workflows |
| Requires | AcrossAI Pro, plus MailerPress 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 action node carries settings, and what those settings are depends entirely on the action — a send-email action needs a campaign; a wait action needs a duration; a tag action needs a tag ID.
Composing a node without knowing its schema produces a node that saves and does nothing, or one MailerPress rejects on execution rather than on save.
So this is the reference for authoring, and it is read live because the action set is extensible — a third-party integration can register its own.
Non-template workflows with any non-TRIGGER step require MailerPress Pro. A free install can hold a trigger and not much else.
That gate applies at the action level: a free install can compose a workflow whose only node is a trigger, which is a workflow that fires and does nothing.
The bare array MailerPress returns is wrapped into an object.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
actions | array | Each action with its keys, label, description and settings schema. |
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 an automation do?
It resolves to one call:
{
"ability": "mailerpress/list-workflow-actions",
"parameters": {}
}Worth knowing
- The settings schema is what makes a node valid.
- A node composed without it saves and does nothing.
- Actions are extensible per site.
- Non-trigger steps need MailerPress Pro.
Related abilities
- MailerPress Create Workflow — compose with these
- MailerPress List Workflow Conditions — the branching side
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category