# Zomato Email Scraper (`leads-scraper/zomato-email-scraper`) Actor

Zomato Email Scraper SD - Zomato Email Scraper is a lead generation tool that extracts leads with public contact emails, account names and profile URLs from Zomato results by keyword, location and email domain - Zomato email extractor.

- **URL**: https://apify.com/leads-scraper/zomato-email-scraper.md
- **Developed by:** [Leads Scraper](https://apify.com/leads-scraper) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.49 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### Zomato Email Scraper

The Zomato Email Scraper collects publicly indexed contact emails connected to `zomato.com`, the restaurant discovery platform that dominates India and has a large footprint in the UAE.
It builds Google queries with the `site:zomato.com` operator, fetches them through the Apify GOOGLE\_SERP proxy, and extracts emails from the result blocks.
No login, no browser, no Zomato API — only what Google has already published in its index.

**Start with the honest part.** Zomato indexes review and menu pages more than restaurant profiles, so many rows carry an email without a restaurant handle.
In a live test run, roughly 10 parsed results produced 8 unique emails but only 2 rows with a usable venue identity and 2 resolvable profile URLs.

So the Zomato Email Scraper is email-dense and identity-thin.
If your workflow keys on the address itself — deduplication, CRM matching, cold outreach — that trade is fine. If you need a clean restaurant name on every row, plan enrichment or use a sibling Actor alongside it.

#### What one run of the Zomato Email Scraper produces

Each dataset row is one unique email plus whatever context Google printed around it.
You get the raw title, an account label where one exists, a cleaned snippet, the exact query used and a truncation flag.
The Zomato Email Scraper pushes rows to the Apify dataset as they are found, so you can export CSV, JSON or Excel mid-run.

#### Exporting and integrating the Zomato Email Scraper dataset

Because rows are written incrementally, an aborted or migrated run still leaves a usable dataset behind.
Export from the Apify console, pull the dataset over the API, or schedule the Zomato Email Scraper and push results straight into your CRM.

### How the Zomato Email Scraper works: Google SERP parsing, not an API

The Zomato Email Scraper runs the same six steps on every query it builds.

1. It reads your input: keywords, location, email domains and limits.
2. It builds Google queries with the `site:` operator, for example `site:zomato.com dhaba "@gmail.com" catering`.
3. It fetches result pages through the Apify GOOGLE\_SERP proxy using async `aiohttp` requests.
4. It parses each result block structurally — locating the `<h3>` and the smallest surrounding block — rather than by CSS class name.
5. It extracts emails with a domain-filtered regex and normalises obfuscated forms.
6. It deduplicates globally and pushes each lead to the dataset immediately.

There is no browser, no JavaScript rendering, no authentication and no cookies.
The Zomato Email Scraper never signs into Zomato and never requests pages from Zomato's own servers.
Everything it returns was already public in Google's search index.

### Local keywords and `countryCode` in the Zomato Email Scraper

`countryCode` and locally-worded keywords are the two real levers you have on this platform, and most disappointing runs come from ignoring both.
Zomato's index is concentrated in India and the UAE, and Google personalises results by country vantage point.

Set `countryCode` to `IN` for India or `AE` for the UAE, and run them as separate jobs.
A default or US-vantage search will bury `zomato.com` pages behind global results and cut your row count sharply.

#### Keyword suggestions for the Zomato Email Scraper

The shipped defaults — `restaurant` and `cafe` — are broad starting points. Local format and cuisine words match far more of the index.

| Keyword | Why it works on Zomato |
|---|---|
| `dhaba` | The Indian roadside diner format, densely listed |
| `biryani` | One of the highest-volume cuisine terms in the index |
| `thali` | Everyday dining pages across tier-1 and tier-2 cities |
| `tiffin` | Meal-subscription and home-kitchen businesses |
| `cloud kitchen` | Delivery-only operators, a fast-growing segment |
| `bakery` | Bakeries and dessert shops with catering inboxes |
| `sweet shop` | Mithai businesses that publish bulk-order addresses |
| `shawarma` | A high-density UAE term when `countryCode` is `AE` |

Pair a cuisine or format noun with an intent modifier — `biryani catering`, `cloud kitchen owner` — instead of searching a bare noun.

#### Email domains worth testing for the Zomato Email Scraper

The default `customDomains` are `@gmail.com` and `@yahoo.com`.
Gmail dominates Indian small-business contact details and should stay. The rest are suggestions based on how these markets publish addresses, not guarantees of volume.

| Domain | Why add it |
|---|---|
| `@gmail.com` | Keep — the default business inbox across India and the UAE |
| `@rediffmail.com` | Long-established Indian provider, common on older listings |
| `@yahoo.co.in` | The Indian Yahoo address |
| `@hotmail.com` | Widely used by older UAE and Indian businesses |
| `@outlook.com` | Increasingly common for newer restaurant groups |

Each extra domain multiplies the query count, because the Zomato Email Scraper searches every keyword against every domain.
Three or four domains per run is a good balance.

### Zomato Email Scraper features

Everything listed below is implemented in the Zomato Email Scraper today.

| Feature | What it means in practice |
|---|---|
| Query expansion | Base, quoted, `intitle:` and one variant per modifier; base queries run first |
| Global deduplication | An email found by several queries is stored exactly once |
| Email normalisation | Understands `name [at] domain [dot] com`, `name (at) domain`, `name @ domain`, `domain .com`, zero-width characters and the full-width `＠` |
| Junk filter | Rejects placeholders such as `email@`, `yourname@`, `test@`, `xxx@` and single-character locals |
| Boundary-correct matching | `@gmail.com` will not match inside `@gmail.company` or `@gmail.com.br` |
| Soft-wrap repair | Drops a hit that is only the tail of another email in the same block |
| Structural parsing | Independent of Google's obfuscated CSS class names |
| Whole-page fallback | A markup change degrades to "emails without account details" rather than "no emails" |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried, not counted as empty |
| Retries | Up to 3 attempts per page with exponential backoff and a fresh proxy session per request |
| Failed-query requeue | Blocked or failed queries are re-queued once at the end of the run |
| Concurrency | An `asyncio` worker pool with a shared stop signal on `maxEmails` |
| Resumable state | Key-value store state keyed by an input hash; saves on `PERSIST_STATE`, `MIGRATING` and `ABORTING` |
| Run summary | Logs pages fetched, blocked pages, retries and emails per page |

### Zomato Email Scraper input fields

These are the exact input fields the Zomato Email Scraper accepts, with the defaults it ships with.

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["restaurant","cafe"]` | Search terms describing the venues you want |
| `location` | string | `""` | Optional location phrase added to every query |
| `customDomains` | array | `["@gmail.com","@yahoo.com"]` | Only emails on these domains are kept; `@` optional |
| `maxEmails` | integer 1-10000 | `20` | Stop after this many unique emails |
| `countryCode` | string | `""` | Two-letter country for the search proxy — use `IN` or `AE` |
| `expandQueries` | boolean | `true` | Search each keyword x domain in several phrasings |
| `queryModifiers` | array | `["email","contact","catering","reservations","owner"]` | Extra words combined with each keyword when expansion is on |
| `maxPagesPerQuery` | integer 1-50 | `30` | Page cap per query |
| `maxConcurrency` | integer 1-20 | `5` | Parallel queries |

#### Example Zomato Email Scraper input

```json
{
  "keywords": ["biryani", "cloud kitchen", "bakery"],
  "location": "Bengaluru",
  "customDomains": ["@gmail.com", "@rediffmail.com", "@yahoo.co.in"],
  "maxEmails": 300,
  "countryCode": "IN",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "catering", "bulk order", "owner"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

#### City-level prospecting with `location`

`location` is the most valuable field in the Zomato Email Scraper for anyone with a territory, because restaurants are an inherently local sale.
It appends a quoted phrase to every query, so you can build one dataset per city instead of one undifferentiated national list.

Useful values on this platform include `Bengaluru`, `Mumbai`, `Delhi NCR`, `Hyderabad`, `Pune`, `Chennai`, `Dubai`, `Abu Dhabi` — and, for tighter targeting, area names such as `Koramangala`, `Bandra` or `Al Barsha`.
Run one city per job, tag the dataset, and hand each rep a list they can actually route.

Leave `location` empty for a first exploratory run, then narrow.
On an identity-thin platform, city segmentation is often the only geographic signal you get, so it is worth capturing at query time.

### Zomato Email Scraper output fields

Every dataset item the Zomato Email Scraper writes carries all fourteen of these fields.

| Field | Meaning |
|---|---|
| `network` | Platform name |
| `keyword` | The keyword that produced the lead |
| `query` | The exact Google query used |
| `title` | Raw result title |
| `accountName` | Account label Google prints |
| `fullName` | Display name parsed from a profile-style title; empty for post captions |
| `username` | URL-safe handle when the platform exposes one; otherwise `null` |
| `profileUrl` | Canonical account URL when a handle is known; otherwise empty |
| `url` | Direct platform link when exposed, else the profile URL |
| `description` | Bio or snippet text, cleaned of labels and engagement counters |
| `email` | Lower-cased email address |
| `emailDomain` | The matched domain |
| `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email |
| `foundAt` | ISO 8601 UTC timestamp |

#### Example Zomato Email Scraper output

```json
[
  {
    "network": "Zomato",
    "keyword": "biryani",
    "query": "site:zomato.com biryani \"@gmail.com\" catering \"Bengaluru\"",
    "title": "Meghana Foods Menu - Koramangala, Bengaluru | Zomato",
    "accountName": "Zomato",
    "fullName": "Meghana Foods Menu - Koramangala, Bengaluru",
    "username": "bangalore",
    "profileUrl": "https://www.zomato.com/bangalore",
    "url": "https://www.zomato.com/bangalore",
    "description": "Biryani, Andhra. Bulk and catering orders: meghana.catering@gmail.com",
    "email": "meghana.catering@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T10:02:18Z"
  },
  {
    "network": "Zomato",
    "keyword": "cloud kitchen",
    "query": "site:zomato.com cloud kitchen \"@rediffmail.com\" owner \"Bengaluru\"",
    "title": "Reviews - Spice Route Cloud Kitchen | Zomato",
    "accountName": "",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "",
    "description": "Ordered twice this month. Owner responds fast on spiceroute.blr@rediffmail.com",
    "email": "spiceroute.blr@rediffmail.com",
    "emailDomain": "@rediffmail.com",
    "possiblyTruncated": true,
    "foundAt": "2026-08-31T10:04:51Z"
  },
  {
    "network": "Zomato",
    "keyword": "bakery",
    "query": "site:zomato.com bakery \"@gmail.com\" contact \"Bengaluru\"",
    "title": "Order Online - Sunrise Bakery, Indiranagar | Zomato",
    "accountName": "",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "",
    "description": "Cakes and bakes. Wholesale enquiries sunrisebakery.blr@gmail.com",
    "email": "sunrisebakery.blr@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T10:05:37Z"
  }
]
```

Two of the three rows above have `username: null` and an empty `profileUrl`, which is representative.
That is the yield note in practice: Zomato indexes review and menu pages more than restaurant profiles, so many rows carry an email without a restaurant handle.

Note the first row's `profileUrl` shape too. Where Zomato does expose a resolvable path, the handle Google prints in its breadcrumb is usually the city segment, so the canonical link the Zomato Email Scraper can build is `https://www.zomato.com/{city}` rather than a per-venue page.

#### What a measured Zomato Email Scraper run looked like

Per roughly 10 parsed results in a live test: 2 rows with a usable identity, 2 resolvable profile URLs, 8 unique emails.
Email density is high; account context is thin.

Plan your enrichment around that shape.
Match on `email` rather than `accountName`, and use `keyword`, `query` and `location` as your segmentation signals instead.

### Restaurant lead generation use cases for the Zomato Email Scraper

Here is where the Zomato Email Scraper fits into real B2B prospecting and market research workflows.

| Use case | How to configure it |
|---|---|
| POS and payments sales in India | `keywords: ["restaurant","cloud kitchen"]`, `countryCode: "IN"`, city in `location` |
| Food distribution and wholesale | `keywords: ["biryani","thali","bakery"]` with a `bulk order` modifier |
| Packaging and disposables suppliers | Target `cloud kitchen` and `tiffin`, the most delivery-intensive formats |
| Catering and events sourcing | Lean on the `catering` modifier; restaurants publish these inboxes deliberately |
| Restaurant equipment sales | `keywords: ["dhaba","sweet shop"]` for owner-operated venues |
| UAE market entry | `countryCode: "AE"`, `location: "Dubai"`, `keywords: ["shawarma","restaurant"]` |
| Hospitality recruitment | Use the `owner` modifier to reach decision-maker inboxes |
| Local agency client acquisition | One city per run; pitch delivery-menu, photography or SEO work |
| CRM enrichment | Match your existing venue list on `email` and backfill missing addresses |
| Keyword research | Analyse `keyword` and `query` to see which phrasings surface public contacts |

### Practical Zomato Email Scraper recipes

**India baseline.** Local cuisine keywords, `countryCode: "IN"`, one city in `location`, `maxEmails: 300`.
This is the configuration most likely to return a large dataset.

**Email-first workflow.** Because identity coverage is thin, treat the dataset as an address list with metadata, not a venue directory.
Deduplicate on `email`, then enrich names separately.

**Domain sweep.** Run `@gmail.com`, `@rediffmail.com` and `@yahoo.co.in` as three separate jobs.
Per-domain visibility tells you where a market actually publishes contact details.

**Widen before you deepen.** More cuisine keywords and modifiers beat more pages per query, because Google caps a single query at roughly 300 results.
Raise `maxPagesPerQuery` last.

**Pair for coverage.** Run the [Uber Eats Email Scraper](https://apify.com/leads-scraper/uber-eats-email-scraper) and [Tripadvisor Restaurants Email Scraper](https://apify.com/leads-scraper/tripadvisor-restaurants-email-scraper) beside this one to cover the same cities from platforms with different indexing behaviour.

### Responsible use, GDPR and CAN-SPAM

An email that identifies a natural person is personal data even when it was published publicly.
Public availability is not consent to send. If you contact EU residents the GDPR applies; commercial email into the United States falls under CAN-SPAM; India's DPDP Act and the UAE's data protection law cover the markets this Actor targets.

Practical steps that keep a Zomato Email Scraper workflow defensible:

- Prefer role addresses (`info@`, `catering@`, `orders@`) over addresses naming an individual.
- Keep provenance for every lead — the `query`, `url` and `foundAt` fields exist for exactly this.
- Give a clear sender identity, a stated purpose and a working opt-out in every message.
- Honour opt-outs immediately and check suppression lists before each follow-up.
- Be careful with review-page rows: the address may belong to a reviewer rather than the venue, so read `description` before sending.
- Delete data you are not actively using rather than warehousing scraped lists.

This is operational guidance, not legal advice.

### Related Actors

The Zomato Email Scraper is one of 35 Actors in a Travel, Hospitality and Food family that all share this engine.
For stronger venue identity, the **OpenRice Email Scraper** and [Resy Email Scraper](https://apify.com/leads-scraper/resy-email-scraper) resolve profile URLs far more often; for the same restaurant motion in the West, use the [OpenTable Email Scraper](https://apify.com/neuro-scraper/opentable-email-scraper).

| Actor | What it collects |
|---|---|
| [Zomato Email and Phone Number Scraper](https://apify.com/leads-scraper/zomato-email-and-phone-number-scraper) | Emails and phone numbers from Zomato |
| [Zomato Phone Number Scraper](https://apify.com/leads-scraper/zomato-phone-number-scraper) | Public phone numbers from Zomato |
| [Airbnb Email Scraper](https://apify.com/leads-scraper/airbnb-email-scraper) | Public contact emails from Airbnb |
| [Booking.com Email Scraper](https://apify.com/leads-scraper/booking-com-email-scraper) | Public contact emails from Booking.com |
| [Caviar Email Scraper](https://apify.com/neuro-scraper/caviar-email-scraper) | Public contact emails from Caviar |
| [ChowNow Email Scraper](https://apify.com/neuro-scraper/chownow-email-scraper) | Public contact emails from ChowNow |
| [Contiki Email Scraper](https://apify.com/neuro-scraper/contiki-email-scraper) | Public contact emails from Contiki |
| [Craigslist Email Scraper](https://apify.com/leads-scraper/craigslist-email-scraper) | Public contact emails from Craigslist |
| [Delivery.com Email Scraper](https://apify.com/neuro-scraper/delivery-com-email-scraper) | Public contact emails from Delivery.com |
| [DoorDash Email Scraper](https://apify.com/leads-scraper/doordash-email-scraper) | Public contact emails from DoorDash |
| [EatStreet Email Scraper](https://apify.com/neuro-scraper/eatstreet-email-scraper) | Public contact emails from EatStreet |
| [G Adventures Email Scraper](https://apify.com/neuro-scraper/g-adventures-email-scraper) | Public contact emails from G Adventures |
| [GetYourGuide Email Scraper](https://apify.com/leads-scraper/getyourguide-email-scraper) | Public contact emails from GetYourGuide |
| [Grubhub Email Scraper](https://apify.com/leads-scraper/grubhub-email-scraper) | Public contact emails from Grubhub |
| [Hostelbookers Email Scraper](https://apify.com/leads-scraper/hostelbookers-email-scraper) | Public contact emails from Hostelworld |
| [HotelsCombined Email Scraper](https://apify.com/neuro-scraper/hotelscombined-email-scraper) | Public contact emails from HotelsCombined |
| [Intrepid Travel Email Scraper](https://apify.com/neuro-scraper/intrepid-travel-email-scraper) | Public contact emails from Intrepid Travel |
| [Just Eat Email Scraper](https://apify.com/leads-scraper/just-eat-email-scraper) | Public contact emails from Just Eat |
| [Klook Email Scraper](https://apify.com/neuro-scraper/klook-email-scraper) | Public contact emails from Klook |
| [OpenTable Email Scraper](https://apify.com/neuro-scraper/opentable-email-scraper) | Public contact emails from OpenTable |
| [Resy Email Scraper](https://apify.com/leads-scraper/resy-email-scraper) | Public contact emails from Resy |
| [TheFork Email Scraper](https://apify.com/leads-scraper/thefork-email-scraper) | Public contact emails from TheFork |
| [Toast Restaurant Email Scraper](https://apify.com/leads-scraper/toast-restaurant-email-scraper) | Public contact emails from Toast |
| [TourRadar Email Scraper](https://apify.com/leads-scraper/tourradar-email-scraper) | Public contact emails from TourRadar |
| [Traveloka Email Scraper](https://apify.com/leads-scraper/traveloka-email-scraper) | Public contact emails from Traveloka |
| [Tripadvisor Attractions Email Scraper](https://apify.com/leads-scraper/tripadvisor-attractions-email-scraper) | Public contact emails from Tripadvisor |
| [Tripadvisor Hotels Email Scraper](https://apify.com/leads-scraper/tripadvisor-hotels-email-scraper) | Public contact emails from Tripadvisor |
| [Tripadvisor Restaurants Email Scraper](https://apify.com/leads-scraper/tripadvisor-restaurants-email-scraper) | Public contact emails from Tripadvisor |
| [Uber Eats Email Scraper](https://apify.com/leads-scraper/uber-eats-email-scraper) | Public contact emails from Uber Eats |
| [Viator Email Scraper](https://apify.com/leads-scraper/viator-email-scraper) | Public contact emails from Viator |
| [Wanderlog Email Scraper](https://apify.com/leads-scraper/wanderlog-email-scraper) | Public contact emails from Wanderlog |
| [Wego Email Scraper](https://apify.com/leads-scraper/wego-email-scraper) | Public contact emails from Wego |
| [Airbnb Email and Phone Number Scraper](https://apify.com/leads-scraper/airbnb-email-and-phone-number-scraper) | Emails and phone numbers from Airbnb |
| [Booking.com Email and Phone Number Scraper](https://apify.com/leads-scraper/booking-com-email-and-phone-number-scraper) | Emails and phone numbers from Booking.com |
| [Caviar Email and Phone Number Scraper](https://apify.com/neuro-scraper/caviar-email-and-phone-number-scraper) | Emails and phone numbers from Caviar |
| [ChowNow Email and Phone Number Scraper](https://apify.com/neuro-scraper/chownow-email-and-phone-number-scraper) | Emails and phone numbers from ChowNow |
| [Contiki Email and Phone Number Scraper](https://apify.com/neuro-scraper/contiki-email-and-phone-number-scraper) | Emails and phone numbers from Contiki |
| [Craigslist Email and Phone Number Scraper](https://apify.com/leads-scraper/craigslist-email-and-phone-number-scraper) | Emails and phone numbers from Craigslist |
| [Delivery.com Email and Phone Number Scraper](https://apify.com/neuro-scraper/delivery-com-email-and-phone-number-scraper) | Emails and phone numbers from Delivery.com |
| [DoorDash Email and Phone Number Scraper](https://apify.com/leads-scraper/doordash-email-and-phone-number-scraper) | Emails and phone numbers from DoorDash |
| [EatStreet Email and Phone Number Scraper](https://apify.com/neuro-scraper/eatstreet-email-and-phone-number-scraper) | Emails and phone numbers from EatStreet |
| [G Adventures Email and Phone Number Scraper](https://apify.com/neuro-scraper/g-adventures-email-and-phone-number-scraper) | Emails and phone numbers from G Adventures |

### Zomato Email Scraper limitations

Read these before planning anything around the output.

- **Zomato indexes review and menu pages more than restaurant profiles, so many rows carry an email without a restaurant handle.** This is the defining limitation, and it is why every recommendation above is email-first.
- **Weak account identity.** In a live test only about 2 of 10 parsed results carried a usable `accountName` or `fullName`. Expect emails with thin context.
- **Publicly indexed emails only.** The Zomato Email Scraper finds addresses already visible in Google's index. Anything behind a contact form or login is unreachable.
- **Google's ~300-result cap.** A single query returns roughly 300 results at most, which is why `expandQueries` defaults to `true`.
- **`possiblyTruncated`.** When `true`, Google's snippet ellipsis touched the email and it may be cut off. Verify before sending.
- **`username` and `profileUrl` are frequently empty.** Where populated, the handle is usually a city segment rather than a venue slug. That is a Google and platform limitation, not a bug.
- **Apify GOOGLE\_SERP proxy required.** The Zomato Email Scraper cannot run without Apify proxy credentials.
- **Free-plan cap.** Free Apify plans stop at 100 emails per run. Paid plans are uncapped.
- **No guaranteed volume.** Results vary with keywords, domains, location and Google's index on the day.
- **Not affiliated with Zomato.** This is an independent tool, not supported, endorsed by or connected to Zomato.

### Zomato Email Scraper FAQ

Common questions about the Zomato Email Scraper, its inputs and its output.

#### How many results should I expect from the Zomato Email Scraper?

In a live test, roughly 10 parsed results produced 8 unique emails but only 2 identified venues and 2 profile URLs. Expect good email density and thin account context. Total volume depends on your keywords, domains and `countryCode`, and no row count is guaranteed.

#### Why do so many rows have no restaurant name?

Because Zomato indexes review and menu pages more than restaurant profiles, so many rows carry an email without a restaurant handle. Google prints a page title rather than a venue label, and there is nothing for the Actor to resolve.

#### Does the Zomato Email Scraper log into Zomato?

No. It never logs in, never calls a Zomato API and never opens zomato.com in a browser. It reads Google results through the Apify GOOGLE\_SERP proxy.

#### What should I set `countryCode` to?

`IN` for India, `AE` for the UAE. Run them separately. Google personalises results by country, and a local vantage point is what surfaces Zomato pages properly.

#### Which keywords work best?

Local format and cuisine words: `biryani`, `dhaba`, `thali`, `tiffin`, `cloud kitchen`, `bakery`, `sweet shop`. Pair them with `catering`, `contact` or `owner` modifiers.

#### Which email domains should I add?

Keep `@gmail.com`, then test `@rediffmail.com`, `@yahoo.co.in` and `@outlook.com`. These are suggestions based on Indian and UAE market habits, not guarantees.

#### How do I use `location` for city-level prospecting?

Put a city or area name in it — `Bengaluru`, `Mumbai`, `Dubai`, `Koramangala` — and run one job per territory. On an identity-thin platform this is often your only reliable geographic segmentation.

#### Whose emails am I actually finding?

Mostly business inboxes published for catering, bulk orders and reservations, but review pages can also surface a reviewer's address. Read `description` before you send.

#### Does the Zomato Email Scraper verify deliverability?

No. It extracts and normalises what Google indexed. Check rows flagged `possiblyTruncated` before using them.

#### Can I resume an interrupted run?

Yes. State lives in the key-value store keyed by a hash of your input, with saves on Apify's `PERSIST_STATE`, `MIGRATING` and `ABORTING` events.

#### What happens when Google blocks a request?

Block, CAPTCHA and consent pages are detected rather than treated as empty. Pages get up to three attempts with exponential backoff, and failed queries are re-queued once at the end of the run.

#### Is scraping Zomato contact emails legal?

The Zomato Email Scraper only reads publicly indexed Google results. Whether you may then contact those addresses is a separate DPDP, GDPR and CAN-SPAM question. See the responsible use section and take your own legal advice.

### Leave a review

If the Zomato Email Scraper saved you time, please leave a star rating and a short review on
the Actor page.

Reviews are how other buyers judge whether a tool works, and they tell us which features to
build next.

If something did not work, email <neurodata.apify@gmail.com>
instead - bugs get fixed faster than they get complained about.

### Support

Questions, a bug, or you need a custom build of the Zomato Email Scraper? Contact **<neurodata.apify@gmail.com>**.

# Actor input Schema

## `keywords` (type: `array`):

Search terms describing the Zomato accounts you want (niche, job title, industry).

## `location` (type: `string`):

Optional location phrase added to every query (e.g. "New York").

## `customDomains` (type: `array`):

Only emails ending with one of these domains are collected. With or without the leading @. Each domain is searched separately, so more domains means more results but a longer run - remove some for a faster, narrower search, or add your own (e.g. @company.com).

## `maxEmails` (type: `integer`):

Stop once this many unique emails have been collected.

## `countryCode` (type: `string`):

Two-letter country code for the search proxy (e.g. US, GB, DE). Empty for any.

## `expandQueries` (type: `boolean`):

Search each keyword x domain pair with several phrasings. Recommended - Google caps a single query at ~300 results.

## `queryModifiers` (type: `array`):

Extra words combined with each keyword when Expand queries is on. Tuned for Zomato.

## `maxPagesPerQuery` (type: `integer`):

Google rarely returns more than ~30 pages for one query.

## `maxConcurrency` (type: `integer`):

How many queries run in parallel.

## Actor input object example

```json
{
  "keywords": [
    "restaurant",
    "cafe"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "catering",
    "reservations",
    "owner"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

## `results` (type: `string`):

Records produced by Zomato Email Scraper, stored in the run's default dataset.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "restaurant",
        "cafe"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "catering",
        "reservations",
        "owner"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leads-scraper/zomato-email-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": [
        "restaurant",
        "cafe",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "catering",
        "reservations",
        "owner",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("leads-scraper/zomato-email-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keywords": [
    "restaurant",
    "cafe"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "catering",
    "reservations",
    "owner"
  ]
}' |
apify call leads-scraper/zomato-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leads-scraper/zomato-email-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/ZY48ANpQ4iB367uUC/builds/mxLWhP2A8xU2JXmnj/openapi.json