B2B Leads List Builder — Maps + Email + Phone Enrichment avatar

B2B Leads List Builder — Maps + Email + Phone Enrichment

Pricing

from $4.90 / 1,000 b2b leads

Go to Apify Store
B2B Leads List Builder — Maps + Email + Phone Enrichment

B2B Leads List Builder — Maps + Email + Phone Enrichment

Give it a city + industry, get a ready-to-work B2B prospect list: company, website, email, phone, address, industry, LinkedIn — one flat row per lead, in one run. Maps search → website visit → email + phone harvest → MX-verify. No chaining actors.

Pricing

from $4.90 / 1,000 b2b leads

Rating

0.0

(0)

Developer

Vitalii Bondarev

Vitalii Bondarev

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Share

Give it a city + an industry. Get back a ready-to-work B2B prospect list — company name, website, email, phone, address, industry, and LinkedIn — as one flat row per lead, in a single run.

Most "leads" tools hand you either raw map listings (name + address, no way to reach anyone) or a domain-only list you then have to feed into a second actor to find emails, and maybe a third for phones. This actor runs that whole waterfall for you in one pass:

Google Maps search → visit each business website → harvest email + phone + socials → MX-verify → flat lead row

No chaining actors. No stitching datasets together. One input, one output, ready for your CRM or sequencer.


What you get — one flat row per lead

FieldDescription
company_nameBusiness name from Google Maps
websiteBusiness website URL
emailBest harvested email (MX-verified when verification is on)
phonePhone number (from Maps and/or the website)
addressFull street address
city / state / countryAddress split into parts for filtering & dedupe
industryPrimary category (e.g. "Marketing agency", "Dentist", "Plumber")
maps_rating / maps_review_countGoogle Maps social proof — qualify before you reach out
linkedin_urlCompany LinkedIn profile, when linked from the site
all_emailsEvery distinct email found (not just the primary)
email_statusvalid · role · risky · invalid · found · none
email_sourceWhere the email came from (website_contact / website)
social_linksOther social profiles found (Twitter/X, Facebook, Instagram, …)
parse_confidence0–1 quality signal per row
scraped_atUTC timestamp

By default the actor returns only reachable leads — every row carries at least an email or a phone. Name-only listings you can't actually contact are dropped (and never charged). Flip requireContact off if you also want the no-contact places.


Why one run instead of three

The cheapest way to get to a usable prospect list today is to chain: a Maps scraper → an email finder → a contact extractor, exporting and re-importing a dataset between each. That's three runs, three bills, and a brittle pipeline.

This actor bakes the proven contact-enrichment logic from our email-finder and website-contact-extractor directly into the Maps crawl. For each place that has a website, it fetches the homepage plus the highest-yield contact pages (contact / about / imprint / team), de-obfuscates the common name [at] domain [dot] com tricks, pulls emails, phones and social profiles, and — when verifyEmails is on — MX-verifies each address so you know the domain actually accepts mail before you send.


Input

{
"queries": [
"marketing agencies in Austin TX",
"dentists in San Francisco CA",
"plumbers near Denver CO 80202"
],
"maxResults": 50, // places per query (1–300, auto-paginated)
"requireContact": true, // only return leads with an email or phone
"verifyEmails": true, // MX-verify each harvested email
"language": "en",
"country": "us",
"proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}

Tips

  • One query ≈ one "industry in a city". For full coverage of a large metro, split into narrower queries (per neighborhood or sub-category) — Google itself caps a single area at ~120–300 places.
  • Residential proxy is required: Google Maps blocks datacenter IPs. The GOOGLE_SERP proxy group does not support Maps — leave the default RESIDENTIAL.

Output example

{
"company_name": "Acme Marketing Co",
"website": "https://acme.com",
"email": "hello@acme.com",
"phone": "+1 512-555-0100",
"address": "500 Congress Ave, Austin, TX 78701, USA",
"city": "Austin",
"state": "TX",
"country": "US",
"industry": "Marketing agency",
"maps_rating": 4.7,
"maps_review_count": 88,
"linkedin_url": "https://linkedin.com/company/acme",
"all_emails": ["hello@acme.com", "info@acme.com"],
"email_status": "valid",
"email_source": "website_contact",
"parse_confidence": 1.0,
"scraped_at": "2026-06-14T12:00:00Z"
}

Pricing

Pay per enriched lead. You're charged only for billable leads — rows with a company name and at least one reachable contact (email or phone). Map listings that yield no contact are dropped at no charge, so you're not paying for rows you can't use.

Example: a run that returns 100 enriched leads costs 100 × the per-lead price. Empty shells dropped along the way are free.

Platform compute (proxy, runtime) is billed to your own Apify account at Apify's standard rates, as with every Store actor.


Use cases

  • SDR / outbound — build a targeted list of "industry in city" prospects with verified emails, ready to drop into your sequencer.
  • Local market research — map every competitor in a category and metro, with ratings and review counts to gauge market density.
  • Recruiting / agency prospecting — find businesses in a vertical and reach the right inbox without buying a seat in an enrichment SaaS.
  • CRM enrichment — feed a list of "category + city" searches and get flat rows you can import directly.

This actor collects publicly available business contact information (the same data a person sees on Google Maps and on the businesses' own public websites). You are responsible for using the output in compliance with applicable laws and regulations (including GDPR/CCPA and anti-spam rules such as CAN-SPAM) and with the terms of the platforms you operate on. Verify consent and legitimate interest before sending marketing communications. The actor does not access private, gated, or login-protected data.

Email verification is performed at the MX layer (does the domain accept mail?). It does not guarantee that a specific mailbox exists — a full SMTP probe is unreliable on cloud infrastructure where outbound port 25 is blocked. email_status is an honest signal, not a delivery guarantee.