Local Lead Finder Pro — Business Contacts & Website Audit

Find US local businesses by category and city, or enrich business websites you already have. Get published contact details, website signals, an explainable lead score and an editable outreach draft in one run. No external API key or website account is required.

$4 per 1,000 delivered leads + $0.00005 per start at up to 1 GB. Start charges scale with memory above 1 GB. Website enrichment is included in the result event. Platform resource usage is charged separately under the active pricing configuration checked on 20 October 2026; check the Pricing tab and your run's actual usage.

First run

1. Enter a business category and US city/state.
2. Keep pages: 1 and maxResults: 25 for a small sample.
3. Start the Actor. Open Results for leads, then SUMMARY for source coverage and ERRORS for incomplete checks.

{
  "workflow": "findLeads",
  "category": "plumbers",
  "location": "New York NY",
  "pages": 1,
  "maxResults": 25,
  "outputPreset": "sales"
}

Directory results can include nearby cities and related categories. Each requested page is collected separately; the run covers a bounded sample, rather than every business in the market.

Enrich websites you already have

{
  "workflow": "enrichUrls",
  "startUrls": ["meditofoundation.org"],
  "maxResults": 1,
  "outputPreset": "contacts",
  "crawlSubpages": true,
  "verifyEmails": true,
  "enrichBrandAge": false
}

Use public business domains or HTTP(S) URLs. URLs containing credentials, private hosts or unsupported schemes are rejected before collection. Repeated domains are merged. A direct website that cannot be read produces a diagnostic and no paid lead. A directory business can still be useful when its website cannot be read: published phone/address data is retained with partial enrichment.

combined requires both search fields and website URLs. auto detects the workflow from the supplied fields. Direct enrichment requires enrichWebsites: true.

What a lead contains

Fields	Meaning
leadId, source, observedAt	Stable identity, directory/website origin and observation time
Business Name, businessNameSource	Published business name where available; an explicit domain fallback otherwise
Phone, phoneE164, Address, City, State, Listing URL	Public directory contact/location evidence; source-dependent
emailsFromWebsite, contactEvidence, contactPageUrl	Addresses actually published on a website, with the page where each contact was observed
emailDetails, bestEmail, bestEmailStatus	Published addresses and DNS-only confidence. mx_present, no_mx, unknown, not_checked, disposable or invalid
emailGuesses	Separate unverified guesses, never promoted to bestEmail or the CSV Email column
socialProfiles, socialSearchUrls	Links published by the site, versus generated search links for manual research
ownerName	Explicitly published owner/founder name when found; article authors and generic team greetings are excluded
websiteAlive, websiteCheckStatus, websiteSslValid	Readable page, observed missing page, or unknown/blocked response; TLS verification stays enabled
websiteTechStack, mobileFriendly, seoAudit	HTML/header patterns, responsive HTML signals and five basic SEO checks; heuristic observations rather than performance audits
leadScore, leadTier, leadScoreReasons	Explainable agency-oriented heuristic, not a sales probability
outreachPitch, bestContact	Editable rule-based draft and a published contact route

Email DNS checks do not verify a mailbox, deliverability or catch-all status. mailboxVerified is false; deliverable and catchAll remain null. A site publishing an address does not prove that its inbox currently works.

onlyWithoutWebsite means no business website was linked by the collected directory listing. Unknown HTTP responses do not mean a dead business. A 404/410 describes the linked page checked. Website names, owner names, coordinates and contacts may be absent.

Controls and filters

Input	Default	Purpose
workflow	auto	findLeads, enrichUrls, combined or auto-detection
category, location	—	Both required for discovery
startUrls	[]	Supplied public website list
pages	1	1–10 result pages
maxResults	25	1–10,000 delivered leads, after sorting/filtering
minLeadScore	0	Minimum agency-opportunity score, 0–100
onlyWithoutWebsite	false	Listings without a linked business site
excludeChains	false	Heuristic exclusion of known chain names; review classifications
enrichWebsites, crawlSubpages	true	Read a homepage, then up to three contact/about/team pages if no email is found
verifyEmails	true	DNS-only checks for published emails
extractOwnerName	true	Look for explicit ownership/founder evidence
enrichEmailGuesses, enrichSocialUrls	true	Clearly separated suggestions/search links
includeOutreachPitch	true	Editable draft grounded in observed fields
enrichBrandAge	true	Years since the earliest returned archive snapshot; not business or domain registration age
enrichGeocode	false	Optional address coordinates; public requests serialized to at most one per second
maxConcurrency	3	1–5 concurrent discovery pages
timeout	120	Per-page collection wait, 30–300 seconds, within the run budget
runBudgetSecs	170	Overall bounded collection/enrichment budget, 30–600 seconds
outputPreset	sales in the form	contacts, sales, full; API calls omitting it retain full output
exportFormat	default	JSON preset, csv flat CRM columns, or both full JSON plus _csv

