ACTION_ID: enrich_company_linkedin_profile NAME: Scrape Company LinkedIn Profile CATEGORY: Company Enrichment CREDITS: 0.2-1 varies by provider Scrape a company's LinkedIn page for its public profile data. Returns the company's name, headline / tagline, description, website, employee headcount, follower count, specialties, headquarters address (line1 / line2 / city / region / country / postal code), other locations, company type, founded year, industries, and image URL. Useful as a lightweight company-firmographics source when you have (or can resolve) a company LinkedIn URL — cheaper than the broader firmographic enrichment actions and good enough when you only need LinkedIn-page-level fields. 1. INPUTS company_linkedin_url (type: url, required) — Company LinkedIn URL LinkedIn URL of the company. Must be a company page URL — see KEY NOTES. 2. OUTPUTS company_name (type: string) — Company Name Name of the company. company_headline (type: string) — Company Headline Tagline / short headline displayed at the top of the LinkedIn page. company_description (type: string) — Company Description Long-form company description from the LinkedIn page. company_website (type: url) — Company Website Company website URL listed on LinkedIn. employee_headcount (type: number) — Employee Headcount Approximate employee headcount as reported on LinkedIn. no_of_followers (type: number) — No. of Followers Number of LinkedIn page followers. specialities (type: raw_array) — Specialities Specialty tags listed on the company page. other_locations (type: raw_array) — Other Locations Other office locations beyond the HQ address. similar_companies (type: raw_array) — Similar Companies Similar / related companies LinkedIn surfaces on the profile. company_linkedin_url (type: url) — Company LinkedIn URL Canonical company LinkedIn URL. company_industries (type: string) — Company Industries Comma-separated industry labels (e.g. "Technology, Internet, Software"). hq_country (type: string) — HQ Country Country of the company HQ. hq_region (type: string) — HQ Region State / region of the company HQ. hq_city (type: string) — HQ City City of the company HQ. postal_code (type: string) — Postal code Postal / ZIP code of the HQ. hq_address_line1 (type: string) — HQ Address line1 First line of the HQ address. hq_address_line_2 (type: string) — HQ Address line 2 Second line of the HQ address. is_primary (type: string) — Is Primary Whether the returned address is the primary HQ. "true" / "false". company_type (type: string) — Company Type Company type label (e.g. "Privately Held", "Public Company", "Non Profit"). company_image_url (type: url) — Company Image URL Company logo / image URL. founded_year (type: string) — Founded Year Year the company was founded. 3. HOW TO CONFIGURE Configure Action body: { "inputs": { "company_linkedin_url": "{{input.company_linkedin_url}}" } } Pass the company's LinkedIn URL as `company_linkedin_url`. See KEY NOTES for the URL-shape requirement. 4. KEY NOTES - The linkedin_url input MUST be a company-page URL — i.e. the path starts with "/company/" (e.g. https://www.linkedin.com/company/google). It will NOT work with: - Person profile URLs ("/in/" — those are for enrich_person_linkedin_profile). - School / education URLs ("/school/"). - Showcase, group, or other LinkedIn surface types. If you only have a company domain or name, use llm_web_agents first with a prompt like "find the company LinkedIn URL for " to resolve the correct /company/ URL, then feed that output into this action. - Lightweight firmographic source: returns LinkedIn-page-level fields only. For workforce trends (growth / churn / tenure / per-month headcount), funding history, or corporate-structure signals, use company_enrich_using_people_data_labs instead. 5. WHERE IT FITS IN A WORKFLOW Pattern (LinkedIn-page firmographic enrichment): pull the LinkedIn-page-level company profile as a quick / cheap firmographic source, then continue to contact discovery or richer enrichment as needed. input (company LinkedIn URL — /company/) -> enrich_company_linkedin_profile (returns name, headcount, industry, HQ address, description, etc.) -> downstream filtering / enrichment / contact discovery. Pattern (resolve LinkedIn URL from a domain first): if you only have the company domain or name, resolve the /company/ LinkedIn URL with a web agent before scraping the page. input (company domain or name) -> llm_web_agents (prompt: "find the company LinkedIn URL for " — returns the /company/ URL) -> enrich_company_linkedin_profile (scrapes the page) -> downstream steps. Pattern (lightweight first, deeper later): use this action as a cheap first-pass firmographic enrichment; if specific signals are missing (workforce trends, funding history, corporate structure), follow up with the deeper PDL enrichment only on the rows that need it. input (company LinkedIn URL) -> enrich_company_linkedin_profile -> filter rows that need deeper data -> company_enrich_using_people_data_labs (only on the filtered subset — saves credits) -> outreach / scoring. 6. WHEN TO USE Use enrich_company_linkedin_profile when: - You have a company LinkedIn URL (or can resolve one from a domain) and want a quick, cheap firmographic enrichment — name, industry, headcount, HQ, description, etc. - You only need LinkedIn-page-level fields and don't need workforce trends, funding history, or corporate-structure signals. - You want a first-pass enrichment to filter rows before spending credits on a deeper provider like company_enrich_using_people_data_labs. 7. WHEN NOT TO USE You're scraping a person profile, not a company page -> action-detail/enrich_person_linkedin_profile.txt You only have a company domain or name (no LinkedIn URL) -> action-detail/llm_web_agents.txt Use a web agent prompted to "find the company LinkedIn URL for " to resolve the /company/ URL, then feed that output into this action. You need workforce trends (growth / churn / tenure), funding history, or corporate-structure signals -> action-detail/company_enrich_using_people_data_labs.txt This action returns only LinkedIn-page-level fields. PDL is the broader enrichment provider for workforce / funding / corporate-structure depth. You need a department-level tech-stack breakdown -> action-detail/company_tech_stack_floqer.txt You only need the country headcount distribution -> action-detail/company_headcount_distribution_by_country.txt Last updated: 2026-04-30.