Update sequence
Update sequence name, steps, angles, goal, or status.
Tool: update_sequence
status='paused' is a real pause: each active lead's queued send is discarded and the lead rewinds to its current step, so setting active again re-sends that step freshly rendered from the latest copy (edit while paused and the fix goes out on resume). Wait timers freeze; enrollments stay intact - use remove_from_sequence to cancel someone permanently. Pause frees the seat's concurrent-sequence capacity slot; unpausing to active re-checks day_cap//5 and fails with validation_error if any hosting seat is full.
Parameters
| Param | Type | Required | Description |
|---|---|---|---|
sequence_id | string (slug or UUID) | yes | Sequence to update. |
name | string | no | New name. |
steps | array of step objects | no | Replacement steps array - see the in-flight rules below. |
messaging_angles | string[] | no | Replacement angle list. |
default_angle | string | no | Alias: angle. |
goal | string | no | New goal. |
status | string | no | draft | active | paused. |
Only the fields you pass are changed.
With leads mid-flight, step changes are limited. Allowed (applies live): edit any step's message (queued unsent sends are re-personalized automatically - per-lead overrides still win), add steps, remove steps no active lead is standing on. Rejected with
in_flight_conflict: removing or re-typing a step an active lead is currently ON - stop those leads first (remove_from_sequence) or create a new sequence.
status='paused'freezes sends and frees the seat's concurrent-sequence capacity slot. Unpausing toactivere-checksday_cap // 5on every seat with mid-flight enrollments - rejects withvalidation_errorif any seat is full.
Sample request — success
{
"sequence_id": "founder-outreach-0016",
"name": "Founder outreach v2",
"status": "active"
}Sample request — in flight rebake
{
"sequence_id": "founder-outreach-0016",
"steps": [
{
"id": "invite",
"type": "send_connection_request",
"message": "Hi {{first_name}} — building in the same space."
},
{
"id": "follow_up",
"type": "send_message",
"delay_days": 2,
"message": "Hi {{first_name}} — following up on my note."
}
]
}