Build a LinkedIn and email sequence

New campaigns prefill from your onboarding goal. Keep the playbook for a first launch. Open the canvas when you need branching, or when you want Connect, then email.

Sequences explains the graph model. Review flags and hold to launch covers the launch gate (runnable step, clean rows, capacity). Handle replies so sequences stop covers what happens when someone replies.

Playbook vs canvas

LinkedIn packs (goal playbooks):

• Founder intro
• Book a demo
• Recruiter reach-out
• Light network

Graph packs (email-aware):

• Connect, then email (this section walks through it)
• Demo, then email
• Recruit, then email

Connect, then email path:

1. View profile
2. Connection request
3. Wait (default 7 days) on Accepted your invite?
4. Yes → Message on LinkedIn
5. No → Email

That email branch is how you keep talking when the weekly invite cap is hit, without adding another LinkedIn account.

Worked path: Connect, then email

1. On the campaign Sequence tab, apply Connect, then email.
2. Connect a mailbox on Senders → Email (/accounts/email): Google, Microsoft, or IMAP via the same hosted wizard as LinkedIn. Without a mailbox, the email branch will not send.
3. Confirm Message and Email copy are filled. Missing copy shows as a canvas warning before launch.
4. Hold to launch when the roster is clean (Review flags and hold to launch).

You do not need a custom graph for a first campaign. This pack is still the shortest way to see LinkedIn plus email without inventing nodes from scratch.

What each step does on LinkedIn

Canvas label	What happens
View profile	They can get a "viewed your profile" notification. Also how we turn /in/slug into an internal id before later steps.
Follow	Follows their LinkedIn profile.
Like post / Comment on post	We take their latest eligible post and like or comment on it. Comment defaults to Held for per-prospect review.
Connection request	Optional note, 300 characters. No note is valid. If they are already a connection, we skip the invite.
Message	LinkedIn only starts a chat with a relation. No invite upstream → Won’t run yet.
Email	Needs an address and a mailbox. No address → skipped.

View, Follow, and Like run after launch once the graph reaches them. Comments stay held for review by default so you see the text before it posts.

Conditions (and why accept waits days)

• Accepted your invite? LinkedIn does not push accepts; detection can lag hours. That is why the wait is measured in days, not minutes.
• Has an email address? Checked immediately.
• Replied? Yes is a terminal: Sequence stops / Prospect replied. You cannot continue the graph on Yes. Inbox is where you take over.

Unmet wait takes the No branch. Do not shrink the accept wait to "same day" expecting Instant Accept notifications. They are not reliable.

InMail fallback (not a canvas node)

Playbooks carry InMail copy. After an invite, if they have not accepted by the wait window, we may send InMail when the sender has Premium, Sales Navigator, or Recruiter credits, or when the profile is Open (free). Accept cancels the pending InMail. No credits and not open → skip.

There is no InMail step to drag onto the graph. Fallback rides on the playbook; you cannot place it as a free-form node.

Warnings the canvas already shows

• Missing Message / Email / Comment copy
• Email node only reachable on the no-email branch
• Message with no Connection request upstream (Won’t run yet)
• Launch requires a runnable step (not Message-only)

Fix those before you chase Review flags. A Message-only graph will never enable Hold to launch.

Variables

{{first_name}}, {{company}}, {{role}}, {{sender.signature}}. Empty fields become empty strings, then flags on Review.

Related: Personalization, Launch your first campaign, Add the right people to a campaign.