Find Company Url

What Find Company Url does

Find Company Url resolves a company name or partial identifier into a canonical LinkedIn company URL you can hand to any downstream action. You give it "Stripe" or "stripe-inc" or a messy CRM string, and it returns the stable /company/{vanity}/ URL with basic disambiguation metadata.

It runs on the LinkedIn level and uses your connected LinkedIn session to match against LinkedIn's own company index.

How it works

You send a name, domain fragment, or partial vanity. Edges authenticates the request with your LinkedIn session, runs a lookup against LinkedIn's company search, and returns the best-ranked match plus a short list of candidates. The action runs on Edges infrastructure with safe pacing, so you do not manage cookies or retries yourself.

Resolution is deterministic enough to drop into an ETL job — when the top match scores above a confidence threshold, Edges returns a single canonical URL; otherwise it returns the candidate list so your workflow can branch on it.

When to use Find Company Url

Use Find Company Url any time the input side of your workflow has company names or fragments but not canonical URLs — which is every time you pull from a CRM, an event registration list, or a CSV someone emailed you. It plugs into the LinkedIn profile & company data API use case as the resolution primitive that makes the rest of the pipeline possible.

Running this action first removes the single biggest cause of downstream extraction failures: bad or ambiguous company URLs.

Use cases

• CRM cleanup. Resolve every account name in your CRM to a canonical LinkedIn URL and store it for future enrichment runs.
• CSV onboarding. New customer import has company names only — Find Company Url gets you to a stable identifier per row.
• Enrichment pipelines. First step before Extract LinkedIn Company Profile or Extract LinkedIn Similar Companies.
• Deduplication. Collapse "Acme Inc", "Acme Incorporated", and "acme-co" into a single canonical URL as your account key.
• Signal ingestion. When a webhook fires with only a company name, resolve it to a URL before running downstream workflows.

Best practices

• Pass region or industry hints when you have them. Same-named companies are the most common source of wrong matches — a hint disambiguates cleanly.
• Gate on `confidenceScore`. Automatically accept high-confidence matches and queue low-confidence ones for a human review step.
• Cache results. The canonical URL rarely changes, so cache by normalized input string to cut redundant calls.
• Stay within LinkedIn guardrails. Edges handles pacing; avoid blasting Find Company Url thousands of times per minute from adjacent automations on the same account.

Common questions

How many companies can I resolve per run?

One per run. The action is a single-record primitive designed to sit inside per-row loops or CRM-triggered flows.

Does this use my LinkedIn account or a shared pool?

Your LinkedIn account. You connect LinkedIn to Edges once, and every resolution runs through that authenticated session.

Can I chain Find Company Url with other Edges actions?

Yes. The canonical companyUrl feeds directly into Extract LinkedIn Company Profile, Search LinkedIn Company Employees, and Extract LinkedIn Company Affiliates.

Get started

Add Find Company Url to any workflow that starts with raw company strings, or call it from the Edges API as a preprocessing step in your enrichment pipeline. Browse the full Actions library to see what to chain after resolution.