ACTION_ID: company_enrich_using_lightning
NAME: Lightning: Company Enrich
CATEGORY: Company Enrichment
CREDITS: 0.1

Enrich a company from its domain or LinkedIn URL — name, about text,
industry, size, follower count, founded year and a full HQ address
breakdown. The cheapest company enrichment in the catalog.

1. INPUTS

company_identifier (type: url, required)
  Company Identifier. Company LinkedIn URL or Domain. Use LinkedIn URL
  for better coverage.

2. OUTPUTS

name (string) — Company name

linkedin_url (string) — LinkedIn URL of the company

about (string) — Company description / about section

industry (string) — Industry the company operates in

type (string) — Company type (e.g. Privately Held)

size (string) — Company size range (e.g. 1-10)

employees_on_linkedin (number) — Number of employees listed on LinkedIn

followers (number) — Number of LinkedIn followers

founded_year (string) — Year the company was founded

domain (string) — Primary domain of the company

website (string) — Company website URL

specialties (string) — Company specialties

city (string) — HQ city

state (string) — HQ state or province

postcode (string) — HQ postcode / zip code

country (string) — HQ country name

country_code (string) — HQ country code (e.g. FR, US)

region (string) — HQ region

continent (string) — HQ continent

street (string) — HQ street address

3. HOW TO CONFIGURE

Single input, no dropdowns. Configure Action body:

{
  "inputs": {
    "company_identifier": "{{input.company_linkedin_url}}"
  }
}

Field-by-field:
  - company_identifier  Required. A company LinkedIn URL or a domain.
                        The LinkedIn URL gives materially better
                        coverage — prefer it when the row has one.

4. KEY NOTES

- At 0.1 credits this is roughly a tenth the cost of
  `floqer_company_firmographics` and a fiftieth of
  `company_enrich_using_people_data_labs`, but it returns no revenue
  band, no NAICS/SIC codes and no per-country locations.
- Coverage is LinkedIn-derived. A company with no LinkedIn presence
  returns mostly empty fields even when the domain resolves.
- `size` is a range string (`1-10`, `51-200`); `employees_on_linkedin`
  is the numeric count. Filter on the numeric field.
- The action takes one identifier, not both — passing a domain when a
  LinkedIn URL is available measurably lowers the hit rate.

5. WHERE IT FITS IN A WORKFLOW

Pattern: use it as the cheap first pass — company_enrich_using_lightning
-> filter (employees_on_linkedin greater than 50) ->
floqer_company_firmographics for the survivors, so the expensive
provider only sees qualified rows.

6. WHEN TO USE

Use company_enrich_using_lightning as a high-volume triage pass where
cost per row matters more than field depth.

7. WHEN NOT TO USE

Need a revenue range or industry codes
  -> action-detail/floqer_company_firmographics.txt

Need workforce trends and funding history
  -> action-detail/company_enrich_using_people_data_labs.txt

Last updated: 2026-08-03.