LinkedIn profiles in Zapier: enrich LinkedIn URLs with one Code step

• A Zapier plan with multi-step Zaps: Professional or above. This Zap has three steps: your trigger, the Code step and the step that writes the fields back. Zapier's Free plan allows two-step Zaps only.
• A Datacircle API key: sign up with your work email and your key is on your dashboard. You get a $5 credit, enough for 2,105 profiles through Up2Data.
• A trigger that passes the profile's URL, like https://www.linkedin.com/in/williamhgates.

After your trigger, add a step with these settings:

// LinkedIn profiles in Zapier, through Datacircle: Up2Data, then Fetchin past Up2Data's daily limit.
// Input Data: linkedin_url, the profile's LinkedIn URL from your trigger. Your key goes in KEY.
const KEY = "your Datacircle API key"

async function call(method, path, provider, body) {
  const headers = { Authorization: "Token " + KEY, "X-Data-Provider": provider }
  if (body) headers["Content-Type"] = "application/json"
  const response = await fetch("https://api.datacircle.dev" + path, { method, headers, body: body && JSON.stringify(body) })
  const answer = await response.json().catch(() => ({})) // a gateway's error page isn't JSON: its status says enough
  return { status: response.status, body: answer }
}

// The same fields on every answer, so the next step can map each one
function row(status, fields = {}) {
  const all = { status, title: "", company: "", location: "", headline: "", industry: "", headcount: "", cost_usd: 0, ...fields }
  for (const key in all) if (all[key] === undefined || all[key] === null) all[key] = ""
  return all
}

function failed(answer) {
  const reason = (answer.body.error && answer.body.error.message) || answer.body.error
  return row(reason ? "error " + answer.status + ": " + reason : "error " + answer.status)
}

const url = inputData.linkedin_url
const up2data = await call("POST", "/v1/profiles/enrich", "up2data", { url })
if (up2data.status === 200) {
  const profile = up2data.body.data
  const company = profile.current_company || {}
  return row("found", {
    title: company.title, company: company.name, location: (profile.location || {}).raw, headline: profile.headline,
    industry: company.industry, headcount: company.headcount, cost_usd: up2data.body.datacircle_meta.cost_usd,
  })
}
if (up2data.status === 422) return row("not found: private or deleted, free")
if (up2data.status === 400) return row("not a profile URL, free")
if (up2data.status !== 429) return failed(up2data)

// Up2Data's daily limit: the same URL through Fetchin, with the same key
const fetchin = await call("GET", "/api/v1/profile?profileUrlOrUrn=" + encodeURIComponent(url), "fetchin")
const body = fetchin.body
if (fetchin.status === 200) {
  return row("found (Fetchin)", {
    title: body.jobTitle, company: body.companyName, location: body.location, headline: body.title,
    cost_usd: body.datacircle_meta.cost_usd,
  })
}
if (fetchin.status === 404 && body.code === "PROFILE_NOT_FOUND") {
  return row("not found (Fetchin): private or deleted, billed", { cost_usd: body.datacircle_meta.cost_usd })
}
if (fetchin.status === 400) return row("not a profile URL, free")
return failed(fetchin)

A Code step reads your trigger's fields only through Input Data, as Zapier's guide says. Run Code tests the step with a real call, and we bill it like any other call.

Anyone who can edit the Zap sees your key in the code, since a Code step has no place to keep it. It stays out of your Zap history, which shows Input Data for every run. If it leaks, reset it: the old one stops working.

The Code step returns the same fields for every answer, so the step that writes the row, such as Google Sheets' Update Spreadsheet Row, can map each one:

Fetchin returns the profile's industry, not the company's, and no headcount, so a row through Fetchin leaves industry and headcount empty. Our LinkedIn Profile API page shows the profile's other fields, such as jobs, schools and skills.

The step returns a status for every answer and never fails on one, so one private profile doesn't stop your Zap. Zapier turns a Zap off when 95% of its runs in the last 7 days end in an error.

Up2Data takes $1 a day per account (421 profiles), with a shared daily limit for all customers, then answers 429 until 00:00 UTC. HarvestAPI has no daily limit. Fetchin has no daily limit either. A call your balance can't cover answers 402. Add funds, from $5, on your dashboard.

For an error row, fix what its reason says, then replay its Zap run: in the Zap editor, open Zap runs, select the runs, then Replay, Entire Zap. Zapier offers Replay on paid plans and counts the replayed steps as new tasks.

We charge your balance these prices, with no markup, as our pricing page shows:

Zapier counts each step against your plan's tasks. If 1,000 new rows come in one day and the providers find every profile, you pay us $1.86 at most: $1.00 for 421 through Up2Data and $0.86 for the other 579 through Fetchin, less if the daily limit all customers share stops Up2Data sooner. Fetchin costs less per profile found. But it bills a profile it can't find, which Up2Data doesn't. It also gives no company industry or headcount, so the code calls Up2Data first.

The same call in n8n: LinkedIn profiles in n8n. In a Make scenario instead: LinkedIn profiles in Make. In a Google Sheet, without Zapier: LinkedIn profiles in Google Sheets. From Python: get LinkedIn profile data with Python. Other vendors' prices per 1,000: LinkedIn profile API pricing compared.