Add actions to an outcome
Appends one or more nodes to the end of an outcome’s action chain. You send the actions, and the server creates their node ids, links and positions.
Applied atomically: if any node in the list is rejected, nothing is written. Appending an action the chain already performs is a no-op rather than a duplicate, so a retry is safe.
Each entry has a type. Most types are { type, config }. A switch router is { type: "switch", cases: [{ condition, actions }], default } because one router produces a branch node plus a chain per case.
Each action must include its full settings. To save an action with incomplete settings, use PUT /workflow. A chain that already ends in a branch cannot be added to. Change it in the dashboard workflow editor or with PUT /workflow.
Send an Idempotency-Key header if you may retry. A repeat with the same key and the same body returns the original result instead of appending again; a repeat with the same key and a different body is rejected with 409.
Required API key scope: campaign_workflows:write.
Authorizations
Headers
Path Parameters
Query Parameters
Body
Response
The updated workflow.
