Skip to main content
PUT
Reorder steps
Sets the order of the cadence. Send every step id of the sequence exactly once, in the order you want; the first id becomes step 1.

Example

The response is the steps in their new order: a JSON array in the same shape as List steps, not an object.
Reordering is 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 get a step twice or miss one. The 409 message says to disable the sequence first, but that does not work, because disabling pauses enrollments and paused enrollments still block. pending enrollments do not block.

Changing the order of a sequence people are in

  1. Duplicate the sequence.
  2. Reorder, add or delete steps on the copy.
  3. Enable the copy.
  4. Move people over with Move enrollments to another sequence. They start the copy from its first step.
Or wait until everyone in the original has finished.

When the body is refused

A 400 when step_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

x-api-key
string
header
required

Team-scoped API key generated in the Salesfinity dashboard under Settings → Connections → API & Webhooks. A missing or invalid key returns HTTP 403.

Path Parameters

sequence_id
string
required

24-character sequence id.

Body

application/json
user_id
string
required

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.

Example:

"507f1f77bcf86cd799439011"

step_ids
string[]
required

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.

Maximum array length: 50

Response

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.