Zomato Email Scraper - Keyword & Location Targeting
Pricing
from $2.50 / 1,000 results
Zomato Email Scraper - Keyword & Location Targeting
π Zomato Email Scraper pulls restaurant and food business emails by keyword and location. π Custom domain filters, hidden-address decoding and dedup. π€ Export Zomato leads to CSV, JSON or Excel for hospitality sales.
Pricing
from $2.50 / 1,000 results
Rating
0.0
(0)
Developer
Scrapido
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
16 hours ago
Last modified
Categories
Share
Zomato Email Scraper π
Zomato Email Scraper helps marketers, recruiters, and sales teams stop manually hunting for contact details by extracting emails from Zomato using keywords and filters. Itβs designed for Zomato email extractor workflowsβideal for extract emails from Zomato and streamlined Zomato lead generation at scale, fast, and with structured results.
π Key Features of Zomato Email Scraper
| Feature | Benefit |
|---|---|
| β Targeted Keyword Search | Reach the exact Zomato audience you need with focused keywords |
| β Location Filtering | Narrow results to a specific city, region, or country to improve relevance |
| β Custom Domain Filter | Extract only email addresses matching your chosen domains (like @gmail.com or @yahoo.com) |
| β Bulk Export (Dataset Output) | Each discovered record is saved to your Apify dataset for easy downstream use |
| β Proxy-Ready Runs | Built for reliable automated scraping with Apify Proxy support |
| β Real-Time Saving | Results are pushed incrementally so long runs donβt lose progress |
| β Resume Support | Automatically continues from the last saved cursor if the run stops or is interrupted |
π₯ Input β Zomato Email Scraper Parameters
{"keywords": ["manager", "founder"],"location": "","customDomains": ["@gmail.com", "@yahoo.com"],"maxEmails": 20}
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
keywords | Array | β Yes | β | A list of keywords or queries to search for when looking for relevant Zomato profiles |
location | String | No | "" | Location to filter results (for example, a city or region) |
customDomains | Array | No | ["@gmail.com","@yahoo.com"] | List of custom email domains to filter extracted emails (e.g., @gmail.com, @yahoo.com) |
maxEmails | Integer | No | 20 | Maximum number of emails to collect for the run (higher can take longer, and wonβt guarantee hitting the number) |
π€ Output β What Zomato Email Scraper Returns
The actor saves each result as a JSON record in your Apify dataset.
{"keyword": "manager","title": "City Center Bistro - Operations Manager","description": "Operations and partnerships for City Center Bistro. Contact for restaurant collaborations and group bookings.","url": "https://www.zomato.com/mumbai/city-center-bistro","email": "ops.citycenterbistro@gmail.com"}
| Field | Label | Format | Description |
|---|---|---|---|
keyword | Keyword | text | The keyword that was used for the search which surfaced this result |
title | Title | text | Zomato profile name or business title associated with the contact |
description | Description | text | Bio or profile summary text captured for context |
url | Url | link | Direct link to the Zomato profile for the scraped lead |
email | text | Email address extracted for outreach (filtered to your chosen domains) |
π» How to Use Zomato Email Scraper β Step-by-Step
- Open the Actor β Launch Zomato Email Scraper in Apify and view the input form.
- Enter Keywords β Add job titles, roles, or query terms you want to target for Zomato email extraction.
- Set Location (optional) β Narrow results using the
locationfilter for more relevant Zomato contact leads. - Filter by Domain (optional) β Use
customDomainsto focus on email harvesting for specific providers or company domains. - Set Max Emails β Control run size with
maxEmailsso you can manage cost and runtime for your Zomato email list. - Run the Actor β Start the run and monitor progress in logs.
- Export Results β Download the dataset items (JSON/CSV) from Apify for CRM import and outreach workflows.
No coding required. Results appear in your dataset as the run progresses.
π‘ Best Use Cases for Zomato Email Scraper
- π― B2B Lead Generation β Build a Zomato lead generation list for outbound sales outreach
- π£ Email Marketing β Enrich campaigns with restaurant email extraction contacts
- π€ Recruitment β Find relevant roles for automated contact retrieval
- π¬ Market Research β Support Zomato data mining around locations and roles
- π CRM Enrichment β Add scraped business emails to existing lead records for faster activation
Disclaimer
This actor only accesses publicly available data on Zomato. It does not scrape private profiles, authenticated content, or password-protected pages. Users are solely responsible for ensuring their use complies with Zomatoβs Terms of Service and applicable privacy/anti-spam regulations in their region. Use this tool only for legitimate purposes such as lead generation and research. For data-removal requests, contact π§ scrapidocontact@gmail.com.
π Support & Feedback
Have a question or found an issue with the Zomato Email Scraper? We're here to help.
- π Bug Reports: Open a ticket in the repository's Issues section
- β¨ Custom Solutions & Feature Requests: Reach out to our team
- π§ Email: scrapidocontact@gmail.com
Your feedback helps improve the Zomato email scraper experience for real-world web scraping tool workflows.
Multiple Email Types
Email Types replaces the old single Audience Type choice: select as many kinds of mailbox as you want and the run chases all of them together.
| Type | What it matches |
|---|---|
| Personal / free webmail | Gmail, Outlook, Yahoo, iCloud, AOL, Proton, ... |
| Business / corporate | Company domains - free webmail and institutions excluded |
| Education (.edu / .ac) | .edu, .ac.uk, .edu.au, .ac.in and other academic suffixes |
| Government (.gov / .mil) | .gov, .mil, .gov.uk, .gc.ca, ... |
| Non-profit (.org) | .org, .ngo, .org.uk, ... |
Each selected type contributes its own Google dork patterns and its own domain
test, so a result is only kept if it genuinely belongs to the type that found
it. Every row carries an emailType field recording which one that was.
Suffixes are matched as real domain suffixes, so cs.mit.edu counts as
Education while notedu.com does not.
Setting Custom Email Domains still overrides everything: an explicit domain
list is a manual override and replaces the type-driven patterns. The legacy
audienceType value is still accepted, so saved inputs keep working.