Reorder steps
Sets the order of the cadence. Send every step id of the sequence exactly once, in the new order; the first becomes step 1. The response is the steps in their new order, as a JSON array in the same shape as GET /v2/sequencer/sequences/{sequence_id}/steps.
Refused with 409 while any enrollment in the sequence is active or paused: renumbering would move the step each person is on, so someone could receive a step twice or miss one. Disabling the sequence does not lift this, because disabling pauses enrollments, even though the 409 message suggests it. pending enrollments do not block. To restructure a sequence people are moving through, duplicate it, change the copy, and move people over with POST /v2/sequencer/enrollments/bulk/move (they start the copy from its first step), or wait until everyone in it has finished.
Safe to retry: the same body produces the same order. user_id must be the author, the team owner or a team admin. Counts toward the Sequencer writes rate limit.
Example
Changing the order of a sequence people are in
- Duplicate the sequence.
- Reorder, add or delete steps on the copy.
- Enable the copy.
- Move people over with Move enrollments to another sequence. They start the copy from its first step.
When the body is refused
A 400 whenstep_ids repeats an id, leaves out a step of the sequence, or includes an id that is not
in it. message names the ids. Also a 400 when the new order would make an auto_email step start
a thread while it has a template with no subject, for example moving a step that replies in a thread in
front of the first email. Sending the same body twice gives the same order, so a retry is safe.
user_id must be the sequence’s 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.
Path Parameters
24-character sequence id.
Body
The team member making the change. Must be the sequence's author, the team owner or a team admin, and have an active plan or seat. A 24-character hexadecimal ID.
"507f1f77bcf86cd799439011"
Every step id of the sequence, each exactly once, in the new order. The first becomes step 1. Each is a 24-character hexadecimal ID.
50Response
The steps in their new order. Production returns a JSON array of steps here, not an object; see the operation description.
The outcome of an action. Shape varies by endpoint — for example enable returns the sequence and how many enrollments it activated, and a bulk verb returns how many rows it moved.