Resources · n8n integration

Browserflow for LinkedIn n8n integrationAutomate Browserflow for LinkedIn with n8n.

Browserflow for LinkedIn n8n integration turns a browser session into a workflow step. The node exposes 11 operations on a single LinkedIn resource, from pulling profiles out of a search to sending a message. It has no trigger of its own, and every operation can run as a background job.

Community node This node is not shipped with n8n: it is a community package (n8n-nodes-browserflow) you install from Settings › Community nodes on a self-hosted instance. npm

Try the Browserflow for LinkedIn integration on n8nSee the 11 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Browserflow for LinkedIn n8n integration actually do?

Browserflow for LinkedIn is a node you add to n8n to automate LinkedIn actions. It groups 11 operations on one resource, called linkedin, covering three jobs: reading public pages (profiles, posts, search results), reading your own network (connections, chat history) and acting in your name (invites, messages, page invitations). Every operation can run in the background and hand back a job ID instead of a result, which is how the long ones stay out of the way.

Start with the one most people come for: prospect lists. linkedin.scrapeProfilesFromSearch takes a search term, or a search URL copied from the LinkedIn address bar, and walks through the result pages. Wire the output into Google Sheets and the list is in a tab, deduplicated by whatever column you pick, ready for a human to read before anything gets sent.

Second scenario, post engagement. A post that worked deserves a follow up, and linkedin.scrapeProfilesFromPostComments returns the people behind the comments and the reactions on it. Feed that into linkedin.checkConnection, and the workflow splits in two: the people already in the network get a message, the rest get an invite. A short summary of the run posted to Slack keeps the team aware without opening n8n.

Third, account monitoring. linkedin.scrapePosts works on a person profile and on a company profile, so a Schedule Trigger every morning can watch a handful of competitors and mail the new posts through Gmail. Nothing here is real time: the node has no trigger, so the rhythm is the one you set on the trigger that starts the workflow.

Where this node stops, the HTTP Request node takes over. It calls any endpoint of the tool's API and reuses the same credential through predefined authentication, which is the answer whenever an operation is missing from the list of 11. Two more limits worth knowing before you build: there is no trigger node, and pagination is manual, handled by Limit, Offset, Start Page and Number of Pages depending on the operation.

If you are still weighing platforms, the n8n review goes through self hosting and the cost model in detail. This node makes the argument on its own, though: a community node only installs on an instance you host yourself, and that instance is where the scraped data stays.

Connect

How do you connect Browserflow for LinkedIn to n8n?

  1. 01

    Install the community node

    Browserflow for LinkedIn does not ship with n8n. On a self hosted instance, open Settings, then Community nodes, and install the npm package n8n-nodes-browserflow in version 2.0.1. n8n Cloud only accepts verified community nodes, so check that point before planning the workflow there. Once the install finishes, the node shows up in the node panel under its display name.

  2. 02

    Create the credential once

    Open the Credentials menu and create the credential for the node. A credential is created once in n8n and reused across every workflow, and the node offers it in its own dropdown, so nothing gets pasted twice. The node has no authentication selector of its own: pick the credential, and all 11 operations on the LinkedIn resource run through it.

  3. 03

    Add a trigger, then a first operation

    The node cannot start a workflow. Put a Schedule Trigger in front of it to run at a fixed interval, or an n8n Webhook, meaning a URL another service calls to fire the workflow. Wire the Browserflow node behind it, pick an operation, and fill its fields with expressions such as {{ $json.linkedinUrl }}, which reads a field from the incoming item.

Actions

The 11 operations of the Browserflow node

The Browserflow for LinkedIn node exposes 11 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCheck if a Person Is a ConnectionExport LinkedIn Chat HistoryGet Job ResultGet Data From A Linkedin ProfileInvite Connections to Follow a LinkedIn PageList LinkedIn ConnectionsScrape LinkedIn PostsScrape Profiles From A LinkedIn PostScrape Profiles From A LinkedIn SearchSend A LinkedIn Connection InviteSend A LinkedIn Message
✓✓✓✓✓✓✓✓✓✓✓

11 operations
01

Check if a person is a connection

linkedin.checkConnection

What you see in n8n

Notes & use cases

This one asks a yes or no question about a single profile: is that person already in your network? The answer comes back as an item you can branch on, before anything is sent.