The result limit caps delivered events, not discovery/enrichment work. Use the platform maximum charge control as an additional cap. Larger lists may finish with partial coverage under the time budget. Unavailable archive/geocode services return unknown fields.

Lead score and outreach

The score is clamped to 0–100. Core signals include no linked website (+40), observed missing linked page (+25), DIY-builder patterns (+15), review/rating evidence, address/hours, archive and contact signals, plus a chain penalty. Reasons accompany each lead. Tiers are cold below 35, warm 35–54, hot 55–74 and on-fire from 75.

These are prioritization hints for website-service agencies. Responsive and SEO flags are checks on available HTML, rather than a rendered mobile usability test or Google ranking. Outreach drafts ask about the observed situation and contain no invented revenue, conversion results or delivery promises. Review and edit before using them.

Results, billing and partial runs

The Dataset contains one delivered business per row. Export it as JSON, CSV or Excel, or choose exportFormat: "csv" for flat CRM column names. Summary and error records are stored in the run's Key-value store and do not incur result events.

• SUMMARY: actual delivered/charged rows, discovery pages, valid/rejected counts, filters, coverage and OK, EMPTY, PARTIAL, FAILED or FAILED_PARTIAL.
• ERRORS: safe stage/page/lead diagnostics; invalid cards and unreadable direct websites are excluded from paid output.
• Valid filters returning no leads produce EMPTY. Source failures produce FAILED, or PARTIAL when useful leads survive. Invalid input fails before source requests.

For 25 delivered leads at up to 1 GB, the Actor events are $0.10005. For 1,000, $4.00005. Add the separately billed platform resource usage. There is no separate website, DNS, CSV or summary event.

API and MCP

Actor: apivault_labs/local-business-lead-finder-pro

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("apivault_labs/local-business-lead-finder-pro").call(
    run_input={
        "workflow": "findLeads",
        "category": "dentists",
        "location": "Chicago IL",
        "maxResults": 10,
        "outputPreset": "contacts",
    }
)
leads = list(client.dataset(run["defaultDatasetId"]).iterate_items())
summary = client.key_value_store(run["defaultKeyValueStoreId"]).get_record("SUMMARY")

Connect an MCP-compatible client through Apify MCP and select this Actor. The tool is apivault_labs--local-business-lead-finder-pro; it accepts the same input fields. Ask it to find three plumbers in New York, read the Dataset, then check SUMMARY before describing coverage. Storage tools can read Dataset items and SUMMARY/ERRORS without another collection run.

Public sites can block automated reads, change fields or omit contacts. This Actor returns current public observations, with source-dependent coverage. It does not send outreach, infer private contacts, guarantee mailbox availability or enumerate the entire local market.

Two starting points for local business lead generation

Use discovery when you need a bounded sample of US directory businesses. Use website enrichment when your CRM, client list or research already gives you the domains. The two routes have different provenance: a directory listing may supply address/phone evidence, while a supplied website does not establish that the business belongs to a particular city or category.

Need	Workflow	Useful output
Local agency prospecting	findLeads	Directory business records plus optional website observations
Enrich an existing account list	enrichUrls	Published contacts and page-derived business signals
Research both audiences in one job	combined	Separate directory/website source evidence
Prepare CRM fields	Contacts preset or CSV export	Stable lead identity and available contact routes
Review website-service opportunities	Sales preset	Explainable signals and an editable draft

Inspect one known business website first

This input avoids a broad directory search and turns off optional archive and generated contact guesses. A useful website row requires a readable public website. Missing phone or email remains missing rather than becoming a claim that the business has no contact route.

{
  "workflow": "enrichUrls",
  "startUrls": [
    "https://meditofoundation.org"
  ],
  "maxResults": 1,
  "enrichWebsites": true,
  "crawlSubpages": true,
  "enrichBrandAge": false,
  "enrichEmailGuesses": false,
  "outputPreset": "contacts"
}

Search a small local-service audience

Use a specific city/state and keep the result and page limits explicit. Directory results can include related services and nearby locations. Check each listing rather than treating the category string as independently verified business classification.

{
  "workflow": "findLeads",
  "category": "plumbers",
  "location": "New York NY",
  "pages": 1,
  "maxResults": 5,
  "enrichBrandAge": false,
  "outputPreset": "sales"
}

