Skip to main content
POST
Enable a sequence
Turns the sequence on and starts everyone waiting in it. This is the call that lets a sequence send email and create tasks.

What changes

  • People added while the sequence was disabled (pending), and people its last disable paused, become active. Their next step is due at the next open sending window; the first step’s interval_seconds does not delay people who were already waiting. The response’s activated is how many started.
  • Tasks the last disable put on hold go back to their reps’ queues.
  • Enrollments a rule is holding for approval stay pending until a manager approves them. Enrollments a rep paused by hand stay paused.

Example

The response holds the sequence, now with enabled: true, and activated. Enabling a sequence that is already enabled returns activated: 0 and changes nothing.

Before you enable

Enabling is refused with 422 unless the sequence can actually run. Check these first: The mailboxes a sequence sends from are its own email_account_ids when set, otherwise the mailboxes assigned to its author, otherwise the team’s shared mailboxes. A paused or disconnected mailbox does not count. A healthy mailbox elsewhere on the team does not help a sequence that points at broken ones. message on the 422 says which check failed.

Retrying

  • 409 has two causes: the Idempotency-Key was used for a different request, or the first enable with email steps is still setting up email sending for the team. If you did not reuse a key, wait a moment and retry.
  • 503 means setting up email sending failed for a moment. Retry in a few minutes.
  • 422 with “Email sequences are not activated for your team yet” will not clear on retry; contact support.
user_id must be the 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.

Headers

Idempotency-Key
string

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

id
string
required

24-character sequence id.

Body

application/json
user_id
string
required

The team member this call acts as. Must be an active member of the team the API key belongs to.

Example:

"507f1f77bcf86cd799439011"

Response

The sequence and how many enrollments started.

sequence
object
required

A Sequencer sequence (a cadence). can_manage is returned by list and get only; step_type_counts and enrollment_counts by list only.

Example:
activated
integer
required

Enrollments moved to active. 0 when the sequence was already enabled.