# Zalando Email Scraper (`leads-scraper/zalando-email-scraper`) Actor

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

- **URL**: https://apify.com/leads-scraper/zalando-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

### Zalando Email Scraper

The Zalando Email Scraper collects publicly indexed contact emails connected to Zalando, Europe's largest online fashion platform.
It builds Google queries with the `site:` operator against `zalando.com`, `zalando.co.uk` and `zalando.de`, fetches them through the Apify GOOGLE\_SERP proxy, and extracts emails from the result blocks.
No login, no browser, no Zalando API — only what Google has already published in its index.

**Start with the honest part.** Zalando is a first-party retailer, so results are brand and campaign pages rather than third-party seller profiles.
It does run a Partner Program, but partner brands are surfaced as brand pages on Zalando's own domains, not as independent seller storefronts with public handles.

That shapes what the Zalando Email Scraper realistically finds: supplier, brand and press contact details published on Zalando's own pages.
It does not find marketplace-seller inboxes, because Zalando largely does not expose those as indexable pages.
If you need genuine third-party sellers, the [Allegro Email Scraper](https://apify.com/neuro-scraper/allegro-email-scraper) and [Cdiscount Email Scraper](https://apify.com/neuro-scraper/cdiscount-email-scraper) are structurally better suited.

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

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

### Language and `countryCode` in the Zalando Email Scraper

This is the most important configuration section in this document.
Zalando is a multi-market European platform, and the Zalando Email Scraper is pointed at three domains at once: `zalando.com`, `zalando.co.uk` and `zalando.de`.

That is why the shipped `keywords` are `brand` and `supplier` and the shipped `queryModifiers` are `email`, `contact`, `wholesale`, `customer service` and `inquiries`.
English works on `zalando.com` and `zalando.co.uk`. It does **not** work well on `zalando.de`, which is Zalando's largest and most deeply indexed market.

#### Running the Zalando Email Scraper against the German market

Set `countryCode` to `DE` and switch the keywords to German. This is the highest-leverage change you can make.
`zalando.de` carries far more indexed pages than the `.com` and `.co.uk` domains combined, and German-country search is what surfaces them.

Useful German keywords: `marke` (brand), `lieferant` (supplier), `haendler` (retailer), `hersteller` (manufacturer), `partner`, `presse`.
Useful German modifiers: `kontakt`, `grosshandel`, `kundenservice`, `vertrieb`, `einkauf`.

For the UK market instead, set `countryCode` to `GB` and keep the English defaults.
Run the two configurations as separate runs rather than mixing languages in one — the `query` field then tells you cleanly which market produced each lead.

#### German free-mail domains for `customDomains`

The default `customDomains` are `@gmail.com` and `@yahoo.com`.
Keep Gmail. Yahoo is comparatively rare in Germany and is usually worth replacing when you target `zalando.de`.

These providers are worth testing. They are suggestions based on how the German and wider European market publishes contact details, not guarantees of volume:

| Domain | Why add it for Zalando |
|---|---|
| `@web.de` | One of the two dominant German free-mail providers |
| `@gmx.de` | The other dominant German provider, common with SMEs and small labels |
| `@gmx.net` | The `.net` variant of the same service |
| `@t-online.de` | Telekom mail, long-established with older German businesses |
| `@gmail.com` | Keep — the most common domain across every European market |

Each extra domain multiplies query count, because the Zalando Email Scraper searches every keyword against every domain.
Given the low expected yield here, prefer a tight, well-chosen domain set over a broad sweep.

### Zalando Email Scraper features

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

| Feature | What it means in practice |
|---|---|
| Multi-domain targeting | Queries run against `zalando.com`, `zalando.co.uk` and `zalando.de` |
| 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] de`, `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 | Finds the `<h3>` and the smallest surrounding block, so it does not depend on Google's CSS class names |
| Whole-page fallback | If Google's markup changes, the run 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 |

### How the Zalando Email Scraper works