Research listings with no linked website

The filter means the collected directory card supplied no business website. It does not prove the company has no domain, social presence or newly built site. Review the listing before using a no-website pitch.

{
  "workflow": "findLeads",
  "category": "dentists",
  "location": "Chicago IL",
  "pages": 1,
  "maxResults": 5,
  "onlyWithoutWebsite": true,
  "enrichBrandAge": false,
  "outputPreset": "sales"
}

Export a flat record for a spreadsheet review

The CSV option changes the delivered representation, not the evidence that was collected. Keep source and observation columns beside the contact fields. A published email is not a validated sales recipient.

{
  "workflow": "enrichUrls",
  "startUrls": [
    "https://meditofoundation.org"
  ],
  "maxResults": 1,
  "exportFormat": "csv",
  "enrichBrandAge": false,
  "includeOutreachPitch": false
}

From observed website signals to a useful agency brief

A practical handoff contains the business identity, source URL, contact evidence, observation date and the particular issue you intend to inspect. Keep your interpretation separate from the Actor's observations. A lead score can rank that queue; it is not proof the business wants a redesign.

HTML/header checks are limited screening signals. A responsive markup hint is not a rendered device test, and a basic SEO flag is not a search ranking. If the account matters, open the site and perform the checks appropriate to the service you would actually deliver.

Published contacts, generated email guesses and social search URLs have different status. Only observed contacts should be treated as published evidence. Generated suggestions are research aids; they are not verified person identities, discovered company profiles or confirmed inboxes.

Budget and recovery for a business enrichment job

The active configuration checked on 20 October 2026 is $0.004 per delivered lead plus a $0.00005 start event per memory unit, minimum one unit, and user-paid platform usage. Five delivered leads at standard memory have $0.02005 in event fees; ten have $0.04005. The arithmetic is separate from a measured run total and does not promise matching coverage.

There is no separate per-page or DNS verification event. Enrichment still uses resources, including when a site is unreadable. A readable directory record can be a billed partial lead with unavailable website fields; an unreadable direct website is reported as a diagnostic instead of a useful paid website record. Inspect SUMMARY before deciding how to retry.

Save the run and dataset IDs. Re-download an existing completed result when a file transfer fails. Repeating collection is a new run, with applicable charges and no general cross-run deduplication guarantee. Use leadId and source-aware keys in your destination rather than assuming a website domain uniquely represents every local business location.

Questions from agency and CRM workflows

Can I use the outreach draft without reviewing it?

Review and edit it first. It is a rule-based suggestion from observed fields, not a claim about revenue, an email-delivery test or permission to contact someone. The Actor does not send the message.

Is brand age the company's founding date?

No. The optional archive observation describes time since the earliest returned snapshot. Missing snapshots, changed domains and earlier business history can make that different from company or domain registration age.

Are the websites and contact details verified in real time?

The run observes what available public pages return. Availability, ownership and freshness can still vary. DNS mail observations do not establish a working mailbox, and blocked responses remain unknown rather than dead.

Can I automate review in n8n or Python?

Yes. Use the linked community node or public client, retain provenance, then route leads to a review queue or your own CRM rules. A public npm package does not by itself establish availability in n8n Cloud.

n8n and developer integrations

Use this Actor in your automation or application with the existing community integrations below. An Apify account and API token are required; Actor and platform charges follow the current pricing.

• n8n community node: n8n-nodes-apivault-local-lead-finder-pro. Install package name n8n-nodes-apivault-local-lead-finder-pro in a self-hosted n8n instance that permits community packages.
• Python client and examples: GitHub.
• n8n source and usage: GitHub.

These are community packages. Publication on npm does not establish n8n verification or availability in n8n Cloud. Review the linked package README for supported inputs and setup.

Discovery budget and source failures

Directory submission and polling share one attempt deadline. runBudgetSecs limits the whole discovery/enrichment phase; discovery uses at most110seconds within that budget. Source timeouts, access denials and rate limits are reported separately in SUMMARY.sourcePages and ERRORS. A denied or timed-out page is not resubmitted repeatedly. Completed valid pages remain available if another page fails. With no useful rows, source failure is FAILED with0paid result rows; it does not prove that the city has no businesses.

maxResults is a delivered-row cap after quality checks, filters and deduplication. It does not promise that many available leads. pages, source availability, onlyWithoutWebsite, minLeadScore, chain filters, time and charge budgets can reduce the result. Contact enrichment and complete directory coverage are not guaranteed.