Public B2B Contact Lookup — Lusha Alternative

Look up public business contact evidence for people and employer domains you already know. Export published contact values, source URLs, page context, timestamps, and per-contact outcomes for CRM review. For CRM owners, each dataset result records a known person's public company-page contact evidence and collection outcome.

Workflow: put the results to work

Begin with a known person and employer domain from your CRM. Review the public page context alongside any contact value, then decide whether the record needs correction or additional research. The lookup preserves observed evidence without asserting mailbox ownership.

Best fit and next step

Choose this Actor when your workflow begins with a person and employer domain you already know, and your decision needs fresh, reviewable website evidence. It is designed as a focused standalone workflow for CRM cleanup, account research, and contact-review queues.

For broad prospect discovery, proprietary emails, direct dials, mobile data, or sales-suite orchestration, continue with an approved licensed data provider whose coverage and permitted use match that wider job.

Workflow story

An operations specialist starts with a CRM list containing each person’s full name and employer domain. The specialist passes that list to this Actor, then receives one cited evidence row per accepted contact. Next, the specialist reviews the source URL and role context, exports the dataset, and feeds confirmed records into the team’s approved CRM-quality or research process.

Input

Supply one to 25 known contacts. Optional company-owned sourceUrls make the check especially precise; otherwise the Actor starts from the homepage and a small set of standard public routes.

{
    "contacts": [
        {
            "fullName": "Ada Lovelace",
            "companyDomain": "example.com",
            "companyName": "Example Ltd",
            "externalId": "crm-001",
            "sourceUrls": ["https://example.com/team/ada-lovelace"]
        }
    ],
    "maxContacts": 25,
    "maxPagesPerContact": 3,
    "requestTimeoutSecs": 10,
    "responseFormat": "detailed",
    "useApifyUnblockerFallback": true
}

Output dataset

The default dataset contains one complete evidence row for each accepted contact. Every contact value carries the public company-page URL that supported it.

Field	Meaning
nameMatched	The supplied full name appeared in visible text on a public page of the supplied company domain.
identityEvidence	Source URL, page title, and optional surrounding role context for each match.
publishedBusinessEmails	Business email values visibly published on a matched page, each with source URLs.
publishedBusinessPhones	Telephone-link values visibly published on a matched page, each with source URLs.
collectionOutcome	Per-contact collection state for a match, a completed empty check, or a source-recovery result.
collectedAt	ISO 8601 collection time for downstream freshness review.

{
    "contactKey": "crm-001",
    "externalId": "crm-001",
    "fullName": "Ada Lovelace",
    "companyDomain": "example.com",
    "companyName": "Example Ltd",
    "nameMatched": true,
    "profileUrl": "https://example.com/team/ada-lovelace",
    "publicTitle": "Leadership | Example Ltd",
    "roleSnippet": "Ada Lovelace, Chief Scientist",
    "publishedBusinessEmails": [
        {
            "value": "ada@example.com",
            "sourceUrls": ["https://example.com/team/ada-lovelace"]
        }
    ],
    "publishedBusinessPhones": [],
    "publishedLinkedInProfileUrls": [],
    "identityEvidence": [
        {
            "sourceUrl": "https://example.com/team/ada-lovelace",
            "pageTitle": "Leadership | Example Ltd",
            "roleSnippet": "Ada Lovelace, Chief Scientist"
        }
    ],
    "fetchedSourceUrls": ["https://example.com/team/ada-lovelace"],
    "matchedSourceUrls": ["https://example.com/team/ada-lovelace"],
    "fetchRoutes": ["direct"],
    "collectionOutcome": "MATCHED_PUBLIC_CONTACT",
    "warnings": [],
    "collectedAt": "ISO-8601 timestamp supplied at collection time"
}

OUTPUT provides the compact run outcome and count summary. RUN_SUMMARY adds route, charge, and collection diagnostics for a complete readback.

Comparison: a bounded workflow alongside Lusha

Decision dimension	This Actor	Lusha and broader prospecting suites
Workflow scope	Starts with a known person and employer domain, then collects bounded public company-page evidence.	Supports wider prospecting and contact-data workflows.
Billing and same-job cost	Pay per event pricing is stated per public name-match evidence record, with platform usage shown separately.	Plan and credit allocation guide the applicable workload cost.
Effective efficiency	One machine-readable row keeps identity evidence, source URLs, collection time, and outcome together for operator review.	Broader suite workflows can serve data-search and sales-process needs.
Input friction	Full name and employer domain create a focused, auditable starting point.	Search and filtering workflows can start from broader prospecting criteria.
Output contract	Typed public values carry their source URLs, plus a concise outcome and warnings.	Product-specific records and fields depend on the selected Lusha workflow.
Integrations and automation	Apify dataset/API readback supports batch handoff and scheduled operation after live configuration.	Lusha documents its own integration and workspace capabilities.
Freshness and provenance	Each collection pass reads public pages again and records collection time alongside source URLs.	Provider database freshness follows the provider’s documented operations.

API example

curl -sS -X POST "https://api.apify.com/v2/acts/khadinakbar~lusha-alternative/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "contacts": [
      {
        "fullName": "Ada Lovelace",
        "companyDomain": "example.com",
        "externalId": "crm-001"
      }
    ],
    "maxPagesPerContact": 3
  }'

After collection completes, read the default dataset together with OUTPUT and RUN_SUMMARY for source provenance, collection outcome, and event-charge readback.

AI agent and MCP guidance

An AI agent or MCP client can use the Actor as a bounded public-evidence step before a downstream CRM-quality decision.

Check these known CRM contacts against public pages on their supplied employer domains. Return the dataset rows, cite the source URLs, read the OUTPUT outcome, and keep the resulting contact evidence separate from broad prospect discovery.

The agent should preserve externalId, use collectionOutcome to route follow-up, and include source URLs and collection time in any human-facing summary. The event price and platform usage remain part of the run’s cost context.

Practical guidance

Provide the most specific public team, leadership, or bio page through sourceUrls when it is already known. Start with a small contact set, confirm the cited source context, then schedule the same focused input pattern for recurring CRM-quality work. The direct route receives a short retry, and Apify Unblocker can add a single public-page route when enabled.

Builder's note

I designed this Actor around a simple invariant: every returned contact value should point back to a public page owned by the supplied employer domain. My goal was a small, reviewable evidence set that helps a person make a clear CRM or research decision without hiding the source context.

Responsible use

Use contacts and company domains you are authorized to research, respect applicable laws and site terms, and review the cited public page before taking downstream action. Public availability supports evidence review; your organization’s privacy, marketing, employment, and data-governance standards guide the next step.

Relationship to Lusha

Lusha is a trademark of its owner. This independent Actor is not affiliated, associated, or endorsed by Lusha.

Provider architecture

The primary workflow reads the public employer pages supplied by the caller, so it operates without a third-party contact-data API. A future data-provider route can be added after an approved pay-per-use provider, permitted-use review, field-parity probe, and live acceptance matrix are in place.

Pricing and run costs

This Actor uses Pay per event plus Apify platform usage. The Pricing tab lists the current event rates and billing terms.

Event	Billing unit	When it applies
apify-actor-start	Actor Start	Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
public-contact-found	Public contact evidence found	One persisted, source-cited record where the supplied person appeared on a public page of the supplied company domain. Valid-empty, invalid, and unavailable-source records are not charged.

Run cost combines the charged events and Apify platform usage. Review the run charge limit and requested result count before starting.

Connect an AI agent

Use the Apify MCP configurator to choose an available client connection. Inspect this Actor’s current input schema and required credentials before running it.