# Trendyol Email Scraper (`solid-scraper/trendyol-email-scraper`) Actor

📧 Trendyol Email Scraper extracts accurate business emails from Trendyol listings fast. Perfect for lead gen, sales outreach, and marketing—save time, reach targeted prospects, and boost conversions. 🚀

- **URL**: https://apify.com/solid-scraper/trendyol-email-scraper.md
- **Developed by:** [SolidScraper](https://apify.com/solid-scraper) (community)
- **Categories:** Lead generation, Automation, E-commerce
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### Trendyol Email Scraper 📬

**Trendyol Email Scraper** is an Apify actor that scrapes email addresses from **publicly available sources** on the Trendyol platform using your provided keywords. If you’re looking for a **Trendyol email scraper** for lead generation or prospecting, a **Trendyol customer email extractor**, or a **Trendyol seller email scraper**, this tool helps you find relevant contacts faster—whether you’re a marketer, researcher, or data analyst. It’s built to turn keyword ideas into usable contact data at scale, saving you hours of manual work.

***

### Why choose Trendyol Email Scraper?

| Feature | Benefit |
| --- | --- |
| ✅ **Keyword + domain filtering** | Helps you focus on the exact **Trendyol leads email scraping** results you need using your keyword list and `customDomains`. |
| ✅ **Structured JSON output** | Produces consistent records (`keyword`, `title`, `description`, `url`, `email`) ready for **Trendyol email list** building. |
| ✅ **Reliability with fallback behavior** | Improves coverage by switching to a special proxy when no emails are found for a run. |
| ✅ **Deduplication across runs** | Avoids repeating email addresses in the output using a `seen_emails` set. |
| ✅ **Built-in proxy support** | Works with your `proxyConfiguration` and can still proceed when proxy options change. |
| ✅ **Made for bulk email scraping tool workflows** | Designed to loop through every combination of `keywords` × `customDomains` for high-volume collection. |

***

### Key features

- 🔍 **Trendyol keyword-driven email harvesting**: Uses your `keywords` input to discover relevant email addresses associated with those terms.
- 🧩 **Custom email domain targeting**: Filters extracted contacts by the domains you provide in **Custom Email Domains** (example default is `@gmail.com`).
- 🛡️ **Proxy resilience & switching**: Supports your selected proxy configuration and includes a fallback path when no emails are found.
- 🔄 **Fallback when results are empty**: If a run yields no emails, the actor attempts a fallback run to improve the chances of finding matches.
- 📄 **Clean, consistent dataset records**: Every saved item includes `keyword`, `title`, `description`, `url`, and `email`, making it easier to import into downstream systems.
- 💾 **Export-ready output**: All collected results are pushed to Apify datasets via `await Actor.push_data(results)`, so you can export as JSON/CSV from the UI.
- 🌐 **Location-aware filtering (optional)**: If you set `location`, it’s included as an extra filter to narrow results.
- 🧠 **Duplicate protection**: Prevents repeated emails by tracking already-seen addresses during the run.

***

### Input

Provide input via an `input.json` file. Example structure:

```json
{
  "keywords": ["john", "marketing"],
  "location": "",
  "platform": "Trendyol",
  "customDomains": ["@gmail.com"],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

#### Input Fields

| Key | Type | Description |
| --- | --- | --- |
| `keywords` | array | **Required.** A list of keywords to search for (the actor iterates through each keyword). |
| `location` | string | Optional location filter. If provided, it’s added to the search context; leave empty to skip location filtering. |
| `platform` | string | Platform selector. The actor supports the enum value **`Trendyol`** (default is `Trendyol`). |
| `customDomains` | array | A list of email domains to keep. The actor matches extracted emails against these domains (default is `["@gmail.com"]`). |
| `proxyConfiguration` | object | Proxy configuration for the Actor. Configure it using the Apify proxy editor (the actor reads this object and uses it to create a proxy URL when applicable). |

***

### Output

The actor saves the collected results in JSON format as a dataset using `await Actor.push_data(results)`.

Example output (array of objects):

```json
[
  {
    "keyword": "john",
    "title": "Example title from the publicly available source",
    "description": "Example extracted text that may contain emails",
    "url": "https://example.com/example-link",
    "email": "john.smith@gmail.com"
  }
]
```

#### Output Fields

| Field | Type | Description |
| --- | --- | --- |
| `keyword` | string | The keyword from your input that produced this record. |
| `title` | string | The `h3` title text extracted from the publicly available source content. |
| `description` | string | Extracted text content (pulled from the source description area and converted to plain text). |
| `url` | string | The link (`href`) associated with the result being processed. |
| `email` | string | The extracted email address that matches one of your `customDomains`. |
| `error_message` | string | ❌ Not produced by this actor (there is no `error_message` field in the pushed result objects). |

> Note: The actor deduplicates emails using an internal `seen_emails` set, so each unique email should appear only once in the dataset.

***

### How to use Trendyol Email Scraper (via Apify Console)

1. **Open Apify Console**\
   Log in at https://console.apify.com and go to the **Actors** tab.

2. **Find this actor**\
   Search for **Trendyol Email Scraper** in the marketplace and open the actor page.

3. **Enter your INPUT settings**\
   In the **INPUT** section, add the JSON fields for:
   `keywords` (required), and optionally `location`, `customDomains`, and `proxyConfiguration`.

4. **Set keyword ideas for Trendyol leads email scraping**\
   Add multiple items to `keywords` if you want broader coverage. The actor runs through each keyword.

5. **Filter to the email domains you care about**\
   Update **Custom Email Domains** (`customDomains`) to keep only matching emails (e.g., `@gmail.com`, or other domains you target for outreach).

6. **Configure proxies (optional but recommended for scale)**\
   Use **Proxy Configuration** if you have special proxy needs. If you don’t provide it, the actor may still attempt a proxy-based approach internally and includes a fallback when no emails are found.

7. **Run the actor and watch logs**\
   During execution, you’ll see logs indicating scraping progress and whether emails were extracted for a given keyword/domain combination.

8. **Open results and export**\
   After completion, open the dataset in the **OUTPUT** tab. Export it from Apify as JSON/CSV for your **Trendyol email list** workflow.

No coding required—get accurate results in minutes with this Trendyol email collection software.

***

### Advanced features & SEO optimization

- 🚀 **Engineered for “Trendyol email scraper” lead workflows**: Works as a **Trendyol bulk email scraping tool** by combining `keywords` with `customDomains`.
- 🧭 **Location-aware collection for more relevant leads**: Add `location` to tighten results when you need regional outreach (Trendyol e-ticaret email veri çekme).
- 🔄 **Resilience via fallback behavior**: If a run doesn’t produce emails, it attempts an additional approach to improve coverage.
- 📊 **Detailed, structured records**: Output is consistent JSON objects containing `keyword`, `title`, `description`, `url`, and `email`, making it easier to analyze with a Trendyol email finder workflow.
- 🧱 **Deduplication for cleaner datasets**: Prevents repeating the same email address in your final dataset.

***

### Best use cases

- 📈 **B2B lead generation for Trendyol seller outreach**: Build a targeted prospect list by extracting emails tied to **Trendyol seller email scraper** use cases.
- 🎯 **Marketing segmentation by keyword intent**: Run multiple `keywords` batches to produce separate lead groups for **Trendyol customer email extractor** campaigns.
- 🔬 **Market research & contact mapping**: Combine extracted emails with descriptions to understand how brands/organizations present themselves publicly (for Trendyol business email scraping).
- 🧾 **Data enrichment pipelines**: Feed results into CRM or marketing automation systems that store `email` plus context (`keyword`, `title`, `url`).
- 🧠 **Researcher workflows**: Use the dataset to support analyses around email contact availability across domains (Trendyol email harvesting).
- 🛒 **E-commerce contact discovery**: Find outreach-ready contacts for e-commerce brands using a **Trendyol contact email scraper** approach.
- 💻 **Developer automation**: Integrate the actor into scheduled runs to keep a growing **Trendyol email list** up to date.

***

### Technical specifications

- **Supported Input Formats**
  - ✅ `keywords` as an array of strings (required)
  - ✅ `location` as a string (optional)
  - ✅ `platform` as a string (enum value: `Trendyol`)
  - ✅ `customDomains` as an array of domains
  - ✅ `proxyConfiguration` as an object (Apify proxy configuration editor)

- **Proxy Support**
  - ✅ Uses the provided `proxyConfiguration` when enabled in your configuration
  - ✅ Includes a fallback path when no emails are found

- **Retry Mechanism**
  - ✅ Includes fallback behavior to improve results coverage
  - ❌ No explicit “number of retries” setting is exposed in the input schema (the actor implements fallback logic, but there is no user-facing retry parameter)

- **Dataset Structure**
  - ✅ Dataset records are pushed as JSON objects with fields: `keyword`, `title`, `description`, `url`, `email`

- **Rate Limits & Performance**
  - ✅ Designed for batch runs across combinations of `keywords` and `customDomains`
  - ✅ Expected to vary depending on proxy latency and page availability (no fixed timing guarantees are provided)

- **Limitations**
  - ❌ Only emails that match the provided `customDomains` are extracted and saved
  - ❌ If no matching email patterns are found in the processed publicly available content, the dataset may be empty for that keyword/domain combination

***

### FAQ

#### What does Trendyol Email Scraper extract?

✅ Trendyol Email Scraper extracts email addresses that match the domains you provide in `customDomains`. Alongside each email, it also saves the related `keyword`, `title`, `description`, and `url` in the output dataset.

#### Do I need a location, or can I run without one?

✅ You can run without `location`. If you leave `location` as an empty string (the default), the actor won’t apply a location filter.

#### How do Custom Email Domains work?

✅ The actor uses `customDomains` to keep only matching emails. For example, if you set `customDomains` to `["@gmail.com"]`, it will only extract emails ending with `@gmail.com`.

#### Does it support proxies?

✅ Yes. The actor accepts `proxyConfiguration` as input and will use it to create a proxy configuration when applicable. It also includes fallback behavior that may switch proxy approach when no emails are found.

#### What output will I get after the run?

✅ You’ll get a dataset of JSON objects pushed by the actor, where each object includes `keyword`, `title`, `description`, `url`, and `email`.

#### Can I use this for bulk Trendyol email scraping tool workflows?

✅ Yes. The actor loops through every combination of your `keywords` and `customDomains`, making it suitable for building a **Trendyol email list** in bulk.

#### Is this actor able to extract emails that don’t match my domain filter?

❌ No. If an extracted email doesn’t match one of the `customDomains` you provided, it won’t be saved in the output.

#### Is there a legal or compliance requirement for using this data?

✅ You’re responsible for complying with applicable laws and platform terms (including GDPR/CCPA considerations and spam regulations). This actor works with **publicly accessible sources**, but compliance is always on the user.

***

### Support & feature requests

Want to improve your Trendyol email scraper results? Share feedback and feature requests for **Trendyol Email Scraper** with us.

- 💡 **Feature Requests**: Ideas like CSV export options, more flexible filtering, or additional fields in the dataset are welcome.
- 📧 **Contact**: Email us at <dataforleads@gmail.com>.

Your feedback helps shape the next iterations of this Trendyol email collection software.

***

### Closing CTA / Final thoughts

*If you’re looking for the most comprehensive Trendyol email scraper for outreach and research, this actor is ready to help you turn keywords into structured contact data—fast.*\
*Get started with Trendyol Email Scraper and build your Trendyol email list at scale.*

***

### Disclaimer

**This Trendyol Email Scraper accesses publicly accessible sources** only. It does not access private profiles, authenticated data, or password-protected content.

You are responsible for complying with applicable laws and regulations (including GDPR/CCPA), as well as respecting platform terms, data privacy rules, and spam regulations.

For data removal requests, contact <dataforleads@gmail.com>.

Always use Trendyol Email Scraper responsibly, ethically, and for legitimate purposes.

# Actor input Schema

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

A list of keywords to search for.

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

Location to filter search results.

## `platform` (type: `string`):

Select platform.

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

List of custom email domains

## `proxyConfiguration` (type: `object`):

Configure proxies for this Actor.

## Actor input object example

```json
{
  "keywords": [
    "john",
    "marketing"
  ],
  "location": "",
  "platform": "Trendyol",
  "customDomains": [
    "@gmail.com"
  ]
}
```

# 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": [
        "john",
        "marketing"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("solid-scraper/trendyol-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": [
        "john",
        "marketing",
    ],
    "location": "",
    "customDomains": ["@gmail.com"],
}

# Run the Actor and wait for it to finish
run = client.actor("solid-scraper/trendyol-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": [
    "john",
    "marketing"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com"
  ]
}' |
apify call solid-scraper/trendyol-email-scraper --silent --output-dataset

```

## MCP server setup

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