Sequences let you combine email and LinkedIn steps, with conditional branching, into a single outreach flow. This article walks through building one from scratch.
Step 1: Create a sequence
In the left sidebar, click Sequences (under Outreach).
Click Add sequence in the top right.
Pick a starting point: Custom sequence for a blank canvas, or a template such as 3-step email outreach, Just LinkedIn, Multichannel combined outreach, Prioritize email, or Prioritize LinkedIn.
If you picked a template, review it in the preview modal and click Use template to load it into the builder.
Step 2: The builder canvas
Every sequence starts from a Sequence start node. Below it, steps run in order, each separated by a Delay (in days) that controls how long to wait after the previous step before this one fires.

Each step shows which channel it uses (an email icon for email steps, a LinkedIn icon for LinkedIn steps) and lists its variants (A, B, C, and so on) for A/B testing.
Step 3: Adding a step
Click the + between any two steps (or right after Sequence start) to open the step picker. Steps are grouped by:
Email: Send email
LinkedIn: Request connection, Send message, InMail message, Withdraw connection request, View profile, Follow contact, Like latest post
Universal / Actions: available regardless of channel
Conditions: branch the sequence based on contact data or behavior, for example Has email, Email bounced, Is email validated, Has LinkedIn URL, If connection accepted

This is what makes a sequence multichannel: you can mix email and LinkedIn steps, or add conditional branches, all in the same flow. A sequence can also be email only or LinkedIn only.
Step 4: Writing an email step
Click into a Send email step to open its editor. You will see:
Subject: the subject line. You can insert variables using Variables, and can use Autospintax to auto-generate wording variations for deliverability.
Body: the email content, with Templates, Variables, Autospintax, formatting, links, images, and an HTML/code view.
Spam check, Send preview, and Save as template at the bottom.

On a follow-up step (any step after the first), the Subject field defaults to empty. If you leave it empty, the follow-up email sends in the same thread as the previous step. If you type a subject instead, it sends as a separate email with a new subject line.
Step 5: Adding contacts
Open the Contacts tab inside the sequence and choose how to add people:
Existing contacts: pick from contacts already in your workspace
Leadsforge: pull from Leadsforge's 500M+ contact database
Google sheet URL: import directly from a Google Sheet
Upload a CSV file: drag and drop or browse (max 100,000 rows). See Importing contacts into Salesforge using CSV file for the column-mapping and custom-variable steps.

Adding contacts is a two-step Select, then Validate flow. After you select contacts, Salesforge runs email validation and splits the results into Safe and Unsafe tabs before you confirm and add them to the sequence. This uses 1 validation credit per contact. See Understanding Salesforge Credits.
Step 6: Sequence settings
The Settings tab controls how the whole sequence behaves:
Schedule: timezone and sending window (days and hours)
Sending priority: whether new contacts or follow-ups get sending capacity first. See Sending Priority: New Contacts vs Follow Ups.
Multithreading: Stop on reply from company, Sequential sending within a company, Set a company limit
Email only: CC and BCC, Pause on click, Pause on open
Deliverability: Bounce shield, Plain Text, Email service provider (ESP) matching
Opt-out of emails: Custom opt-out at the bottom, with a Type of Hyperlink or Text, plus an optional Localized opt-out link that auto-translates the unsubscribe link into the recipient's language. See Localized Opt-Out Link.
Tracking: Track opportunities, Track open rate, Track link clicks (open and click tracking are not recommended, since they can affect deliverability)


Step 7: Subsequences
The Subsequences tab lets you automatically move a contact into a follow-on sequence based on how they were labeled in Primebox after replying. See Subsequences for the full setup.
Related articles