subsequences

Create a new subsequence under a parent sequence

Create a new subsequence under the specified parent sequence with trigger conditions, optional schedule, and optional entry delay in a single call.

<strong>Required</strong> — <code>title</code> (1–200 chars) and <code>conditions</code> (min 1; all conditions use implicit AND). See the condition reference table in the Swagger schema — invalid <code>name</code>/<code>operation</code>/<code>value</code> combinations are rejected with a 400.

<strong>Optional</strong> — <code>scheduleId</code> (server assigns the account default if omitted) and <code>firstStepRelativeDays</code> (entry delay, min 1; omitted = no delay).

To add steps to the subsequence after creation, call <code>POST /v1/sequences/{subsequenceId}/steps</code> using the returned <code>id</code>. To read conditions back, use Get Subsequence Settings. To update, use Update Subsequence.

post/v1/sequences/{sequenceId}/subsequence

Path parameters

sequenceIdstring required

Hashid-encoded ID of the parent sequence.

Request body

titlestring required

Subsequence title. 1–200 characters.

scheduleIdnumber

Sending schedule ID (integer). Use <code>GET /v1/schedules</code> to list available IDs. When omitted, the account default schedule is assigned.

firstStepRelativeDaysnumber

Days after the trigger fires before the first step runs (entry delay). Minimum 1. When omitted, no delay is applied.

Example request

{
  "title": "Re-engagement Subsequence",
  "scheduleId": 58964,
  "firstStepRelativeDays": 2,
  "conditions": [
    {
      "name": "Replied",
      "operation": "is",
      "value": false
    },
    {
      "conditionId": "cond-open-01",
      "name": "Email Open Count",
      "operation": "greater than",
      "value": 3
    },
    {
      "name": "Link Click",
      "operation": "is any"
    }
  ]
}

Response

Subsequence created successfully

Changes

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