mailerpress/update-workflow is a full-replace update. The nodes array wholly replaces the workflow’s current step tree.
So the sequence is always fetch, mutate, send back.
At a glance
| Ability | mailerpress/update-workflow |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Workflows |
| Requires | AcrossAI Pro, plus MailerPress active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
A full replace is the right primitive for structural change — adding nodes, removing them, rewiring branches — because those cannot be expressed as a patch to one node.
It is the wrong primitive for a small fix, and that is not just inefficiency. A full replace can rebuild branches, disturb nodes you did not mean to touch, and delete automation campaigns attached to steps.
It can also disturb subscribers in flight. A contact partway through a workflow is at a node, and replacing the tree can strand them.
mailerpress/update-workflow-step edits a single node in place and does none of that — it is the right call for a wrong delay, a wrong template ID or a mis-wired branch.
Use this one when the structure genuinely changes.
Non-template workflows with any non-TRIGGER step require MailerPress Pro. A free install can hold a trigger and not much else. The same gate applies to newly added non-TRIGGER steps.
Idempotent in the sense that sending the same tree twice leaves the same workflow.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | The workflow. |
automation | object | No | Workflow metadata. |
nodes | array | Yes | The complete replacement step tree. |
What comes back
| Name | Type | What it is |
|---|---|---|
workflow | object | The workflow after the replace. |
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:
Restructure that automation.
It resolves to one call:
{
"ability": "mailerpress/update-workflow",
"parameters": {
"id": 21,
"nodes": []
}
}Worth knowing
- Wholly replaces the tree. Fetch first.
- Can rebuild branches, delete automation campaigns and strand in-flight subscribers.
- For a single-node fix, use the step ability instead.
- Newly added non-trigger steps need Pro.
Related abilities
- MailerPress Get Workflow — fetch the current tree
- MailerPress Update Workflow Step — the safe alternative
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category