LinkedIn Employees from Company Domain (HarvestAPI)
Resolve a domain and return an exact-company, multi-page LinkedIn employee dataset through native HarvestAPI.
Shared June 2026
- 1
Install & authenticate
$ npm install -g deepline@latest && npm exec --yes --package=deepline@latest -- deepline setup --json
- 2
Test out this play on my data
What this workflow does
Resolve a domain and return an exact-company, multi-page LinkedIn employee dataset through native HarvestAPI.
LinkedIn Employees from Company Domain (HarvestAPI) (Deepline play "company-domain-to-linkedin-employees-harvestapi", version 1). Resolve a domain and return an exact-company, multi-page LinkedIn employee dataset through native HarvestAPI. Pipeline: 5 steps, 2 providers, processes input rows as a dataset. Inputs: domain, max_items, profile_depth. Outputs: domain, linkedin_company_url, rows.
Inputs you need
Bring these fields
- domain
- max_items
- profile_depth
Outputs you get
Produced by the run
- serper_linkedin_company_from_domain
How it works
Step 1
Looped code
1 nested step
Step 2
Looped code
1 nested step
Step 3
Serper
Serper · google search
Step 4
Conditional code
1 nested step
Step 5
Dataset rows
over linkedin_url, full_name
Cost/latency when available
This public page does not show cost or latency yet. Deepline only displays those metrics when the published package has safe, comparable run samples, and cost is always shown in Deepline credits.
Common edits
- Rename the copied play before the first run so it is owned by your workspace.
- Map your CSV headers into the expected input fields and add status or miss_reason columns.
- Keep stable step, fetch, dataset, and play-call ids so retries and durable receipts stay useful.
- Edit the final projection before scale so the output table matches your CRM or campaign import.
Use it when
- You need data from HarvestAPI and Serper in one pass.
- You want a repeatable pipeline instead of one-off lookups.
- You want an agent or teammate to run the same workflow on demand.
Related workflows
LinkedIn Employees from Company Domain
domain, max_items, profile_depth → domain, linkedin_company_url, rows
LinkedIn Profile from Name and Company
first_name, last_name, domain → linkedin_url, linkedin_source, serper_name_validate
LinkedIn Profile from Name and Company (HarvestAPI)
first_name, last_name, domain → linkedin_url, linkedin_source, serper_name_validate
Run or fork with Deepline CLI
LinkedIn Employees from Company Domain (HarvestAPI) is a Deepline play. Inputs: domain, max_items, profile_depth. Outputs: serper_linkedin_company_from_domain.
# Inspect the contract
$ deepline plays describe prebuilt/company-domain-to-linkedin-employees-harvestapi --json
# Copy to an owned scratchpad
$ deepline plays get prebuilt/company-domain-to-linkedin-employees-harvestapi --source --out company-domain-to-linkedin-employees-harvestapi-scratchpad.play.ts
# Check before running
$ deepline plays check company-domain-to-linkedin-employees-harvestapi-scratchpad.play.ts
# Paste into Claude Code, Cursor, or Codex.
$ Use the deepline-gtm skill's plays recipe to turn the Deepline play "LinkedIn Employees from Company Domain (HarvestAPI)" (https://deepline.com/p/deepline/company-domain-to-linkedin-employees-harvestapi) into an editable scratchpad play. Inputs: domain, max_items, profile_depth. Outputs: serper_linkedin_company_from_domain. The .play.ts file is the source of truth: copy the play, rename it for this user's workflow, encode input mapping/validation/status/output projection in the play, and iterate there instead of doing one-off CSV post-processing. Keep stable dataset names, dataset row keys, and step/fetch/play-call ids across edits. Provider tool calls reuse paid work by play, tool, semantic input, auth scope, provider action version, and cache policy unless you intentionally change those inputs or refresh stale data. # install Deepline if the CLI is missing npm install -g deepline@latest && npm exec --yes --package=deepline@latest -- deepline setup --json # inspect the live contract deepline plays describe prebuilt/company-domain-to-linkedin-employees-harvestapi --json # copy to an owned scratchpad, then rename the play inside the file before first run deepline plays get prebuilt/company-domain-to-linkedin-employees-harvestapi --source --out company-domain-to-linkedin-employees-harvestapi-scratchpad.play.ts # edit company-domain-to-linkedin-employees-harvestapi-scratchpad.play.ts: set an owned play name, add mappings/validation/status/miss_reason/final columns deepline plays check company-domain-to-linkedin-employees-harvestapi-scratchpad.play.ts # run the scratchpad on your data deepline plays run --file company-domain-to-linkedin-employees-harvestapi-scratchpad.play.ts --input '{"domain":"<value>","max_items":"<value>","profile_depth":"<value>"}' --watch # only for an exact one-off with no edits or custom output deepline plays run prebuilt/company-domain-to-linkedin-employees-harvestapi --input '{"domain":"<value>","max_items":"<value>","profile_depth":"<value>"}' --watch Play spec (JSON): https://deepline.com/api/v2/shared-plays/prebuilt-company-domain-to-linkedin-employees-harvestapi
Version
v1 · Shared June 2026 · Unlisted page