LinkedIn + Browserflow: send invites without tab chaos
You start with good intentions. Then LinkedIn turns into 30 open tabs, duplicate profiles, and that low-grade anxiety that you’ve already invited this person.
Sales reps feel it when pipeline is thin. Recruiters hit it when they’re sourcing at volume. And if you run an agency, you’ve probably built (and rebuilt) a LinkedIn invite automation process that still relies on someone babysitting a browser.
This workflow uses n8n plus Browserflow to pull profiles, check connection status, and send invites in controlled batches. You’ll learn what it does, what you need, and how to run it safely.
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: LinkedIn + Browserflow: send invites without tab chaos
flowchart LR
subgraph sg0["When clicking ‘Test workflow’ Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "When clicking ‘Test workflow’", pos: "b", h: 48 }
n1@{ icon: "mdi:swap-vertical", form: "rounded", label: "Loop Over Items", pos: "b", h: 48 }
n2@{ icon: "mdi:swap-vertical", form: "rounded", label: "Split Out", pos: "b", h: 48 }
n3@{ icon: "mdi:cog", form: "rounded", label: "Check if person is a connect..", pos: "b", h: 48 }
n4@{ icon: "mdi:cog", form: "rounded", label: "Send Connection invite", pos: "b", h: 48 }
n5@{ icon: "mdi:cog", form: "rounded", label: "Scrape profiles from a linke..", pos: "b", h: 48 }
n6@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Check Connection Status", pos: "b", h: 48 }
n2 --> n1
n1 --> n3
n4 --> n1
n6 --> n1
n6 --> n4
n3 --> n6
n0 --> n5
n5 --> n2
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
class n6 decision
Why This Matters: LinkedIn outreach breaks when it’s manual
Sending connection invites sounds simple until you do it every day. You search, open profiles, check if you’re already connected, copy a name into a spreadsheet, paste a message, then repeat. The repetitive part is bad enough, but the real cost is inconsistency. One day you send 40 invites, the next day none because you got pulled into meetings, and suddenly outreach becomes “when I have time” instead of a dependable channel. And frankly, the tab chaos makes it easier to make mistakes, like inviting the same person twice or forgetting who you already messaged.
It adds up fast. Here’s where it usually breaks down in real life.
- You lose about 1–2 hours a week just switching tabs, checking profiles, and trying not to duplicate work.
- Existing connections slip through, which means wasted invites and awkward follow-ups.
- Outreach volume spikes and dips because a human has to push every button, every time.
- There’s no clean handoff from “found a lead” to “invite sent,” so tracking ends up scattered.
What You’ll Build: a controlled LinkedIn invite loop that skips existing connections
This workflow starts when you manually launch it in n8n, so you stay in control. Browserflow then runs a LinkedIn search flow and returns a list of profile links that match your targeting (role, industry, location, keywords, whatever you searched for). n8n splits that list into individual items and processes them one-by-one in a loop. For each profile, it checks whether you’re already connected. If yes, it skips. If not, it sends a connection request, optionally with a short message, then moves on to the next profile. The end result is steady outreach without you living inside a browser session.
The workflow begins with profile discovery in Browserflow. Then n8n handles batching and decision-making, so you don’t “spray and pray” invites all at once. Finally, Browserflow sends the invite only when the connection status check says it’s safe.
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Say you invite 30 new prospects a day. Manually, you might spend about 2 minutes per person between opening the profile, checking connection status, and sending the request, so you’re at roughly 1 hour daily. With this workflow, you kick it off in n8n (maybe 5 minutes to confirm the search and batch size), then Browserflow runs the loop in the background. You still review outcomes, but you’re not clicking through 30 profiles one-by-one, and you stop wasting invites on people you already know.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Browserflow for LinkedIn (community node) to scrape and send invites.
- LinkedIn account to run the outreach.
- Browserflow API key (get it from your Browserflow dashboard).
Skill level: Beginner. You’ll mostly be connecting credentials, adjusting targeting, and choosing a safe batch size.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
You launch it when you’re ready. The workflow uses a Manual Trigger, so nothing runs on autopilot until you hit “Test workflow.” That makes it easier to stay compliant with internal outreach policies and to avoid running during odd hours.
Browserflow collects the profiles. The “Retrieve LinkedIn Profiles” action runs your LinkedIn search and returns a list of profile links (and usually basic profile attributes, depending on your Browserflow setup).
n8n processes one profile at a time. The list is split into individual records, then “Loop Over Items” (Split in Batches) iterates through them so you don’t hammer LinkedIn with simultaneous actions.
Connection status decides what happens next. For each profile, Browserflow checks if you’re already connected. The If node gates the next action, so connected profiles are skipped and only net-new prospects receive an invite.
You can easily modify your targeting and batch size based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Manual Trigger
Set up the workflow to start manually so you can control when LinkedIn scraping and outreach begins.
- Add the Manual Launch Trigger node at the start of the workflow.
- Leave all settings as default since this trigger runs when you click Execute Workflow.
- Connect Manual Launch Trigger to Retrieve LinkedIn Profiles.
Step 2: Connect Browserflow and Pull Profiles
Configure the LinkedIn profile search and attach Browserflow credentials for scraping.
- Open Retrieve LinkedIn Profiles and set Operation to
scrapeProfilesFromSearch. - Set Search Term to
Content Marketeer, City toAmsterdam, and Country toNetherlands. - Credential Required: Connect your
browserflowApicredentials. - Connect Retrieve LinkedIn Profiles to Extract Records.
Step 3: Split and Iterate Through Search Results
Break the scraped results into individual records and process them one at a time.
- In Extract Records, set Field to Split Out to
data. - Connect Extract Records to Iterate Through Records.
- In Iterate Through Records, set Batch Size to
=1to process one profile at a time. - Ensure Iterate Through Records outputs to Verify Connection Status on the second output (Continue).
Step 4: Verify Status and Gate Invitation Sending
Check each profile’s connection status and decide whether to send an invitation.
- Open Verify Connection Status and configure the Browserflow action needed to inspect the current profile’s connection state.
- Credential Required: Connect your
browserflowApicredentials in Verify Connection Status. - In Connection Status Gate, confirm the boolean conditions use
{{ $json.is_connection }}and{{ $json.is_pending }}with the operator set tofalsefor both checks. - Connect Verify Connection Status to Connection Status Gate.
Execution Flow Note: Connection Status Gate routes profiles that are not connected and not pending to Dispatch Connection Invite, while all results loop back to Iterate Through Records for the next batch.
Step 5: Send Connection Invites and Loop Batches
Send the connection request and return to the batch iterator to continue through all profiles.
- Open Dispatch Connection Invite and configure the Browserflow action that sends a LinkedIn connection request.
- Credential Required: Connect your
browserflowApicredentials in Dispatch Connection Invite. - Connect Connection Status Gate (false branch) to Dispatch Connection Invite.
- Connect Dispatch Connection Invite back to Iterate Through Records so the workflow continues with the next profile.
Step 6: Test and Activate Your Workflow
Run a manual test to confirm profile scraping, status checks, and invitation dispatching all work as expected.
- Click Execute Workflow on Manual Launch Trigger to start a test run.
- Verify that Retrieve LinkedIn Profiles outputs results, Extract Records splits them, and Iterate Through Records processes each profile one by one.
- Confirm Verify Connection Status and Connection Status Gate properly route profiles and that Dispatch Connection Invite only runs for non-connected, non-pending profiles.
- When satisfied, toggle the workflow to Active for production use.
Troubleshooting Tips
- Browserflow credentials can expire or need specific permissions. If things break, check your Browserflow API key and connected LinkedIn session in the Browserflow dashboard first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Quick Answers
About 30 minutes if Browserflow is already connected to LinkedIn.
No. You’ll install the Browserflow community node and paste in your API key. After that, it’s mostly configuration (search targeting, batch size, and your invite message).
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Browserflow costs (it offers a free trial, then paid plans).
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and you should. Most people swap targeting inside “Retrieve LinkedIn Profiles” (different search keywords, locations, roles), then adjust “Iterate Through Records” to control batch size. You can also tweak “Dispatch Connection Invite” to add a personalized note, but keep it short because LinkedIn limits how many custom-message invites you can send per month. If you want this to run daily, replace the Manual Trigger with a schedule trigger and keep the same connection-check gate.
Usually it’s an expired Browserflow API key or a LinkedIn session that got disconnected inside Browserflow. Refresh the key, re-auth the LinkedIn connection in Browserflow, then reselect the credential in each Browserflow node. If it fails only after several profiles, it can also be throttling; reduce your batch size and run fewer profiles per execution.
Practically, you should keep it to small daily batches (think a few dozen invites) to stay consistent and avoid account risk. On n8n Cloud, your execution limit depends on plan, and self-hosting has no hard execution cap (it depends on your server). The workflow processes profiles sequentially, so it scales by running more often, not by running everything at once.
Often, yes, because this is browser-driven automation with branching logic and batching. Zapier and Make are great for app-to-app workflows, but they’re not built for “open LinkedIn, scrape results, check status, then click invite” style execution. n8n also makes it easier to loop through leads one at a time, which keeps outreach steadier. The tradeoff is setup: you need Browserflow configured correctly and you’ll want to test carefully. If you’re unsure, Talk to an automation expert and we’ll point you to the simplest option.
Once this is running, LinkedIn outreach stops being a daily wrestling match. You press go, invites move in steady batches, and your attention goes back to conversations that actually turn into revenue.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
