Apify Local Business Leads Osm

Local business leads from OpenStreetMap

Turn "I need local businesses in <city> with emails" into one scored, deduplicated lead table without touching Google Maps: businesses are discovered on OpenStreetMap, each business's own public website is crawled for a contact email, phones and social profiles, every email is MX-verified inside the same run, and the user knows the cost ceiling before the run starts.

Disclosure: the author of this skill owns the Actor it routes to (flash_scraper/local-business-leads). It is a pay-per-result Actor on the Apify Store; no referral or tracking parameters are used anywhere in this skill. For Google star ratings and review counts this skill sends the user elsewhere (see the boundary below).

Example prompts

Prompts this skill handles:

• "Get me 200 dentists in Austin with a verified email and a phone number, as a CSV."
• "I run a web-design agency: find hair salons in Lyon whose website is weak, or who have no website at all."
• "Here are 300 business websites from a conference exhibitor list; find and verify a contact email for each."
• "Every Monday, tell me which new restaurants appeared within 5 km of our downtown office."

Out of scope (the boundary):

• "Sort them by Google rating" or "only businesses with 4+ stars and 50+ reviews". OpenStreetMap carries no review data, and the Actor only sees a rating when the business publishes one on its own site (about 7% of rows, 4 of 55 on the 2026-08-08 reference run). For Google ratings and review counts route to the apify-google-maps-leads skill or compass/crawler-google-places directly.
• Different from apify-verified-email-finder: that skill starts from Google Maps, a Google SERP or a user-supplied URL list; this one discovers on OpenStreetMap and never touches Google. If the user already has a URL list and only wants emails verified, that skill is the shorter path; use this one when discovery itself must avoid Google.
• Person-level contacts (owner name, LinkedIn profile, direct dial). This Actor returns the business's published contact channels, not people; for named decision-makers use the leads-enrichment steps in apify-google-maps-leads.

Prerequisites

• Apify account (sign up)
• Authentication via one of:
  • apify login (OAuth, if using the Apify CLI)
  • APIFY_TOKEN environment variable
  • Token from Apify Console → Settings → Integrations

Never paste a token into a URL or into a file inside this skill; pass it as Authorization: Bearer (the CLI does this for you).

Workflow

Copy this checklist and track progress:

Task Progress:
- [ ] Step 1: Get the four anchors (category, city, what must every row have, how many)
- [ ] Step 2: Pick the search mode and check the live schema
- [ ] Step 3: Build the input and state the cost
- [ ] Step 4: Run and wait
- [ ] Step 5: Deliver: rows, fill rates, what the map could not supply

Step 1: Get the four anchors

Ask these as one block; do not start a run without them.

1. Category — plain English (dentist, HVAC contractor, hair salon). Several are fine. Warn up front that trades run from a van map thinly (see Step 5).
2. City — city plus region or country (Austin, Texas, Lyon, France). If the name exists in several countries ask for the country, and set countryCode.
3. What must every row have — the contactability floor. Default to "a website" for email work (onlyWithWebsite); "a verified email" for cold email (onlyVerifiedEmail); "a phone" for call lists (requirePhone); "no website" for first-website pitches (onlyWithoutWebsite).
4. How many — maxItems is the cost ceiling. Default to 25 for a first run; ask before going above 500.

Optional follow-ups, only if the user raises them: exclude chains or named brands, a radius around one address, a bring-your-own website list, a weekly new-business watch, a Slack/Discord webhook.

Step 2: Pick the search mode and check the live schema

Check the live input schema before building input (fields change; the schema wins over this file):

apify actors info "flash_scraper/local-business-leads" --input --json \
  --user-agent apify-awesome-skills/apify-local-business-leads-osm 2>/dev/null

The Actor runs without an API key, proxy, login or cookies. It never reads Google Maps; every row carries a constructed google_maps_url search link and an osm_url so the user can open the source in one click.

Step 3: Build the input and state the cost

Field names as in the live schema. Only category and location are required; everything else has a working default.

Cold-email list (the most common request):

{
  "category": "dentist",
  "location": "Austin, Texas",
  "maxItems": 100,
  "onlyWithWebsite": true,
  "onlyVerifiedEmail": true,
  "skipClosed": true,
  "excludeChains": true,
  "expandNearby": true
}

• onlyWithWebsite, onlyVerifiedEmail, requirePhone, requireSocial, requireAnyContact, excludeKeywords, excludeChains and skipClosed all drop rows before billing; the run log names each filter and how many rows it removed.
• expandNearby: true widens the search in rings around the city when the city runs out (measured 2026-08-15: dentist / Round Rock, Texas at maxItems: 100 delivered 21 rows without it and 100 with it, ring rows labelled in query_location).
• preset: "cold_email" sets onlyWithEmail + onlyVerifiedEmail for you; other presets are web_design, call_list, full_enrichment. A preset never overrides a field the user set.

Web-design prospects — businesses with a site, but a weak one:

{
  "category": "hair salon",
  "location": "Lyon, France",
  "countryCode": "fr",
  "onlyWithWebsite": true,
  "maxScore": 45,
  "requireAnyContact": true,
  "skipClosed": true
}

For businesses with no website at all use onlyWithoutWebsite: true instead (mutually exclusive with onlyWithWebsite; expect name, address, coordinates and sometimes a phone, nothing to crawl).

Enrich the user's own list (no map data fetched):

{
  "websiteList": ["aloha-dental.com", "averyranchdental.com"],
  "verifyEmails": true,
  "outputFields": ["domain", "email", "email_status", "email_type", "phone", "lead_grade"]
}

Weekly new-business watch: add "onlyNewBusinesses": true to any of the above and put it on a schedule. The first run is the baseline; later runs with the same categories, locations and filters deliver only businesses not delivered before, and a quiet week delivers 0 rows and bills nothing. Add "webhookUrl": "https://hooks.slack.com/..." for a Slack, Discord or JSON digest.

Cost, stated before the run. The Actor bills per delivered business; filtered rows and empty runs cost nothing, and MX verification is included. Read the current price from the Store Pricing tab (the schema fetch in Step 2 also returns the pricing block). As an illustration only, the free-plan rate read from the Store API on 2026-09-05 was $0.003 per lead, so 100 rows cost at most $0.30 and 1,000 rows $3.00; paid plans pay less. A pricing record scheduled for 2026-09-14 raises this to $0.005 per lead ($0.50 per 100 rows, $5.00 per 1,000), so read the live price rather than quoting these figures. Say the ceiling to the user in one sentence, and confirm before running above 500 rows.