Key parameters

  • LinkedIn URL: the LinkedIn profile URL to check connection status. Required, so an empty value stops the node. It often comes from an earlier step as {{ $json.linkedinUrl }}.
  • Schedule as a Job (Polling): runs the action in the background and returns a job ID you can poll.
Use cases
split an outreach list in two, so existing connections receive a message and everyone else receives an invite.
02

Export linked in chat history

linkedin.getChatHistory

What you see in n8n

Notes & use cases

Copying a conversation out of LinkedIn by hand is slow and lossy. This operation exports the message thread you have with one profile and drops it into the workflow as data.

Key parameters

  • LinkedIn URL: the LinkedIn profile URL to get chat history. Required.
  • Number of Messages: how many messages to retrieve from the chat history. Left blank, all messages are retrieved.
  • Callback URL: the server posts the result there when the job is done.
Use cases
archive the last exchanges with a lead into a document before a sales call, so the context is read rather than remembered.
03

Get data from a linkedin profile

linkedin.getProfileData

What you see in n8n

Notes & use cases

One profile in, its data out. Point the operation at a person and the workflow receives what the profile page holds, ready to be written somewhere useful.

Key parameters

  • LinkedIn URL: the LinkedIn profile URL to get profile data. Required, and the value is normally the one carried by the incoming item.
  • Schedule as a Job (Polling): sends the work to the background and returns a job ID you can poll.
Use cases
enrichment. A new row lands in a CRM with a LinkedIn URL and nothing else, and this operation fills the rest of the record in the same run.
04

Get the result of a job

linkedin.getJobResult

What you see in n8n

Notes & use cases

Background work needs a second visit. Any operation launched with polling returns a job ID instead of the data, and this operation is what turns that ID back into the result.

Key parameters

  • Job ID: the job ID returned when you invoked an action with polling enabled, for example 1201bfb7-1b5f-44fe-93c5-3e269316876851a. Required.
Use cases
pair it with a Schedule Trigger that runs a few minutes after a long scrape, or skip it entirely by setting a Callback URL on the original operation.
05

Invite connections to follow a linkedin page

linkedin.inviteToFollowPage

What you see in n8n

Notes & use cases

Growing the audience of a company page is repetitive clicking. Here it becomes one node that picks connections and sends them the page invitation.

Key parameters

  • LinkedIn URL: the URL of the company page you are admin to. People get invited to this page. Required.
  • Max Number of Connections to Invite: how many connections to invite, the default being 10. Required.
  • Search Method: term to use a search term, filters to invite the 1st degree connections matching your filters.
  • Current Company, Location, Industry, School: the filters themselves, such as a city or a university.
Use cases
after a product launch, invite the connections working in one industry, in batches, on a weekly schedule.
06

List your linkedin connections

linkedin.listConnections

What you see in n8n

Notes & use cases

No URL to provide on this one: it reads your own network and returns the connections as items. It is the usual starting point when the workflow needs a base to work from.

Key parameters

  • Limit: the maximum number of results to return.
  • Offset: how many connections to skip before starting to scrape, which is how you page through a long network.
  • Filter: the sort order, recently added, first name or last name.
Use cases
export the network to a spreadsheet once a month and diff it against the previous export to see who joined.
07

Scrape linkedin posts

linkedin.scrapePosts

What you see in n8n

Notes & use cases

Publication history, as data. Give the operation an account and it returns the posts it finds on that page, without anyone opening a browser tab.

Key parameters

  • LinkedIn URL: the profile URL to scrape posts from. It works for both person and company profiles. Required.
  • Limit: the maximum number of results to return.
  • Offset: how many entries to skip before starting to scrape.
Use cases
competitive watch. A daily run over five company pages, filtered on what is new since yesterday, then a digest sent to the marketing channel.
08

Scrape profiles from a linkedin post

linkedin.scrapeProfilesFromPostComments

What you see in n8n

Notes & use cases

Engagement on a post is a list of people, and this operation returns that list. It starts from the post itself, not from a profile, which is what makes it different from the other scrapers.

Key parameters

  • Post URL: the URL of the LinkedIn post to scrape profiles from. Required.
  • Add Comments and Comments Limit: include the comments in the results, and cap how many are scraped.
  • Add Reactions, Reactions Offset and Reactions Limit: the same controls for reactions.
Use cases
a hiring post collects a wave of reactions, and the workflow turns them into a shortlist the same evening.
09

Scrape profiles from a linkedin search

linkedin.scrapeProfilesFromSearch

