This is a reference for every block (node) you can drag onto the campaign builder canvas, including its outcome paths and key settings. For message content and AI settings shared across blocks, see "Writing messages & the AI Builder".
Where to find it
Open your campaign → Campaign Builder tab. Blocks live in the Actions section of the left palette.
Connection Request 🤝
Sends a LinkedIn connection request. Only available on the Not Connected path, where it's the typical starting block.
Message options: an AI-personalized note, a template note, or No message (blank invite).
A character counter keeps the note within LinkedIn's invite limit.
Outcome paths (three handles):
🟢 Accepted & Replied — the invite was accepted and the candidate replied.
🟡 Accepted (No Reply) — accepted, but no reply yet.
🔴 Not Accepted — no response to the invite within the connector's delay.
Send Message 💬
Sends a regular LinkedIn message. Use it as the first step on the First Degree path, or as a follow-up after an accepted connection request.
Use AI Agent for personalized messages, or write a Template Message per language.
Send manually — instead of sending automatically, generated messages go to a manual queue you can copy via the browser extension.
Outcome paths (two handles):
🟢 Replied — the candidate answered this message. Connect a Conversational Agent here to keep the conversation going automatically.
🔴 No Response — continue if the candidate doesn't reply within the delay.
Send InMail 📧
Sends a LinkedIn InMail — reaches candidates without a connection.
Subscription — select your LinkedIn subscription type: LinkedIn Premium, Sales Navigator, or Recruiter. This determines how the InMail is sent.
InMail Subject and InMail Body (AI or template, per language).
InMail visibility (Recruiter): Private — only you, or Team-visible so other Recruiter users in the same dashboard can see the InMail.
Automatic Follow-Up (if enabled for your account) — LinkedIn Recruiter's native follow-up, sent by LinkedIn itself 3–28 days later if there's no reply. Note: LinkedIn schedules it at send time and it can't be cancelled or edited afterwards; it requires Recruiter Corporate or RPS+.
Outcome paths: 🟢 Replied / 🔴 No Response.
Send E-Mail 📨
Sends an email to the candidate's enriched email address.
Select the email account to send from.
Email Subject and Email Body (AI or template, per language).
In AI mode you can design an Email layout (HTML wrapper) — greeting, signature, footer — with the
{{ai_agent_message}}placeholder marking where the AI-generated body appears. An Inbox preview shows the final result.Outcome paths: 🟢 Replied / 🔴 No Response.
💡 Tip: Email and WhatsApp steps need enriched contact details. If a campaign starts with one of these channels, enrich your profiles first — the publish check will tell you if none of the selected profiles have the required details.
Send Whatsapp Message 📱
Sends a WhatsApp message to the candidate's enriched phone number.
Select the WhatsApp account to send from.
AI or template message per language, plus a Send manually option.
Outcome paths: 🟢 Replied / 🔴 No Response.
Cancel Connection Request ❌
Withdraws the pending LinkedIn connection request if it hasn't been accepted by the time this step runs — useful to keep your pending-invites count healthy before switching channels (e.g. InMail or email).
No settings to configure. The waiting period before withdrawal is the delay on the incoming connector.
Outcome path: Connection Request Cancelled — continues to the next step.
Call Webhook 🔗
Sends a signed HTTP request to an external endpoint when the step runs — for example to notify Zapier, your ATS, or a Slack workflow.
Webhook endpoint — pick an existing endpoint or use Create new endpoint (name + URL). The endpoint's signing secret is shown once at creation — copy it then.
Custom parameters — up to 20 key/value pairs included in the payload. Values support profile variables:
{{firstname}},{{lastname}},{{currentcompanyname}},{{linkedinurl}},{{email}}, and{{phonenumber}}(unknown placeholders are left as-is).Delivery is fire-and-forget — the workflow continues immediately regardless of the delivery outcome.
Outcome path: Webhook called — continues to the next step.
Conversational Agent 🤖
Takes over the conversation once a candidate replies. Connect it to a green response handle — Accepted & Replied on a Connection Request, or Replied on any message block. The agent answers on the candidate's channel, works toward your goal, and can book meetings directly in your Cal.com calendar. Full details in the dedicated article "The Conversational Agent — automatic follow-ups and scheduling".
Agent goal type: Schedule a meeting (Cal.com required) or Custom goal.
Require approval before sending — when on, each agent reply is drafted for review before it is sent.
Maximum conversation turns — the agent escalates to a human after this many turns without reaching the goal.
Escalation instructions — describe when and how to escalate to a human recruiter.
Outcome paths: none — the agent is the end of the automated sequence; the conversation continues turn by turn until the goal is reached, the candidate opts out, or it's escalated to you.
Shared options and behavior
Attach PDF — the Send Message, Send InMail, Send E-Mail, and Send WhatsApp blocks can carry a PDF attachment (max 10MB). Use it for a job description or company one-pager.
Every connector between two blocks carries a delay: a number plus min / hrs / days. Click the connector to change it.
On response-style paths the delay doubles as the waiting window: "🔴 No Response, 3 days" means "if no reply within 3 days, continue".
If a candidate replies at any point, the automated sequence for that branch stops and the conversation moves to your Inbox — unless the block's 🟢 Replied path is connected (for example to a Conversational Agent), in which case the reply continues the workflow along that path.
Path colors: 🟢 accepted & replied / replied, 🟡 accepted without reply / skipped, 🔴 no response / not accepted.
FAQ
Which blocks can start a sequence? On Not Connected: Connection Request, Send InMail, Send E-Mail, or Send WhatsApp. On First Degree: Send Message, Send InMail, Send E-Mail, or Send WhatsApp.
Can I mix channels in one sequence? Yes — a common pattern is Connection Request → (not accepted) → Cancel Connection Request → Send E-Mail.