Enroll Contact
Enroll a contact into a sequence template, starting a sequence run.
The template must be ACTIVE and have at least one step; the sequence is
instantiated from the template’s steps and scheduled exactly like an
enrollment made from the app, including task-owner assignment.
A contact already running this template is rejected rather than enrolled twice, and so is a contact (or its company) on an exclusion list.
A contact with an active sequence from a different template is also
rejected: stop that sequence first (POST /v1/sequences/{id}/stop) to avoid
two sequences messaging the same person at once. Templates the contact only
has completed or stopped sequences for do not block enrollment.
Requires the sequences:write scope on the API key.
Authorizations
Bearer API key issued from Settings → Developers.
Body
Enroll Contact payload
Response
Successful Response
Unique identifier.
Workspace this sequence belongs to.
Contact this sequence is targeting.
Template the sequence was instantiated from.
Current execution state.
ACTIVE, SUCCEEDED, FAILED, COMPLETED, WAITING_FOR_LEAD, WAITING_FOR_USER, STOPPED_EARLY, FOUND, REFUSED Per-run template variables substituted into outbound messages.
Contact list that triggered this sequence, if any.
When the most recent step ran.
When the sequence was created.
When the sequence last changed.
Summary of the contact this sequence is targeting.
Summary of the template this sequence was instantiated from.