Disable a sequence
Turns the sequence off. Returns the sequence and paused, the number of enrollments paused. Every active enrollment becomes paused, with pause_reason sequence_disabled and no due time. Open tasks from the sequence are put on hold, hidden from reps’ queues and refused if someone tries to complete them, and call tasks are taken out of reps’ dial lists. Nothing is finished or deleted: enabling again resumes exactly these enrollments and releases the tasks. pending enrollments stay pending.
Already disabled: returns paused: 0 and changes nothing, so a retry is safe. Disabling does not unlock reordering or deleting steps, or deleting the sequence: paused enrollments still block those.
user_id must be the author, the team owner or a team admin. Counts toward the Sequencer writes rate limit.
What changes
- Every
activeenrollment becomespaused, withpause_reasonset tosequence_disabledand no due time. The response’spausedis how many. - Open tasks from the sequence go on hold: they disappear from reps’ queues and cannot be completed, and call tasks are taken out of reps’ dial lists.
pendingenrollments staypending, and enrollments a rep paused by hand stay paused.
Example
enabled: false, and paused, the number of enrollments
this call paused.
Things to know
- Disabling a sequence that is already disabled returns
paused: 0and changes nothing, so a retry is safe. - Disabling does not unlock reordering or deleting steps, or deleting the sequence. Those are refused while enrollments are paused, too.
user_idmust be the author, the team owner or a team admin.
Authorizations
Team-scoped API key generated in the Salesfinity dashboard under Settings → Connections → API & Webhooks. A missing or invalid key returns HTTP 403.
Headers
Makes this write safe to retry. Send a unique value, such as a UUID, and send the same value again when you retry the same request. A retry with the same key and the same request (method, path including the query string, and JSON body) returns the original successful response without acting twice. The same key with a different body or path returns 409, and so does a retry while the first request is still running; that one is safe to repeat after a moment. A request that fails frees its key, so a retry runs the write again: after a 5xx on a create, confirm with a GET before retrying. Keys are kept for 24 hours and are scoped to your team.
Path Parameters
24-character sequence id.
Body
The team member this call acts as. Must be an active member of the team the API key belongs to.
"507f1f77bcf86cd799439011"
Response
The sequence and how many enrollments were paused.