The Zalando 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 against Zalando's domains, for example `site:zalando.de marke "@web.de" kontakt`.
3. It fetches result pages through the Apify GOOGLE\_SERP proxy using async `aiohttp` requests.
4. It parses each result block structurally 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 Zalando Email Scraper never signs into Zalando and never requests pages from Zalando's own servers.
Everything it returns was already public in Google's search index.

### Zalando Email Scraper input fields

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

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["brand","supplier"]` | Search terms describing the accounts 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 — set `DE` or `GB` here |
| `expandQueries` | boolean | `true` | Search each keyword x domain in several phrasings |
| `queryModifiers` | array | `["email","contact","wholesale","customer service","inquiries"]` | 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 Zalando Email Scraper input

```json
{
  "keywords": ["marke", "lieferant", "hersteller"],
  "location": "Berlin",
  "customDomains": ["@web.de", "@gmx.de", "@gmail.com"],
  "maxEmails": 100,
  "countryCode": "DE",
  "expandQueries": true,
  "queryModifiers": ["email", "kontakt", "grosshandel", "kundenservice", "vertrieb"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

The `location` field appends a phrase to every query.
European fashion hubs work well as values — `Berlin`, `Hamburg`, `Amsterdam`, `Paris`, `Milano`.
On a low-yield platform, location narrows an already narrow result set, so use it sparingly.

### Zalando Email Scraper output fields

Every dataset item the Zalando 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 Zalando Email Scraper output

```json
[
  {
    "network": "Zalando",
    "keyword": "marke",
    "query": "site:zalando.de marke \"@web.de\" kontakt",
    "title": "NordLabel - Marke bei Zalando",
    "accountName": "NordLabel",
    "fullName": "NordLabel",
    "username": "nordlabel",
    "profileUrl": "https://www.zalando.co.uk/nordlabel/",
    "url": "https://www.zalando.co.uk/nordlabel/",
    "description": "Skandinavische Mode. Presse und Vertrieb: presse.nordlabel@web.de",
    "email": "presse.nordlabel@web.de",
    "emailDomain": "@web.de",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T12:04:18Z"
  },
  {
    "network": "Zalando",
    "keyword": "lieferant",
    "query": "site:zalando.de lieferant \"@gmx.de\" grosshandel",
    "title": "Lieferanteninformationen und Kampagnen - Zalando",
    "accountName": "Zalando Lieferanteninfo",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "",
    "description": "Anfragen von Lieferanten: einkauf.beispiellabel@gmx.de",
    "email": "einkauf.beispiellabel@gmx.de",
    "emailDomain": "@gmx.de",
    "possiblyTruncated": true,
    "foundAt": "2026-08-31T12:05:44Z"
  }
]
```

The second row is the more common shape here.
`username` is `null` and `profileUrl` is empty because Google printed a campaign or information page title rather than a brand slug, so no `https://www.zalando.co.uk/.../` URL can be built.
The email and account label remain usable.

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

A live test run returned **3 result blocks**.
That is a small number, and it is consistent with the platform's structure rather than a parsing failure.

Zalando is a first-party retailer, so results are brand and campaign pages rather than third-party seller profiles, and those pages rarely publish free-mail contact addresses.
Treat the Zalando Email Scraper as a supplementary enrichment source for a European fashion list, not as a primary lead engine.

### Use cases for the Zalando Email Scraper

Here is where the Zalando Email Scraper fits into real prospecting and research workflows.

| Use case | How to configure it |
|---|---|
| European fashion brand discovery | `keywords: ["marke","hersteller"]`, `countryCode: "DE"`, `customDomains: ["@web.de","@gmx.de"]` |
| Supplier and wholesale research | Use `lieferant` with the `grosshandel` and `vertrieb` modifiers |
| Press and PR outreach | Add `presse` and `partner` as keywords |
| Filling gaps in an existing brand list | Match `accountName` to labels you already track and add missing emails |
| UK market pass | Keep English defaults and set `countryCode: "GB"` |
| Market research | Analyse `query` and `keyword` to see which phrasings surface public contacts |
| Cross-market enrichment | Run beside the Otto, Allegro and Cdiscount Actors for a wider European picture |
| Data-quality benchmarking | Compare yield here against a true marketplace to calibrate expectations |

### Practical Zalando Email Scraper recipes

**German baseline.** German keywords, German modifiers, `countryCode: "DE"`, `maxEmails: 50`.
This is the configuration most likely to return anything at all.

**UK comparison run.** English defaults, `countryCode: "GB"`, same `maxEmails`.
Comparing the two runs tells you where Zalando's indexable contact data actually lives for your niche.

**Brand-first framing.** Drop seller-flavoured terms entirely; use `marke`, `hersteller`, `lieferant` and `presse`.
This matches how Zalando's own pages are written and is the more productive angle.

**Widen before you deepen.** On a low-yield platform, more keyword variants beat more pages per query.
Raise `maxPagesPerQuery` last, after you know a keyword returns Zalando pages at all.

### Responsible use and GDPR

Zalando's core markets are in the EU, so the GDPR applies to anything you collect through the Zalando Email Scraper.
An address that identifies a natural person — a named press contact, a sole trader — is personal data even when it was published on a public page.

Public availability is not consent to send. Establish a lawful basis before your first message.
Germany in particular applies the UWG to unsolicited commercial email, and it is stricter than several other EU markets.

Practical steps that keep a Zalando Email Scraper workflow defensible:

- Strongly prefer role addresses (`presse@`, `kontakt@`, `vertrieb@`) 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.
- Delete data you are not actively using rather than warehousing scraped lists.
- Take local legal advice before running cold outreach at scale in Germany.

This is operational guidance, not legal advice.

### Related Actors

The Zalando Email Scraper belongs to an E-commerce and Marketplaces family that all share this engine.
Its closest structural sibling is the [Otto Email Scraper](https://apify.com/leads-scraper/otto-email-scraper) — also a German first-party retailer with the same brand-page caveat.
For genuine third-party European sellers, use the [Allegro Email Scraper](https://apify.com/neuro-scraper/allegro-email-scraper) or [Cdiscount Email Scraper](https://apify.com/neuro-scraper/cdiscount-email-scraper); for secondhand European fashion specifically, the [Vinted Email Scraper](https://apify.com/leads-scraper/vinted-email-scraper) usually yields far more, and independent fashion labels are often reachable via the [Shopify Store Email Scraper](https://apify.com/leads-scraper/shopify-store-email-scraper).

| Actor | What it collects |
|---|---|
| [Zalando Email and Phone Number Scraper](https://apify.com/leads-scraper/zalando-email-and-phone-number-scraper) | Emails and phone numbers from Zalando |
| [Zalando Phone Number Scraper](https://apify.com/leads-scraper/zalando-phone-number-scraper) | Public phone numbers from Zalando |
| [AliExpress Email Scraper](https://apify.com/neuro-scraper/aliexpress-email-scraper) | Public contact emails from AliExpress |
| [Allegro Email Scraper](https://apify.com/neuro-scraper/allegro-email-scraper) | Public contact emails from Allegro |
| [Amazon Email Scraper](https://apify.com/leads-scraper/amazon-email-scraper) | Public contact emails from Amazon |
| [Best Buy Seller Email Scraper](https://apify.com/leads-scraper/best-buy-seller-email-scraper) | Public contact emails from Best Buy |
| [BigCommerce Store Email Scraper](https://apify.com/neuro-scraper/bigcommerce-store-email-scraper) | Public contact emails from BigCommerce Store |
| [Cdiscount Email Scraper](https://apify.com/neuro-scraper/cdiscount-email-scraper) | Public contact emails from Cdiscount |
| [Coupang Email Scraper](https://apify.com/neuro-scraper/coupang-email-scraper) | Public contact emails from Coupang |
| [Depop Email Scraper](https://apify.com/leads-scraper/depop-email-scraper) | Public contact emails from Depop |
| [DHgate Email Scraper](https://apify.com/neuro-scraper/dhgate-email-scraper) | Public contact emails from DHgate |
| [eBay Email Scraper](https://apify.com/leads-scraper/ebay-email-scraper) | Public contact emails from eBay |
| [Ecwid Store Email Scraper](https://apify.com/neuro-scraper/ecwid-store-email-scraper) | Public contact emails from Ecwid Store |
| [Etsy Email Scraper](https://apify.com/leads-scraper/etsy-email-scraper) | Public contact emails from Etsy |
| [Faire Email Scraper](https://apify.com/leads-scraper/faire-email-scraper) | Public contact emails from Faire |
| [Flipkart Email Scraper](https://apify.com/leads-scraper/flipkart-email-scraper) | Public contact emails from Flipkart |
| [Home Depot Seller Email Scraper](https://apify.com/leads-scraper/home-depot-seller-email-scraper) | Public contact emails from Home Depot |
| [JD.com Email Scraper](https://apify.com/leads-scraper/jd-com-email-scraper) | Public contact emails from JD.com |
| [Lazada Email Scraper](https://apify.com/neuro-scraper/lazada-email-scraper) | Public contact emails from Lazada |
| [Lowe's Seller Email Scraper](https://apify.com/leads-scraper/lowes-seller-email-scraper) | Public contact emails from Lowe's |
| [MercadoLibre Email Scraper](https://apify.com/neuro-scraper/mercadolibre-email-scraper) | Public contact emails from MercadoLibre |
| [Mercari Email Scraper](https://apify.com/neuro-scraper/mercari-email-scraper) | Public contact emails from Mercari |
| [Newegg Email Scraper](https://apify.com/leads-scraper/newegg-email-scraper) | Public contact emails from Newegg |
| [Otto Email Scraper](https://apify.com/leads-scraper/otto-email-scraper) | Public contact emails from Otto |
| [Overstock Email Scraper](https://apify.com/leads-scraper/overstock-email-scraper) | Public contact emails from Overstock |
| [Poshmark Email Scraper](https://apify.com/leads-scraper/poshmark-email-scraper) | Public contact emails from Poshmark |
| [Rakuten Email Scraper](https://apify.com/neuro-scraper/rakuten-email-scraper) | Public contact emails from Rakuten |
| [Shopee Email Scraper](https://apify.com/leads-scraper/shopee-email-scraper) | Public contact emails from Shopee |
| [Shopify Store Email Scraper](https://apify.com/leads-scraper/shopify-store-email-scraper) | Public contact emails from Shopify Store |
| [Taobao Email Scraper](https://apify.com/leads-scraper/taobao-email-scraper) | Public contact emails from Taobao |
| [Target Seller Email Scraper](https://apify.com/neuro-scraper/target-seller-email-scraper) | Public contact emails from Target |
| [Temu Email Scraper](https://apify.com/leads-scraper/temu-email-scraper) | Public contact emails from Temu |
| [Tmall Email Scraper](https://apify.com/leads-scraper/tmall-email-scraper) | Public contact emails from Tmall |
| [Vinted Email Scraper](https://apify.com/leads-scraper/vinted-email-scraper) | Public contact emails from Vinted |
| [Walmart Email Scraper](https://apify.com/leads-scraper/walmart-email-scraper) | Public contact emails from Walmart |
| [Wayfair Email Scraper](https://apify.com/neuro-scraper/wayfair-email-scraper) | Public contact emails from Wayfair |
| [Wish Email Scraper](https://apify.com/leads-scraper/wish-email-scraper) | Public contact emails from Wish |
| [Wix Stores Email Scraper](https://apify.com/leads-scraper/wix-stores-email-scraper) | Public contact emails from Wix Stores |
| [WooCommerce Email Scraper](https://apify.com/neuro-scraper/woocommerce-email-scraper) | Public contact emails from WooCommerce |
| [AliExpress Email and Phone Number Scraper](https://apify.com/neuro-scraper/aliexpress-email-and-phone-number-scraper) | Emails and phone numbers from AliExpress |
| [Allegro Email and Phone Number Scraper](https://apify.com/neuro-scraper/allegro-email-and-phone-number-scraper) | Emails and phone numbers from Allegro |
| [Amazon Email and Phone Number Scraper](https://apify.com/leads-scraper/amazon-email-and-phone-number-scraper) | Emails and phone numbers from Amazon |

### Zalando Email Scraper limitations

Read these before planning anything around the output.

- **Zalando is a first-party retailer, so results are brand and campaign pages rather than third-party seller profiles.** This is the defining limitation of the Zalando Email Scraper.
- **Low measured yield.** A live test run returned 3 result blocks. Expect a supplementary trickle, not a lead firehose.
- **Publicly indexed emails only.** The Zalando Email Scraper finds addresses already visible in Google's index. Nothing behind a login or an internal partner portal is reachable.
- **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.** Google often prints a campaign or category title with no brand slug, so no canonical `https://www.zalando.co.uk/.../` URL can be built. That is a Google limitation, not a bug.
- **Apify GOOGLE\_SERP proxy required.** The Zalando 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 Zalando.** This is an independent tool, not supported, endorsed by or connected to Zalando.

### Zalando Email Scraper FAQ

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

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

Few. A live test run returned 3 result blocks. Zalando is a first-party retailer, so results are brand and campaign pages rather than third-party seller profiles, and those pages seldom publish free-mail addresses. Plan for a supplementary source.

#### Why is the yield lower than on Allegro or Cdiscount?

Those are genuine third-party marketplaces with many indexed seller pages. Zalando sells largely its own and partner-brand stock through its own pages, so there are far fewer independent seller pages to index.

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

No. It never logs in, never calls a Zalando API and never opens zalando.de in a browser. It reads Google results through the Apify GOOGLE\_SERP proxy.

#### Why are the default keywords English when Zalando is a German company?

Because the Zalando Email Scraper targets `zalando.com` and `zalando.co.uk` as well as `zalando.de`. For the German market — which is the deepest index — switch to German keywords and set `countryCode` to `DE`.

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

`DE` for the German market, `GB` for the UK. Google personalises results by country, and an unset `countryCode` will usually underperform both.

#### Which email domains work best for Zalando?

For the German market start with `@web.de`, `@gmx.de` and `@gmail.com`; `@gmx.net` and `@t-online.de` are worth testing. These are suggestions based on market habits, not guarantees.

#### Whose emails am I actually finding?

Mostly supplier, brand and press contacts published on Zalando's own pages — not marketplace-seller inboxes. Set expectations accordingly.

#### Why is `username` empty on so many rows?

Google frequently prints a campaign or informational title rather than a brand slug. Without a slug there is no canonical profile URL to build. `accountName` and `email` are still populated.

#### Does the Zalando 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 Zalando contact emails legal?

The Zalando Email Scraper only reads publicly indexed Google results. Whether you may contact those addresses is a separate GDPR and UWG question — see the responsible use section and take your own legal advice.

### Leave a review

If the Zalando 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 Zalando Email Scraper? Contact **<neurodata.apify@gmail.com>**.

# Actor input Schema

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

Search terms describing the Zalando 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 Zalando.

## `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": [
    "brand",
    "supplier"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "wholesale",
    "customer service",
    "inquiries"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

Records produced by Zalando 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": [
        "brand",
        "supplier"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "wholesale",
        "customer service",
        "inquiries"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leads-scraper/zalando-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": [
        "brand",
        "supplier",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "wholesale",
        "customer service",
        "inquiries",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("leads-scraper/zalando-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": [
    "brand",
    "supplier"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "wholesale",
    "customer service",
    "inquiries"
  ]
}' |
apify call leads-scraper/zalando-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leads-scraper/zalando-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/yraTqy2avAMmgYRIc/builds/nrOdYYUUBBYLZhgvB/openapi.json