Roofing Contractor Lead Scraper — Website Emails & Verification

Find roofing contractors, roof repair services, gutter services, and siding contractors by location. The actor searches Google Maps, discovers public website contact details, and exports business leads as Full, HubSpot, or Salesforce column layouts. Email availability and confirmation vary by business.

Quick start

Select a business type and location, set maxResults to 3, and inspect the output before scaling. For a custom query, select Custom. Use Full output to inspect email evidence; CRM imports may require field mapping.

{
  "businessType": "Roofing Contractor",
  "location": "Dallas, TX",
  "maxResults": 3,
  "enrichEmails": true,
  "verifyEmails": true,
  "enrichSocials": true,
  "outputFormat": "full"
}

Email evidence

DNS MX records show domain mail routing. They do not confirm a mailbox. emailVerified is true only when SMTP accepts the recipient and rejects a random address. Catch-all servers, blocked SMTP, timeouts, and temporary errors remain unconfirmed. Full output includes emailDomainHasMx, emailVerificationStatus, and notes. No emails are sent by this check, and delivery is not guaranteed.

Pricing

Current base fees are $50 per 1,000 returned leads. A lead with at least one SMTP-confirmed email adds $20 per 1,000 such leads. The start event costs $0.01 per GB of memory (minimum one event). Platform usage is additional. The live Pricing tab is authoritative.

For example, 100 base leads cost $5 in base result fees. If 20 have an SMTP-confirmed email, add $0.40, then add the start events and platform usage. A charged base record may have no email. Set a maximum run cost and timeout before larger runs.

Output and repeat use

Records can contain name, category, address, phone, website, Google Maps URL, rating, review count, website emails with verification evidence, and social links. Unavailable fields can be blank. Results are deduplicated by normalized business name and address within a run, enriched in batches, and written as each batch finishes. When combining cities or scheduled runs, deduplicate your merged dataset too.

Source blocks and failures can prevent output. Check the run log before repeating a failed run. A successful sample is not a guarantee that every city or website will work.

Support

Open an issue with a fresh run link, search settings, expected result, and observed result. Keep credentials and private data out of public issues. If the actor helps your workflow, an honest review helps other users evaluate it.