Automations

Add a sequence node to an automation

While the automation is "draft", inserts directly into the live sequence. While "active" or "paused", the node is inserted into (a copy of) the sequence staged as draftSequence instead, leaving the running automation untouched until POST .../merge-draft.

post/v1/projectId/{projectId}/automations/{automationId}/node

Request

  • Base URL: https://api.bluefox.email
  • URL: https://api.bluefox.email/v1/projectId/{projectId}/automations/{automationId}/node
  • Auth: HTTP bearer

Path parameters

projectIdstring required

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

automationIdstring required

Request body

type'delay' | 'send-email' | 'filter-audience' | 'branch' | 'condition' | 'set-value' | 'notify' | 'complete' | 'manage-tags' | 'webhook' required

"condition" is special: it does not add a top-level node. Instead, set prevNodeId to an EXISTING branch node's own _id, and it appends one more arm to that branch's branches[] (branches start with two). Its condition fields go under a nested "condition" object in the body, e.g. { "type": "condition", "prevNodeId": "<branchNodeId>", "condition": { "property": "...", "operator": "...", "value": "..." } } - not flat on the request body like filter-audience.

prevNodeIdstring

Create only. Insert immediately after this node (a sibling _id anywhere in the tree, including inside a branch). Omit to insert as the very first node.

Response

OK

statusinteger

Example response

{
  "status": 200
}

Changes

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