Skip to content
Banyan Help

Sequence steps reference

This is the full reference for every step type that can appear in a sequence. Use it as a lookup when designing or debugging a campaign.

Action steps

Connection request

Sends a LinkedIn invite to the lead.

  • Optional: a note (≤ 300 chars). Notes can use personalization placeholders.
  • Cap: counts against your daily Connection requests limit.
  • Result: lead state becomes pending_connection. The next time Outpilot syncs (every few minutes), it detects accept/decline and the lead state moves to connected or not_connected.
  • Common branch: most sequences branch on this with if accepted:.

Send message

Sends a LinkedIn DM to the lead.

  • Requires: a 1st-degree connection. Outpilot will skip this step if the lead isn’t connected yet.
  • Optional: attachments (PDF, image), max 10 MB, sent inline as LinkedIn supports.
  • Cap: counts against your daily Messages limit.
  • Personalization: full placeholder support including {{customField.*}}.

Profile view

Visits the lead’s profile. The lead may see “Someone viewed your profile” depending on their privacy settings.

  • Cap: counts against your daily Profile views limit.
  • Use: gentle warmup — many leads accept invites faster after a view. Often paired with wait 1 day before a connection request.

Like a recent post

Likes the lead’s most recent feed post. If the lead has no recent posts (last 30 days), the step skips for that lead.

  • Cap: counts against your daily Post engagements limit.
  • Use: warmer than a profile view; signals genuine interest.

Comment on a recent post

Posts a comment on the lead’s most recent feed post.

  • Cap: counts against daily Post engagements.
  • Personalization: yes, including a placeholder for post topic.
  • Use: highest-touch warmup, but the comment must read naturally. Generic AI-feeling comments hurt more than help — pre-write 2–3 pattern templates.

InMail

Sends a LinkedIn InMail. Requires InMail credits on the connected account (Premium / Sales Navigator).

  • Cap: limited by your InMail credits, not Outpilot.
  • Use: when the lead has connection requests off, or when you want to bypass the connection step entirely.

Wait steps

Wait

Pauses the sequence for N hours/days/weeks before the next step.

  • Min: 1 hour. Max: 60 days.
  • Time math: respects business hours — if the wait expires at 2 a.m., Outpilot defers the next action until business hours start.
  • Use: between every action. Sequences without waits look mechanical.

Branch steps

Connection accepted?

Two-way branch on whether the lead’s pending invite was accepted.

  • Triggered by: a prior Connection request step.
  • If yes: continue down the accepted branch.
  • If no (after the wait window): continue down the not accepted branch.

Replied?

Two-way branch on whether the lead has replied to any of your messages in the campaign.

  • If yes: typically End (you take over manually).
  • If no: continue with another follow-up.

Verify Email (Instantly integration only)

Three-way branch:

  • Verified — Mailgun says the address is deliverable.
  • Not verified — undeliverable, unknown, or the lead has no email.

See Connecting Instantly for the full Verify Email reference.

Integration steps (Instantly only)

Add to Instantly campaign

Pushes the lead into a specific Instantly email campaign.

  • Requires: a verified email on the lead (skips otherwise).
  • Use: switch to email follow-up after LinkedIn connection fails.

Add to Instantly list

Pushes the lead into an Instantly list (no campaign yet).

  • No email required.
  • Use: collect leads for a future Instantly send.

Terminal steps

End

Stops the lead’s progression in this campaign. No further sends.

  • Use: at the end of any branch you want to terminate cleanly.
  • Note: leads that hit End are marked completed for this campaign; they can still be enrolled in other campaigns.

Skip vs. Fail vs. End

A lead at any step can have one of three outcomes:

  • Send / executed — happy path; advance to next step.
  • Skip — the lead doesn’t qualify for this step (e.g. Send message on a not-yet-connected lead). The lead advances to the next step without an attempt being made.
  • Fail — Outpilot tried, LinkedIn rejected (rate limit, restriction, account error). Outpilot retries with exponential backoff up to 3 times; if all fail, the lead is paused on this step and the campaign surfaces a warning. Fix the underlying issue and resume.

Activity tab on the campaign shows which outcome applied to each lead × step combination.