LinkedIn outreach workflows
with n8n and BeReach.

LinkedIn prospecting alone isn't enough. You need it connected to everything else.

Most LinkedIn prospecting tools exist in isolation. You find leads, get replies, then manually copy data into your CRM, notify your team on Slack, and follow up by email. The LinkedIn part is covered. Everything around it isn't.

n8n solves this. It's an open-source workflow automation platform (think Zapier, but self-hostable and more powerful) that connects 500+ tools through a visual node-based interface. When you combine n8n with BeReach's LinkedIn prospecting, you build systems where LinkedIn lead discovery is connected to everything else in your sales stack.

Here's what that looks like in practice.

Why this combination works

n8n handles orchestration: when something happens in one tool, trigger actions in others. It's the glue between your tools.

BeReach handles LinkedIn: find warm prospects, draft messages you review and approve, and surface who's engaging. It provides the LinkedIn layer that n8n doesn't have natively. If you are weighing that layer against a raw LinkedIn API, see our BeReach vs Unipile comparison for LinkedIn outreach.

Together they solve the two problems that kill outreach productivity:

1. Manual data transfer between tools (copying prospects from LinkedIn to HubSpot)
2. Missed timing (a prospect replies on LinkedIn but nobody notices for two days)

Four workflows that actually save time

Workflow 1: New LinkedIn reply to Slack alert and CRM update

The problem: Your team runs LinkedIn campaigns but doesn't check for replies consistently. Hot prospects go cold because nobody responded for 48 hours.

The workflow:

1. BeReach webhook fires when a LinkedIn message arrives
2. n8n receives the webhook and reads the prospect's name, company, and message
3. n8n sends a Slack message to your sales channel with the prospect details
4. n8n creates or updates a contact in HubSpot with the interaction logged
5. If the message contains keywords like "interested" or "schedule", n8n sends a priority alert

Result: Your team sees LinkedIn replies within seconds, not hours. Nobody falls through the cracks.

Workflow 2: CRM deal stage change to timely LinkedIn touchpoints

The problem: When a deal moves to "Proposal Sent" in your CRM, the relationship goes quiet while the prospect evaluates. You want to stay visible without being pushy.

The workflow:

1. HubSpot deal moves to "Proposal Sent"
2. n8n triggers and reads the prospect's recent LinkedIn activity via BeReach
3. n8n posts a Slack summary of what they've been posting and engaging with
4. 3 days later, n8n reminds you to engage with their recent content from your own account
5. 7 days later, if the deal hasn't moved, BeReach drafts a follow-up message and n8n pings you to review and approve it

Result: You show up naturally during their evaluation period with informed, timely touches instead of a "just checking in" message.

Workflow 3: New blog subscriber to LinkedIn connection

The problem: Someone signs up for your newsletter or downloads a resource. They're interested but you don't connect with them on LinkedIn.

The workflow:

1. New subscriber added in Mailchimp/ConvertKit
2. n8n reads their name and company
3. n8n looks up their LinkedIn profile through BeReach
4. If found, BeReach drafts a connection note referencing the content they downloaded
5. n8n adds the draft to your review queue and pings you on Slack
6. You review the note, tweak it if needed, and send the request from your own account

Result: Every inbound lead gets a ready-to-send LinkedIn touch within a day, turning email subscribers into multi-channel relationships.

Workflow 4: Daily engagement signal digest

The problem: BeReach finds engagement signals (post likes and comments) but you want a single daily summary instead of real-time notifications.

The workflow:

1. n8n runs a scheduled workflow every morning at 8am
2. Pulls recent engagement data from BeReach
3. Filters for high-intent signals (comments > likes, multiple engagements > single)
4. Formats a daily digest email with prospect name, signal type, and suggested action
5. Sends to the responsible team member

Result: Your team starts each day with a prioritized list of warm prospects to reach out to.

Put the idea to work

Less searching.
More conversations.

Tell Vera who you want to reach. Review the first message. Take it from there.

Ask Vera to find leads

Getting started

What you need

The BeReach Pro plan includes webhooks and full workflow access. See the BeReach pricing page for the full breakdown, including the Max and Max+ tiers for larger teams.

How to connect them

BeReach's webhooks and n8n's HTTP Request nodes are how the two tools communicate. n8n can both receive events from BeReach (incoming messages) and trigger work in BeReach (find prospects, prepare message drafts).

n8n's visual interface means you can build these workflows without writing code. Drag nodes, connect them, set conditions. If you can use a flowchart, you can build an n8n workflow.

Start simple

Don't build all four workflows on day one. Start with Workflow 1 (LinkedIn reply notifications). It takes 15 minutes to set up and delivers immediate value. Once that's running reliably, add workflows based on what eats the most manual time in your process.

When n8n workflows aren't the right answer

n8n + BeReach is powerful for connecting tools. But if all you need is LinkedIn prospecting (finding leads and drafting each message), BeReach's built-in AI agent handles that without n8n.

Use n8n when:

• You need LinkedIn connected to other tools (CRM, Slack, email, databases)
• You want custom logic (if prospect is in industry X, use message template Y)
• You're building a multi-channel sales system

Use BeReach alone when:

• You just need LinkedIn prospecting to work
• The AI agent's built-in searches and campaigns cover your use case
• You don't want to maintain workflow infrastructure

If you'd rather drive BeReach from an AI assistant than build node graphs, you can also connect it to Claude directly. See our guide to setting up the LinkedIn MCP server for Claude.

Frequently asked questions