What you see in n8n

Notes & use cases

Search results, paged and returned as items. This is the widest operation of the node, and the one that builds lists from scratch rather than from someone you already know.

Key parameters

  • Search Term: the term used for scraping profiles. Required.
  • Search Method: filters, or url to paste a Search URL copied from the LinkedIn address bar once the filters are set there.
  • Category: persons or companies.
  • City and Country: geographic filters on the results.
  • Start Page and Number of Pages: the manual pagination of the scrape.
Use cases
build a territory list of companies in one country, then enrich each of them in a second pass.
10

Send a linked in connection invite

linkedin.sendConnectionInvite

What you see in n8n

Notes & use cases

The invite itself, sent from the workflow. One profile per item, and a choice to make about whether a note travels with it.

Key parameters

  • LinkedIn URL: the LinkedIn profile URL to send a connection invite. Required.
  • Add Message: whether a custom message goes with the invite.
  • Message: left blank, the invite is sent without a message, which avoids LinkedIn limits. With a message, make sure it fits within LinkedIn's character and message limits.
Use cases
the second branch of an outreach workflow, the one that handles everyone the connection check found outside the network.
11

Send a linkedin message

linkedin.sendMessage

What you see in n8n

Notes & use cases

Here the workflow writes in the conversation. Two required fields, no options to weigh, which makes this the simplest operation of the 11 and the easiest to fire by accident.

Key parameters

  • LinkedIn URL: the LinkedIn profile URL to send a message. Required.
  • Message: the message to send. Required, and it has to fit within LinkedIn's character and message limits.
Use cases
a follow up sent a few days after an invite was accepted, with the text built from the profile data collected earlier in the run.
Need help

Need help automating Browserflow for LinkedIn with n8n?

A person reads every message.

FAQ

Browserflow for LinkedIn and n8n, the questions that come next

01Is the Browserflow for LinkedIn n8n integration free?
On the n8n side, yes, there is nothing to pay. The catch is a different one: this is a community node, so it does not ship with n8n. It is the npm package n8n-nodes-browserflow, in version 2.0.1, installed from Settings, then Community nodes, on a self hosted instance. n8n Cloud only accepts verified community nodes, which means a Cloud plan is not a safe assumption here. What the tool itself costs is a separate matter, and this page does not cover it. Budget the hosting of the n8n instance, and check the node installs on your version before you design anything around it.
02What credentials do you need to connect Browserflow to n8n?
One credential, created once and reused everywhere. In n8n, credentials live in their own menu, separate from workflows, and the node picks one up from a dropdown instead of holding the values itself. This node has no authentication selector, so there is no method to choose between: you select the credential and all 11 operations run through it. No credential documentation was published with the node, so the fields to fill are the ones the credential form shows in n8n, and nothing else should be guessed around them. Install the package first, since the credential type only appears once the node is installed.
03What are the limits of the Browserflow node in n8n?
Three worth planning for. First, there is no trigger node, so nothing here reacts on its own and every workflow starts from something else. Second, pagination is manual and named differently from one operation to the next: Limit and Offset on the connection and post scrapers, Start Page and Number of Pages on the search scraper. Third, the node covers 11 operations on one LinkedIn resource, and anything outside that list is not there. That last one has an answer: the HTTP Request node calls any endpoint of the tool's API and reuses the same credential through predefined authentication.
04Does Browserflow for LinkedIn react in real time in n8n?
No, and it cannot. This tool has no trigger node in n8n, so a workflow around it starts somewhere else: a Schedule Trigger at a fixed interval, an n8n Webhook called by a third party service, or the trigger of another tool already in your stack. Inside the node there is a second timing question. Operations can be scheduled as a job, returning a job ID rather than a result, and you get that result back either by calling Get Job Result later or by setting a Callback URL, which the server posts to once the work is done.
05n8n or Make for Browserflow for LinkedIn?
It depends, and here one criterion settles it faster than usual. Make is a hosted automation platform with no self hosting option, billed per operation. A community node installs on an instance you host yourself, so this particular node points toward n8n by construction. Beyond that, the comparison is the usual one: where the platform runs, who holds the data that comes out of a scrape, how the bill grows with volume, and how comfortable the visual logic feels to the person who will maintain the workflow. High volume scraping is exactly the pattern where a per operation bill and a per server bill diverge.
Same platform

Other docs you might need on this stack.

Browse all integrations