Resources · Make integration

Browserflow for LinkedIn Make integrationAutomate Browserflow for LinkedIn with Make.

Can LinkedIn outreach run without you clicking every profile by hand? The Browserflow for LinkedIn Make integration gives you 8 action modules: scrape profiles, read their data, send invites and messages. This guide is for sales and recruiting teams, and it walks you to a working first scenario.

Try the Browserflow for LinkedIn integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Browserflow for LinkedIn Make integration actually do?

The Browserflow for LinkedIn Make integration lets a Make scenario (the automation you build, a chain of steps) do the LinkedIn chores you usually do in a browser tab: pull profiles from a search or a post, read a profile, check whether someone is already a connection, then invite or message them. Each step is a module, one brick of the scenario.

A search that fills your pipeline. A recruiter looking for data engineers in a given city starts with Scrape Profiles From a LinkedIn Search, passes each result to Get Data From a Linkedin Profile, and sends the rows to a spreadsheet or a CRM. The shortlist builds itself.

Warm leads from a post. Someone published a post that drew comments from exactly your buyers. Scrape Profiles From a LinkedIn Post collects the commenters, Check if a Person is a Connection filters out the people you already know, and Send a Linkedin Connection Invite reaches the rest.

A clean record of every conversation. Before handing an account to a colleague, Export LinkedIn Chat History pulls the thread with that connection so nothing gets lost in the handover.

What the app does not have: a trigger. No module watches LinkedIn and starts the scenario on its own, so you start it from another app or from the Make schedule. Make publishes no limits for this app, so test on a few profiles before you point a scenario at a large list. If a Make concept still feels fuzzy, the Make training covers the basics, and the Make review helps you judge the tool as a whole.

The same app exists on n8n. The Browserflow for LinkedIn n8n integration page covers the same app on n8n, and n8n vs Make lays out the differences between the two platforms.

Connect

How do you link your Browserflow account to Make?

  1. 01

    Add a Browserflow module

    In your scenario, click the +, type Browserflow for LinkedIn in the search box and pick any module. Then click Create a connection. A connection is your account linked to Make once, and every Browserflow module reuses it.

  2. 02

    Name it and authorize

    Give the connection a name if you like, for example the name of the LinkedIn account it drives. Then follow what the window asks: either authorize Make on the Browserflow page, or paste the key Browserflow gives you.

  3. 03

    Save and check

    Click Save. The connection now appears in the module's dropdown. From here, every other Browserflow for LinkedIn module you add to any scenario can pick the same connection, with no second setup.

First scenario

Your first scenario: invite the people who commented on a post

GoalWhen you point Make at a LinkedIn post, it collects the commenters and sends each one a connection invite.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. Since Browserflow has no trigger, the first module here is an action, and the schedule will start it.

  2. 02

    Add the post scraper

    Search Browserflow for LinkedIn, choose Scrape Profiles From a LinkedIn Post, pick your connection and fill in the post it should read. Each commenter comes out as a bundle, one item passed to the next module.

  3. 03

    Add the invite

    Click the + to the right of the scraper and add Send a Linkedin Connection Invite. Map the profile from the previous module into it, so each commenter receives their own invite.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received. Check who got an invite before you go further: these are real invites, sent under your name.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, and the Free plan allows no shorter interval. Pick the rhythm that suits you, then switch the scenario on.

Modules

The 8 Browserflow for LinkedIn modules, one by one

Browserflow for LinkedIn gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Browserflow for LinkedIn1

Check if a Person is a Connection

Action

In Make“Checks if a LinkedIn profile is a first degree connection or if the invite is pending”

Tells you whether a LinkedIn profile is already a first-degree connection, or whether your invite is still waiting for an answer.

When to use it
right before an invite step, so a prospect who already accepted, or who has an invite pending, does not get a second one.
Watch out
add a filter after this module, otherwise the answer is read but nothing changes in the flow.
Browserflow for LinkedIn2

Export LinkedIn Chat History

Action

In Make“Exports all messages send to and received from a LinkedIn Connection”

Pulls every message exchanged with one LinkedIn connection, sent and received, so the conversation can live outside LinkedIn.

When to use it
when a deal moves into your CRM and you want the full LinkedIn thread attached to the contact record.
Watch out
it only works with people who are already connections, so pair it with Check if a Person is a Connection on doubtful lists.
Browserflow for LinkedIn3

