LinkedIn Companies scraper

What it collects

socialEnriches from the site

The organisation behind any public LinkedIn company page — name, description, tagline, live employee count, website and registered city, one row per company, read from the page LinkedIn serves without an account. It is a scraper, which means the whole contract is: fill in the form, and one table comes back. No browser window opens, it costs none of your plan's automation slots, and the requests go out over plain HTTP carrying a real browser's TLS fingerprint.

It runs fine from your own address; a proxy is available on the run and this target does not need one. Whichever way it went, every row records it — see the provenance columns below.

What you give it — 6

The form the app draws, read out of the card itself. Each hint below is the one shown beside that field in the run dialog, so nothing here is a description of the product written separately from it.

The one answer it needs

companies

Companies · list · required

One company per line, in whatever form you have it — the company page URL, a country subdomain like de.linkedin.com/company/…, or the bare slug. Member, school and showcase pages are not companies and are skipped. If every one of them fails with a 999 it is the address and not the slugs: this card usually does better with no proxy than with a shared one.

Everything else is optional

minEmployees

Minimum employees · number

LinkedIn’s live headcount. A company whose page publishes no count at all fails this rather than counting as zero.

website

Website · select

Most company pages link one; the ones that do not are usually the smaller listings.

keywords

Description contains · list

Keeps a company only when its About text contains one of these. Costs no extra requests — the reply already carried the text.

countries

Country · list

Two-letter codes, as LinkedIn writes them. Most companies publish no address at all and fail this, so reach for it only when you know your targets have one.

scrapeContacts

Find email addresses · boolean

Opens each company’s own website — the one in the Website column, not the LinkedIn page — looking for an address, a named contact and social links. A company with no linked site is skipped. This is the slow half: a company page is one request, and this adds up to fifteen more per company.

What comes back — 29 columns

One dataset per run — a typed table your workspace owns, which you can then sort, filter, edit in the grid, export whole, or read back over the local API. These are the columns it is created with.

13 from LinkedIn Companies

12 from the enrichment pass

Opt in and the run makes one extra request per row: it visits the site in the website column looking for an address, a named contact and social links. That is the step that turns a listing into a lead, and it is what the run is mostly spending its time on when you ask for it.

4 that every scraper writes

The same four on every card, so a table can still answer months later how its rows got there: which service they came from, when, which profile's identity the requests carried, and whether that identity was signed in.

Four ways to run it

The Scrapers tab. Pick the card, fill in the form, press Start. Every run started here makes a new table, named after what you searched for and when. Check first if you like — it collects one page, writes nothing, and reports which columns came back filled.

Ask the assistant. It has the whole catalogue, so this card is a sentence rather than a form. It fills in the parameters above from what you said and shows you them before it starts.

Over MCP or the local API. The same card, from a coding agent — argus_run_scraper over the MCP server, or POST http://127.0.0.1:39219/v1/scrapers/run on the local API. There is a sample call beside it that writes nothing.

{
  "kind": "linkedin_companies",
  "inputs": {
    "companies": [
      "…"
    ]
  }
}

As a step inside a workflow. The Run scraper step puts this collector in the middle of an automation — collect, then filter, then mail — and the tree still opens no window doing it. It is also the one caller that can overrule the table-per-run rule: pointed at a table you name, it creates that table with the columns above if it is missing and files every run into it after, appending or updating the row in place on a column you match on. The step hands the next one the table's name, its id and the row count.

Where it stops

It will not drive a page. Anything that needs a real browser — a site with no list endpoint behind it, or anything operating an account of your own — is an automation instead, and that is a different tool rather than a worse version of this one.

It signs in to nothing. Reading a public page signed out is the settled position — Bright Data scraped Meta signed out and won; hiQ scraped LinkedIn signed in and lost — so this card asks for no account and holds none.