Skip to main content
A sequence is the path each lead follows: the steps, the waits between them, and the branches depending on what the lead does. Only Owners and Managers can create or edit sequences. Everyone else sees them read-only.

​
Create one

Go to Sequences and click New sequence. Choose how to start:
  • Start from a template: a ready-made flow for connecting, following up, rotating senders or nurturing. See Sequence templates.
  • Build from scratch: an empty canvas with just a start and an end.
Enter a Name (for example Founders: invite + 2 follow-ups) and an optional Client, then click Create and open. The Sequences list shows each sequence’s status, sender pool and counts (live, completed, replied, sent, queued). From the … menu you can Duplicate, Archive, or Delete a sequence. Only draft or archived sequences can be deleted.

​
The builder at a glance

The top row shows the sequence name, its status and version, and whether your draft is saved. On the right are Discard draft, Save or Publish, and Activate, Pause or Resume. Under it, six tabs split the sequence into parts:
The open tab is kept in the page address, so a reload or a shared link opens the same tab.
Changes on the Senders and Settings tabs go into the same draft as your step changes. Save or publish them from the top row.

​
Steps: build the flow

Steps run from top to bottom. When a step has more than one outcome, its branches fan out underneath it, each with a coloured label such as connected or no connect. The layout is done for you: steps always sit under the step they follow, and you cannot drag them around.
1

Add a step with +

Every line between two steps, and every branch that does not lead anywhere yet, has a + button. Click it to open Add a step on the right.Steps are grouped as LinkedIn actions, Conditions and timing, Update the lead, Team and AI and Connect other tools. Each one has a short explanation, and you can search by name. The new step is connected for you. If you add it on a line, the line carries on to the step that followed.See the step reference for what every step does.
2

Only steps that fit are offered

Steps that make no sense at that point are greyed out, with the reason underneath. The picker looks at every step above the +, including which branch the lead took. For example:
  • Send message needs a connection first. It becomes available after Wait for connection on the connected branch, or after an Already connected? condition on its true branch.
  • Send invitation is greyed out where the lead is already connected, and where an invitation was already sent on that path and not withdrawn.
  • Wait for connection and Withdraw invitation need an invitation above them.
3

Configure the step

Click a step to open its settings on the right. There you set the message text, the Wait before this step delay (1 day ±20% by default), and How this step runs:
  • Auto runs inside the sender’s schedule and budgets.
  • Manual creates a task, and the step runs when a teammate completes it.
The delay shows on the canvas as Wait 3 days, then above the step. Use Duplicate or Delete at the bottom of the panel. You can also select a step and press Delete.
4

End every path

Every path must finish at an End step or hand the lead to another sequence.
5

Save, or publish

On a sequence that has never had leads, Save (Ctrl/⌘ + S) writes the steps and creates a version.Once it has had leads, your edits go into an auto-saved draft and the button becomes Publish, which first shows you who the change affects. See Drafts and publishing.

​
Moving around the canvas

Once leads are running, each step card shows how many actions are queued, sent, accepted, replied, failed and skipped. Click the failed or skipped count to see those leads and why. See Recover failed leads.

​
Senders tab

​
Settings tab

On a sequence that has leads, these take effect when you publish.

​
AI brief

Brief for AI is the background the AI uses when drafting copy and checking the sequence: who you are, who you target, the offer and the tone. It sits at the top because every AI feature in the sequence reads it.

​
When a lead replies

Stop the sequence for that lead is on by default. Then choose the scope:
  • Stop this lead everywhere (default): a reply on any channel, to any sender, stops every sequence that lead is in. This is what you want: an email reply should stop the LinkedIn follow-up too.
  • Only stop the sender they replied to: other senders and mailboxes keep going. Rarely what you want.

​
After a reply

  • Exit the lead (default): the sequence ends and you carry on in the Inbox.
  • Hold for review: the lead waits on the attention list, and one click resumes the sequence or exits the lead. Set Exit held leads after (days), 30 by default, so nobody is held forever.

​
Out-of-office replies

Resume the lead later is on by default, after 7 days. If the auto-reply names a return date, that date is used instead. Turn it off and an out-of-office ends the sequence like any other reply.

​
Before the first step

  • Wait for profile enrichment before the first step: the lead starts once its profile data has arrived, or after 72 hours, whichever comes first.
  • Hold leads until AI-written lines are approved: the lead waits instead of sending the fallback text.

​
General

​
Letting AI draft copy

Send invitation, Send message and Comment on post have a Let AI draft option with an AI brief field. You can also use the AI draft + approval step. AI drafts are never sent on their own. Each one becomes a Review AI draft task, where a teammate edits, approves or rejects it. See Tasks.

​
Checks while you build

The bar at the bottom of the Steps tab says Everything looks good, or how many things to fix and suggestions there are. Open it to see each one in plain words, with the step it is about and a Show me button that zooms to that step. Things to fix are red. Suggestions are amber.
  • An invitation note is too long: 300 characters, or 200 if a free LinkedIn account is in the pool. Spintax is measured at its longest combination.
  • A message, comment or InMail is over its limit.
  • Wait for connection has no connected branch.
  • A path never reaches an End step.
  • A step leads to a step that no longer exists.
  • There’s a Send email step, but no mailbox in the pool.
  • A Send message step has nothing before it that proves a connection (an invitation and wait, an InMail, or an Already connected? condition), and isn’t set to send always.
  • A step has more than 5 variants, or its variant weights are all zero.
  • An A/B split or AI routing step has a branch with nothing connected.
  • A condition is missing its true or false branch.
  • AI drafting is on, but there’s no brief.
  • A tag, list, stage, sequence or webhook hasn’t been selected.
  • A step isn’t connected to the sequence, so no lead will ever reach it.
  • An email step has no {{unsubscribe_link}}.
  • A voice-note step has a pool sender with no recorded clip.