mailerpress/get-workflow fetches one workflow by ID, including its automation metadata and its full node tree.
Two normalisations happen on the way out.
At a glance
| Ability | mailerpress/get-workflow |
| 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
Node type is normalised to uppercase — TRIGGER, ACTION, CONDITION and the rest — because MailerPress stores them inconsistently and a caller comparing case-sensitively gets the wrong answer on some nodes.
Node position metadata is extracted from settings and surfaced at the top level, where it belongs. Canvas position is presentation rather than configuration, and burying it inside the settings blob means anything editing settings has to preserve it carefully.
The node tree is what mailerpress/update-workflow replaces wholesale, so this read is the required first half of any structural edit: fetch, mutate, send back.
Node wiring uses step_id string handles with next_step_id and alternative_step_id pointers. CONDITION nodes carry settings.branches for multi-way splits.
For a single-node change, mailerpress/update-workflow-step edits in place and avoids the whole fetch-mutate-replace cycle — which matters because a full replace has side effects a single-step edit does not.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | The workflow. |
What comes back
| Name | Type | What it is |
|---|---|---|
workflow | object | Automation metadata and the full node tree. |
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:
Show me how that automation is wired.
It resolves to one call:
{
"ability": "mailerpress/get-workflow",
"parameters": {
"id": 21
}
}Worth knowing
- Node types are uppercased, because MailerPress stores them inconsistently.
- Canvas position is lifted out of settings so editing settings cannot lose it.
- This is the required first half of a structural edit.
- Single-node changes have a narrower ability.
Related abilities
- MailerPress Update Workflow — the full replace
- MailerPress Update Workflow Step — change one node
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category