Get Data From a Linkedin Profile

Action

In Make“Retrieves data from a LinkedIn profile. This module works for both company and person profiles.”

Reads a LinkedIn profile and hands its data to the next module. It accepts company pages as well as personal profiles.

When to use it
after a scraping step, to turn a bare list of profile links into usable rows before they reach a spreadsheet or a CRM.
Watch out
every profile read is one operation, the unit Make counts on your plan, so a long list adds up.
Browserflow for LinkedIn4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends your own request to the Browserflow API with the connection you already set up. It is the escape hatch for anything the seven ready-made modules do not cover.

When to use it
when Browserflow offers a feature in its API that has no dedicated module in Make yet.
Watch out
you need to know the endpoint and its format yourself, Make will not suggest them.
Browserflow for LinkedIn5

Scrape Profiles From a LinkedIn Post

Action

In Make“Retrieves LinkedIn profiles from people that have commented under a LinkedIn post.”

Collects the profiles of people who commented under a LinkedIn post. You get the audience that reacted, not just a count of comments.

When to use it
after a competitor or an industry voice publishes a post your buyers commented on.
Watch out
each commenter comes out as a separate bundle, so every module placed after it runs once per person.
Browserflow for LinkedIn6

Scrape Profiles From a LinkedIn Search

Action

In Make“Scrapes profiles from a LinkedIn search for a specific search term and a given location.”

Runs a LinkedIn search on a term and a location, then returns the matching profiles as a list your scenario can process.

When to use it
building a prospect or candidate list for a job title in one city, without copying names by hand.
Watch out
a broad term brings back a crowd, and each result then costs operations downstream. Narrow the term first.
Browserflow for LinkedIn7

Send a Linkedin Connection Invite

Action

In Make“Sends a connection invite to a person on Linkedin.”

Sends a connection request to a person on LinkedIn from the account behind your connection.

When to use it
once a profile has passed your filters, such as the right role and not already connected.
Watch out
each invite really goes out from your account. Test with Run once on a single profile before letting a full list through.
Browserflow for LinkedIn8

Send a Linkedin Message

Action

In Make“Sends a message to a LinkedIn connection without the need for SalesNavigator.”

Writes a direct message to one of your LinkedIn connections, and you do not need a Sales Navigator subscription for it.

When to use it
to thank someone who just accepted your invite, or to follow up after an event with a message mapped from a spreadsheet.
Watch out
it targets connections only. Check the relationship first, or the message has nowhere to go.
Need help

Need help automating Browserflow for LinkedIn with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the Browserflow for LinkedIn Make integration free?
Yes, on the Make side. Browserflow for LinkedIn is a standard app, so it is available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and count usage in credits, which are operations, per month. Whatever Browserflow itself charges is a separate matter, check it on their side.
02What do you need to connect Browserflow for LinkedIn to Make?
A Browserflow account and a Make account. Make lists no other prerequisite. In the editor, add any Browserflow module, click Create a connection, name it if you want, then either authorize Make on the Browserflow page or paste the key Browserflow provides, and click Save. The connection is then reused by all eight modules, so you only do this once per LinkedIn account you want to drive. If a teammate uses a different account, they create their own connection.
03Can Browserflow for LinkedIn start a Make scenario in real time?
No. The app has no trigger module, so nothing on LinkedIn starts the scenario by itself. You have two ways around it. Put a Browserflow action first and let the Make schedule run it, every 15 minutes by default. Or start with a trigger from another app, for example a new row in a spreadsheet of profiles to contact, and place the Browserflow modules after it. The second option fits lists you feed by hand.
04What if the Browserflow module you need is missing in Make?
It depends on what Browserflow exposes. The app includes Make an API Call, which calls any endpoint of the Browserflow API with the connection you already created, so a feature without its own module is still reachable. You will need the endpoint and its format from the Browserflow side. Make publishes no numbered limits for this app, so if something blocks at volume, split the list and test again with Run once.
05Make or n8n for Browserflow for LinkedIn?
It depends on how you like to work. Make suits people who want to assemble a scenario visually, see each bundle after Run once and get going without code. n8n suits teams that want finer control over each step and are comfortable with a more technical tool. The same app exists on both, so the choice comes down to your team, not to Browserflow. The comparison page on the site walks through the criteria in detail.
Same platform

Other docs you might need on this stack.

Browse all integrations