subsequences

Update the schedule, entry delay, or conditions of a subsequence

Update the <code>scheduleId</code>, <code>firstStepRelativeDays</code>, and/or <code>conditions</code> on a subsequence. All fields optional — omit to leave unchanged.

<strong>Conditions are full-replacement</strong> — supplying the field replaces the entire set, it does not append. Supplying <code>conditions: []</code> is silently ignored by the internal API and does NOT clear conditions.

Response is always <code>{"message": "Subsequence updated successfully"}</code> — call Get Subsequence Settings to read the updated state.

patch/v1/sequences/{sequenceId}/subsequence/{subsequenceId}

Path parameters

sequenceIdstring required

Hashid-encoded ID of the parent sequence.

subsequenceIdstring required

Hashid-encoded ID of the subsequence to update.

Request body

scheduleIdnumber

Replace the current sending schedule. Use <code>GET /v1/schedules</code> to list available IDs.

firstStepRelativeDaysnumber

Replace the entry delay (days after the trigger before the first step runs). Minimum 1.

Example request

{
  "scheduleId": 60030,
  "firstStepRelativeDays": 3,
  "conditions": [
    {
      "conditionId": "cond-open-01",
      "name": "Email Open Count",
      "operation": "greater than",
      "value": 3
    },
    {
      "name": "Replied",
      "operation": "is",
      "value": false
    }
  ]
}

Response

Subsequence updated successfully

Changes

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