mailerpress/update-workflow-step edits a single node of an existing automation in place: its settings, its next_step_id, its alternative_step_id, or its canvas position.
Every other node is untouched.
At a glance
| Ability | mailerpress/update-workflow-step |
| 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 |
What it cannot disturb
Unlike a full workflow update it cannot rebuild branches, cannot delete automation campaigns, and cannot disturb other nodes. It also preserves subscribers’ in-flight progress, so contacts partway through the automation carry on.
That makes it the right call for the common fixes: a wrong delay, a wrong template ID, a branch wired to the wrong next step.
What it cannot do is structural. It cannot add or remove nodes, and it cannot change a node’s type or key — so converting an action into a condition, or inserting a wait step, needs mailerpress/update-workflow.
The boundary is deliberate: everything inside it is safe on a running automation, and everything outside it is not.
Node handles come from mailerpress/get-workflow, which is also where the current settings are.
Idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | The workflow. |
step_id | string | Yes | The node handle. |
settings | object | No | Replacement settings for that node. |
next_step_id | string | No | Rewire the primary pointer. |
alternative_step_id | string | No | Rewire the alternative pointer. |
position | object | No | Canvas position. |
What comes back
| Name | Type | What it is |
|---|---|---|
step | object | The node after the edit. |
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:
Change the delay on that automation step.
It resolves to one call:
{
"ability": "mailerpress/update-workflow-step",
"parameters": {
"id": 21,
"step_id": "wait-1",
"settings": { "duration": 3, "unit": "days" }
}
}Worth knowing
- Preserves in-flight subscriber progress; a full update may not.
- Cannot add, remove, or change the type of a node.
- The right tool for a wrong delay, template or branch pointer.
- Idempotent.
Related abilities
- MailerPress Get Workflow — get the node handles
- MailerPress Update Workflow — for structural changes
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category