LinkedIn + email in one sequence

A Vaam sequence isn't tied to one channel. You build one sequence and drop in the steps you want, in the order you want. Vaam then runs those steps for every prospect enrolled, including a branch between LinkedIn and email based on what the prospect does.

What you can put in one sequence

A single sequence can combine:

• LinkedIn — connection request, message, profile visit, and liking or commenting on the prospect's post.
• Email — sent from your own connected Gmail or Outlook mailbox.
• Video — a recorded message, which can be personalized per prospect.
• Form — a quick form embedded in the sequence.
• Manual task — a step that lands in your task list instead of sending automatically, for anything that needs a human touch.
• Webhook — a step that notifies another system when it runs.
• Wait — a delay before the next step, measured in business days.

A typical shape

A common pattern looks like this:

1. LinkedIn connection request.
2. A wait step for the invitation to be accepted.
3. If accepted — a LinkedIn message, then a personalized video.
4. If not accepted after the wait period — an email instead.

The wait for invitation isn't a fixed delay you have to guess at. It's a real branch point, with separate paths configured for "accepted" and "not accepted."

Replies pause the sequence

If a prospect replies — on LinkedIn or by email — that prospect's sequence pauses and a task appears for you. Nothing further sends on that prospect until you open the task and choose to continue the sequence or end it. This applies regardless of which channel the reply came in on. A LinkedIn reply doesn't get missed just because the next scheduled step was an email.

What still counts toward the LinkedIn prospect limit

Mixing channels doesn't create an exception to Vaam's LinkedIn prospect limit. Any sequence that includes at least one LinkedIn step counts toward the limit, even if most of its steps are email. A sequence built entirely from email steps does not count, and can hold as many active prospects as you want. See Safe LinkedIn automation for how that limit relates to LinkedIn account risk.

One sequence per language

If you write to prospects in more than one language, build a separate sequence per language rather than branching language inside one sequence — the steps themselves are plain text, not templated for multiple locales.