Sequences and enrollment
Sequences separate drafting, validation, publishing, enrollment, starting, delivery, and replies.
A sequence is an ordered outreach journey built from a worksheet view or a workflow. Use it when the same audience needs a paced set of steps, while keeping drafting, publication, enrollment, and delivery separate. The sequence builder is at /dashboard/automations/sequences; a worksheet supplies the rows it can enroll.
Build the audience first in a workbook, then use a workflow only when a trigger or graph should control enrollment.
Build from a worksheet
sequence.sequences.create_from_worksheet creates a draft, binds exactly one worksheet view, validates it, and stages that view's rows. It is free and synchronous. It does not publish, start, or send, so you can inspect the sequence and its audience in the app before delivery exists.
Keep lifecycle states separate
| Stage | What happens |
|---|---|
| Draft and validate | Create or edit the sequence, then read structural errors without saving or sending. |
| Publish | Marks a draft version as published. It does not enroll people, call a provider, or send. |
| Enroll | Stages eligible worksheet rows as admission candidates. Starting is separate. |
| Start and deliver | The delivery stage that can reach real people, paced by sender settings. |
Enrollment can freeze up to 10,000 worksheet rows. A sequence without usable LinkedIn identities reports unresolved rows. A provider-bound LinkedIn journey with no connected LinkedIn sender returns sequence_no_senders and stages no rows. Email-only journeys can still be enrolled without a mailbox.
Use the current step palette
The canonical sequence model includes email, wait, condition, random split, action, and LinkedIn steps. Its action and LinkedIn arms cover the outreach actions used by the builder. The frozen spec says the intended eleven-step palette includes email, send DM, connection request, wait for connection, profile view, profile fetch, like, comment, wait, condition, and Slack message.
Validate before publication
A Sequence should be structurally valid before it is published or enrolled. Ask Architect to use the outreach skill to check the journey order, then use the sequence validation capability to return structural errors without saving or sending. In the builder, check the Worksheet view, steps, and selected sender context before you move beyond the draft.
Validation is not delivery. A valid draft proves that the currently saved structure can be evaluated, while publication creates the published version and enrollment stages people from the selected Worksheet view. Starting and delivery remain later events, which means a published Sequence has not reached a prospect merely because it has been validated.
Inspect the Sequence in Automations after each meaningful change. Keep the returned Sequence identifier for the next capability call, and follow a returned web_url to the matching app object when one is available. The URL is a useful app shortcut, but the JSON id remains the durable reference in tool calls.
Keep enrollment separate from delivery
Enrollment stages Rows from a Workbook view as admission candidates. It does not send them a message, and it does not silently turn a draft into a running journey. That boundary lets you inspect the audience before the explicit start action permits provider delivery.
The outreach skill treats publishing, enrollment, starting, delivery, and reply as separate facts. A reply ends the person’s run, and company pause on reply can apply where several people belong to one company. Check the Sequence state and related Run rather than assuming that one lifecycle event implies another.
Missing connections do not prevent building a Sequence. They can block a provider-bound execution step, such as a LinkedIn journey that needs a connected sender. Preserve the draft, connect the needed account in settings, then recheck the current sequence contract before retrying the blocked operation.
When sequence work fails
sequence.sequences.validate returns structural errors without saving or sending. Use it before publishing. If enrollment is blocked by a missing sender, connect the sender for the provider-bound journey, then retry. Missing or invalid workbook, worksheet, saved view, or sort-column references appear in lint results as enrollment_workbook_not_found, enrollment_worksheet_not_found, enrollment_saved_view_not_found, or enrollment_sort_column_not_found.
A failed enrollment does not make the underlying Workbook disappear. Use the named error to inspect the source Workbook, Worksheet, saved view, or sort Column, then rerun validation before staging Rows again. If a live action starts durable work, inspect its Run instead of submitting the same enrollment request repeatedly.