6steps·3providers·SQLyou own

LinkedIn Profile from Name and Company

Find a LinkedIn profile from a person name and company context.

Shared June 2026

  1. 1

    Install & authenticate

    $ npm install -g deepline@latest && npm exec --yes --package=deepline@latest -- deepline setup --json

  2. 2

    Test out this play on my data

What this workflow does

Find a LinkedIn profile from a person name and company context.

LinkedIn Profile from Name and Company (Deepline play "person-to-linkedin", version 1). Find a LinkedIn profile from a person name and company context. Pipeline: 6 steps, 3 providers. Inputs: first_name, last_name, domain, company_name, email. Outputs: linkedin_url, linkedin_source, serper_name_validate.

Inputs you need

Bring these fields

  • first_name
  • last_name
  • domain
  • company_name
  • email

Outputs you get

Produced by the run

  • linkedin_url
  • linkedin_source
  • serper_name_validate

How it works

  1. Step 1

    Enrichment waterfall

    6 providers, first match wins

    • google search · Serper
    • search people · Dropleads
    • google search · Serper
    • v2 enrich person · Crustdata
    • google search · Serper

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 Serper, Dropleads and Crustdata 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

Mobile Phone from Person

first_name, last_name, domain → phone, phone_source, phone_validated

LinkedIn Profile from Personal Email

personal_email → personal_email, normalized_email, linkedin_url

Personal Email Finder

first_name, last_name, linkedin_url → personal_email, email_source, email_validated

Run or fork with Deepline CLI

LinkedIn Profile from Name and Company is a Deepline play. Inputs: first_name, last_name, domain, company_name, email. Outputs: linkedin_url, linkedin_source, serper_name_validate.

# Inspect the contract

$ deepline plays describe prebuilt/person-to-linkedin --json

# Copy to an owned scratchpad

$ deepline plays get prebuilt/person-to-linkedin --source --out person-to-linkedin-scratchpad.play.ts

# Check before running

$ deepline plays check person-to-linkedin-scratchpad.play.ts

# Paste into Claude Code, Cursor, or Codex.

$ Use the deepline-gtm skill's plays recipe to turn the Deepline play "LinkedIn Profile from Name and Company" (https://deepline.com/p/deepline/person-to-linkedin) into an editable scratchpad play. Inputs: first_name, last_name, domain, company_name, email. Outputs: linkedin_url, linkedin_source, serper_name_validate. 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/person-to-linkedin --json # copy to an owned scratchpad, then rename the play inside the file before first run deepline plays get prebuilt/person-to-linkedin --source --out person-to-linkedin-scratchpad.play.ts # edit person-to-linkedin-scratchpad.play.ts: set an owned play name, add mappings/validation/status/miss_reason/final columns deepline plays check person-to-linkedin-scratchpad.play.ts # run the scratchpad on your data deepline plays run --file person-to-linkedin-scratchpad.play.ts --input '{"first_name":"<value>","last_name":"<value>","domain":"<value>","company_name":"<value>","email":"<value>"}' --watch # only for an exact one-off with no edits or custom output deepline plays run prebuilt/person-to-linkedin --input '{"first_name":"<value>","last_name":"<value>","domain":"<value>","company_name":"<value>","email":"<value>"}' --watch Play spec (JSON): https://deepline.com/api/v2/shared-plays/prebuilt-person-to-linkedin

Version

v1 · Shared June 2026 · Unlisted page