Sequences
Update Sequence
Update a sequence name, stop condition, branch logic, or existing sequence email steps
PUT
Update Sequence
Update Sequence
Updates sequence metadata, auto-stop behavior, branch logic, and email content. You can target email steps bynodeId, by emailId, or by array order.
Request
Sequence ID.
Updated sequence name.
Updated re-entry mode:
unlimited, one_time, or matching_field.
matching_field is only valid for event-based sequence triggers.Dot-path event property used by
matching_field. Set to null or omit it to
use the built-in defaults.{"enrollmentMode":"matching_field","enrollmentFieldPath":"order.id"} to allow one active run per order while blocking duplicate active runs for the same subscriber and order.
Updated auto-stop condition. Use
has_tag, does_not_have_tag,
added_to_list, removed_from_list, event_received, or none.Insert an if/else branch after an existing node. Provide
afterNodeId and a
branches array with steps for each path plus elseSteps. Empty branch
paths are rejected unless you set allowEmptyPaths: true. Branch
conditionType values include has_tag, in_list, in_segment,
event_received, link_clicked, and field comparisons. For event_received
and link_clicked, set activityScope to this_sequence, previous_email,
or ever; omitting it checks ever.Email step updates. Provide
emails or steps, not both.Alias for
emails.Responses
Update Sequence