> ## Documentation Index
> Fetch the complete documentation index at: https://docs.entryway.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Sequences and playbooks

> Design the steps of a campaign: invitations, messages, waits, branches, manual tasks and exits, then review exactly what each person will receive.

A sequence is the plan a campaign follows for each person: what to send, how long to wait, what to do if they accept or reply, and where the plan ends. Open **Sequences** to see your saved sequences and build new ones.

## Starting points

* **A recommended playbook.** The guided campaign flow suggests a playbook and fills its details from your Vault. See [Campaigns overview](/campaigns/overview).
* **A template.** The template gallery (**Start with a useful structure**) lets you browse ready-made structures by goal and channel. A template is imported into an unsaved draft; you review it before saving. Templates that need actions Entryway cannot perform yet are marked with their blockers.
* **A blank sequence.** Add steps yourself after **Start**.

## Step types

| Step | What it does |
| - | - |
| **Connection request** | Sends a LinkedIn invitation, with or without a short note |
| **Message** | Sends a LinkedIn message to someone you are connected with |
| **Wait** | Waits before the next step. After an invitation, a wait for acceptance lasts up to 14 days |
| **Condition** | Splits the path in two, for example **They accepted the connection**, **They replied**, or whether a person's company, headline, location or name is filled in, contains or is exactly a value |
| **Manual step** | A task you complete yourself, marked done in the sequence |
| **End sequence** | Ends the path. Nothing further is sent |

Every path must end, and a condition needs both a "yes" and a "no" path. The builder tells you when a path is unfinished or a message has no text.

<Note>
  Sequences send LinkedIn invitations and messages. InMail and email steps are not supported.
</Note>

## Personalizing messages

Messages can use these variables: `{{first_name}}`, `{{name}}`, `{{company}}`, `{{headline}}`, `{{location}}` and `{{linkedin_url}}`. Entryway never sends a blank variable: if someone in the audience is missing a detail a message needs, the review stops until it is fixed.

## Building on the canvas

* Drag steps on the canvas and connect their handles, or use the step list to edit without a mouse. Focused steps also move with the arrow keys.
* Select a step to edit its text, variables, wait time, condition and next step in the step inspector.
* Save a draft at any time, even before you have chosen a sender or audience. Unsaved changes are flagged, and if someone else saved a newer version, Entryway asks you to compare rather than overwrite.
* You can ask the agent to propose changes, such as rewriting every message in your voice. Proposals use the same saved version as the canvas and change nothing until you apply them.

## Review before activating

Before a sequence can run, the review shows:

* **What they'll receive:** the exact text, rendered for people in this audience
* **Sending:** the LinkedIn account, invitation pace and sending window
* **Safety:** stops when they reply, skips anyone already in a sequence, honors do-not-contact and exclusions, never sends a blank variable
* **Before you can activate:** anything that still needs attention

An owner, admin or reviewer approves the exact sequence version, sender, audience and text. An owner, admin or operator then activates it. Changing any of those after approval needs a new approval.

## After you activate

* **Enrollment status** shows each person's progress and anything blocking them.
* **Pause** a running sequence whenever you need to. To resume, review the paused people in small batches, approve that review and resume. A new batch needs a fresh review.
* Edits to a running sequence do not silently change people who are already enrolled.
* Completed actions are never replayed, and people who replied or were suppressed are not restarted.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.