Automations

Merge staged draft changes into a live automation

Only meaningful when status is "active" or "paused" and draftSequence/draftTrigger/draftExitCriteria are present (i.e. node/trigger/exit-criteria edits were made after the automation went live). Re-validates the same way as activate and is a no-op (hasErrors: true, nothing persisted) on failure. On success, the staged draft becomes the live sequence/trigger/exitCriteria and any contact currently mid-automation is transitioned onto the new sequence from its current position. Requires { "confirm": true } in the body - omit it (or send false) to get back the automation's current full state with confirmationRequired: true instead, with nothing applied. Always fetch and show the caller (or end user) that state before sending confirm: true.

post/v1/projectId/{projectId}/automations/{id}/merge-draft

Request

  • Base URL: https://api.bluefox.email
  • URL: https://api.bluefox.email/v1/projectId/{projectId}/automations/{id}/merge-draft
  • Auth: HTTP bearer

Path parameters

projectIdstring required

The project _id, found in the app under Project Settings.

idstring required

Request body

confirmboolean

Must be true to actually apply this action.

Response

OK - check result.hasErrors/result.confirmationRequired before assuming the action actually applied.

statusinteger

Example response

{
  "status": 200,
  "result": {
    "hasErrors": true
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.