Add a step
Adds a step at the end of the cadence; its order is the current number of steps plus one. Move it with PUT /v2/sequencer/sequences/{sequence_id}/steps/reorder. A sequence holds at most 50 steps.
The body is checked against the sequence (400 when a rule is broken): an interval sequence needs interval_seconds and refuses date, and a date sequence needs date and refuses interval_seconds. auto_email needs at least one template. templates and new_thread are only for auto_email and manual_email, and call_purpose only for call. Every template must be on your team; archived templates are accepted. LinkedIn, meeting and SMS exist as one-off task types but cannot be cadence steps.
Adding a step while people are in the sequence is allowed: anyone still partway through reaches it after the earlier steps, and anyone already finished does not. user_id must be the author, the team owner or a team admin. Send an Idempotency-Key: without one, a retry appends a second step. Counts toward the Sequencer writes rate limit.
Step types
display_name becomes the task’s title, and task_note and
task_priority are copied onto it. LinkedIn, meeting and SMS exist as
one-off task types but cannot be cadence steps.
Examples
A call on the day someone is enrolled:Rules
Each of these is a 400 naming the problem:- An
intervalsequence needsinterval_secondsand refusesdate. Adatesequence needsdateand refusesinterval_seconds. auto_emailneeds at least one template.- An
auto_emailstep that starts a thread (the first email step, or one withnew_thread: true) needs asubjecton every template it uses. A step that replies in a thread does not. templatesandnew_threadare only forauto_emailandmanual_email;call_purposeonly forcall.- Every template must be on your team. Archived templates are accepted.
Things to know
- Subjects and threads. An email step replies in the thread of the previous email unless you set
new_thread: true, and a reply does not send its template’ssubject. The first email step always starts a thread, so its template’s subject is the one the prospect sees. - Weights are relative.
weight0 keeps a template on the step but never picks it. Anauto_emailstep whose templates all weigh 0 cannot send. - Adding to a running sequence. Allowed. People still partway through reach the new step after the earlier ones; people who already finished do not.
- Retries. Without an
Idempotency-Key, a retry appends the step twice. user_idmust 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.
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
auto_email sends an email on its own; manual_email, call and task create a task for the rep who owns the enrollment.
auto_email, manual_email, call, task 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"
Required on an interval sequence, refused on a date sequence. Seconds to wait after the previous step finished (an email sent, or a task completed or skipped); for the first step, after enrollment. Whole number.
x >= 0Required on a date sequence, refused on an interval sequence. ISO 8601 date-time when the step comes due.
Step label, up to 200 characters. Becomes the title of the task the step creates.
200auto_email and manual_email only. true starts a new email thread with this step's template subject; otherwise the email replies in the previous email's thread and the template's subject is not sent. The first email step always starts a thread.
Up to 2,000 characters, copied onto the task the step creates.
2000high, medium, low Seconds after the task is created at which a still-open task expires and the enrollment moves on. Whole number. Omit to let tasks wait indefinitely.
x >= 0call steps only.
auto_email and manual_email only; auto_email needs at least one. 1 to 10 templates, each on your team (archived ones are accepted), picked by weight each time the step runs.
10Response
The new step.
One step of a cadence.
24-character hexadecimal id.
"507f1f77bcf86cd799439011"
The sequence the step belongs to (24-character id).
"507f1f77bcf86cd799439011"
The team that owns the step (24-character id).
1-based position in the cadence. Steps run in this order; change it with PUT /v2/sequencer/sequences/{sequence_id}/steps/reorder.
auto_email sends an email on its own. manual_email creates a task with the email drafted from a template, for the rep to edit and send. call creates a call task. task creates a to-do. Tasks go to the rep who owns the enrollment.
auto_email, manual_email, call, task On an interval sequence: seconds to wait after the previous step finished (an email sent, or a task completed or skipped) before this step comes due. For the first step, the wait after enrollment. Absent on a date sequence.
On a date sequence: when the step comes due. Absent on an interval sequence.
Step label. Becomes the title of the task the step creates.
Email steps: true starts a new email thread with this step's template subject; false replies in the previous email's thread, so the template's subject is not sent. The first email step always starts a thread.
Note copied onto the task the step creates.
Priority copied onto the task the step creates. Defaults to medium.
high, medium, low Seconds after the task is created (when the step comes due) at which a still-open task expires and the enrollment moves on to the next step. Absent means tasks wait indefinitely.
Email steps: the templates to pick from, by weight. Empty for call and task steps.
Call steps only: the call purpose set on the step. Absent when none is set.
Number of deliveries from this step, counted as events. Rebuilt every 15 minutes.
Number of opens from this step, counted as events. Rebuilt every 15 minutes.
Number of link clicks from this step, counted as events. Rebuilt every 15 minutes.
Number of replies from this step, counted as events. Rebuilt every 15 minutes.
Number of bounces from this step, counted as events. Rebuilt every 15 minutes.
Number of opt-outs from this step, counted as events. Rebuilt every 15 minutes.
Number of failed sends from this step, counted as events. Rebuilt every 15 minutes.
Times this step ran and produced work: emails sent plus tasks created. Rebuilt every 15 minutes.
When the step was created.
When it last changed.