Domain to LinkedIn URL Resolver

Version: 0.2.0

Resolves a company domain or name to its LinkedIn company URL. Fixes the miss rate in Clay native enrichment.

---

Why not use a free tool?

Free tools return a URL or null. That's it.

You get no signal on how the URL was found, no confidence rating, and no way to gate your downstream enrichment on data quality. In a Clay workflow processing thousands of rows, a wrong LinkedIn URL propagates silently into your sequences.

This actor returns resolution_method (pattern_match / google_search / not_found) and confidence (high / medium / low) on every row. You can filter in Clay to pass only confidence = high rows forward, and review google_search results separately before they hit your sender.

The $0.03 price is for the metadata. The URL is the bonus.

---

How it works

Two-method cascade:

1. Pattern match. Derives a slug from the domain and validates it against LinkedIn directly via HTTP. No external API required. Fast and free of search rate limits.
2. Google search fallback. If pattern matching fails, runs a Google search for the company name plus LinkedIn and extracts the first matching company URL from results.

If you only have a company name and no domain, the actor skips pattern matching and goes straight to Google search. Both input paths return the same flat output row.

The resolution_method field tells you which path succeeded. The confidence field tells you how reliable the result is.

---

Input

At least one of company_domain or company_name must be provided.

Field	Type	Required	Notes
company_domain	String	No	Bare domain, e.g. stripe.com. Required if company_name is not provided. Enables pattern match resolution before Google search fallback.
company_name	String	No	Company name. Required if company_domain is not provided. When provided alongside a domain, improves Google search accuracy.

Example with domain:

{
  "company_domain": "stripe.com",
  "company_name": "Stripe"
}

Example with name only:

{
  "company_name": "Linear"
}

---

Output

One flat row per input. Every field is always present. Null over missing keys.

Field	Type	Description
company_domain	String	Echoed from input, or null if not provided
company_name	String	Echoed from input, or derived from domain
linkedin_company_url	String	Full LinkedIn company URL, e.g. https://www.linkedin.com/company/stripe
linkedin_slug	String	Slug only, e.g. stripe
resolution_method	String	pattern_match / google_search / not_found / error
confidence	String	high / medium / low
facebook_url	String	Facebook company page URL, or null if not found
instagram_url	String	Instagram profile URL, or null if not found
run_date	String	ISO timestamp of run

---

Confidence and resolution_method explained

resolution_method tells you how the URL was found:

• pattern_match: slug derived from domain, validated directly against LinkedIn. Fastest, most reliable.
• google_search: URL found via Google search results. Accurate but subject to Google result freshness.
• not_found: neither method returned a result.
• error: no valid input was provided (both company_domain and company_name were empty).

confidence tells you how much to trust the result:

• high: URL confirmed via direct LinkedIn validation or unambiguous Google result.
• low: no result found, or error state.

Use confidence as a Clay view filter. Pass high rows straight to your enrichment pipeline. Review not_found rows manually or route them to a secondary enrichment source.

---

Social URLs

Facebook and Instagram company page URLs are included as bonus fields at no extra charge. After LinkedIn resolution completes, the actor runs a second targeted Google search to find the company's Facebook page and Instagram profile. When found, the URLs are returned in facebook_url and instagram_url. When not found, both fields return null.

---

Sample output

Successful resolution with all fields:

{
  "company_domain": "stripe.com",
  "company_name": "Stripe",
  "linkedin_company_url": "https://www.linkedin.com/company/stripe",
  "linkedin_slug": "stripe",
  "resolution_method": "pattern_match",
  "confidence": "high",
  "facebook_url": "https://www.facebook.com/StripeHQ",
  "instagram_url": "https://www.instagram.com/stripe",
  "run_date": "2026-04-15T12:00:00.000Z"
}

Google search fallback with null social fields:

{
  "company_domain": "obscure-startup.io",
  "company_name": "Obscure Startup",
  "linkedin_company_url": "https://www.linkedin.com/company/obscure-startup",
  "linkedin_slug": "obscure-startup",
  "resolution_method": "google_search",
  "confidence": "high",
  "facebook_url": null,
  "instagram_url": null,
  "run_date": "2026-04-15T12:00:00.000Z"
}

---

Clay integration

Use this actor as a fallback enrichment column in any Clay table where linkedin_company_url is empty after native enrichment.

1. Add a formula column: needs_linkedin = {{linkedin_company_url}} is empty.
2. Add an Apify enrichment column. Search for domain-to-linkedin-url-resolver.
3. Map company_domain to your domain column. Optionally map company_name to your company name column for better accuracy.
4. Set run condition: needs_linkedin equals true.
5. Map output fields to new columns: resolved_linkedin_url, confidence, facebook_url, instagram_url.
6. Add a view filter: confidence equals high.

This runs only on rows where Clay native enrichment failed, keeping credit costs low.

---

Pricing

$0.03 per domain resolved. Actor start fee: $0.00005. No separate charge for social URL resolution.

1,000 domains costs $30. Run it as a fallback layer only and your average cost per enriched row stays well under $0.01.

---

Known limitations

• Pattern match works best for companies with straightforward slug patterns. Obscure or rebranded companies fall through to Google search.
• Social URL coverage is best-effort. Not every company has a crawlable Facebook or Instagram page.
• LinkedIn blocks direct scraping. This actor uses slug validation via HTTP, not scraping.
• Google search results vary by region and by query freshness.
• Name-only resolution (no domain) relies entirely on Google search and may return less accurate results for companies with common names.

---

Related actors

Related actors section to be added in a future README pass across all Mamba Labs actors.

---

Built by Mamba Labs.