# Xing Email Scraper - Domain Filter & Deduplication (`insightflow/xing-email-scraper-powerful-and-intelligent`) Actor

🟢 XING Email Scraper — turn XING searches into a clean professional email list. Filter by keyword, location and domain, merge aliases and decode hidden addresses. 🇩🇪 For DACH B2B sales & German recruiting.

- **URL**: https://apify.com/insightflow/xing-email-scraper-powerful-and-intelligent.md
- **Developed by:** [InsightFlow](https://apify.com/insightflow) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.99 / 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.

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

## 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

### Xing Email Scraper 🔍

**Xing Email Scraper** helps you extract emails from Xing quickly and at scale, replacing manual profile hunting with a streamlined Xing email extractor for marketers, recruiters, and sales pros. It’s built for Xing lead generation, Xing contact scraper workflows, and fast public web data collection so you can find relevant contacts with less effort and more consistency. 🚀

### 🌟 Key Features of Xing Email Scraper

| Feature | Benefit |
|---|---|
| ✅ **Targeted Keyword Search** | Use your chosen keywords to focus on relevant Xing profile data and improve lead quality. |
| ✅ **Location Filtering** | Narrow results by location when you want more specific Xing business contacts. |
| ✅ **Custom Email Domain Filter** | Filter for specific domains such as `@gmail.com` or `@yahoo.com` to shape your Xing B2B leads. |
| ✅ **Maximum Email Cap** | Control how many emails are collected in a run to manage cost and output size. |
| ✅ **Built-In Proxy Support** | Helps keep scraping reliable when working with public web data at larger volumes. |
| ✅ **Incremental Saving** | Results are saved as they are found, which helps protect long-running Xing data extraction jobs. |

### 📥 Input — Xing Email Scraper Parameters

```json
{
  "keywords": [
    "manager",
    "founder"
  ],
  "location": "Berlin",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20
}
```

| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| `keywords` | Array | Yes | `["manager", "founder"]` | A list of keywords or queries used to find relevant Xing profiles. |
| `location` | String | No | `""` | Optional location filter for narrowing search results. |
| `customDomains` | Array | No | `["@gmail.com", "@yahoo.com"]` | Email domains to focus on during Xing email extraction. |
| `maxEmails` | Integer | No | `20` | Maximum number of emails to collect before the actor stops. |

### 📤 Output — What Xing Email Scraper Returns

The actor saves each result as a JSON record in your Apify dataset.

```json
{
  "keyword": "manager",
  "title": "Anna Müller",
  "description": "HR Manager at GreenTech Consulting in Berlin",
  "url": "https://www.xing.com/profile/Anna_Mueller",
  "email": "anna.mueller@gmail.com"
}
```

| Field | Label | Format | Description |
|---|---|---|---|
| `keyword` | Keyword | text | The keyword that surfaced the result. |
| `title` | Title | text | The Xing profile title or name shown for the result. |
| `description` | Description | text | The visible profile description or summary text. |
| `url` | Url | link | The direct link to the Xing profile or source page. |
| `email` | Email | text | The email address found in the public data. |

### 💻 How to Use Xing Email Scraper — Step-by-Step

1. **Open the Actor** — Find Xing Email Scraper in Apify and open the run configuration.
2. **Enter Keywords** — Add job titles, roles, industries, or other terms relevant to your Xing lead generation goals.
3. **Set Location** — Optionally narrow results by city or region for more focused Xing contact extraction.
4. **Add Email Domains** — Include domains such as `@gmail.com` or company email domains to refine the search.
5. **Set Max Emails** — Choose how many results you want per run to control scraping volume.
6. **Run the Actor** — Start the run and monitor progress in the logs.
7. **Export Results** — Download your Xing email list from the dataset in JSON format.

### 💡 Best Use Cases for Xing Email Scraper

- 🎯 **B2B Lead Generation** — Build targeted Xing B2B leads for outreach campaigns.
- 📣 **Email Marketing** — Collect contacts for newsletters, sequences, and follow-ups.
- 🤝 **Recruitment** — Find Xing recruitment leads and contact professionals directly.
- 🔬 **Market Research** — Study industries, roles, and profiles for research projects.
- 📊 **CRM Enrichment** — Add Xing contact data to existing lead records.

### Disclaimer

This actor only accesses publicly available data on Xing. It does not scrape private profiles, authenticated content, or password-protected pages. Users are solely responsible for ensuring their use complies with Xing’s Terms of Service, GDPR, CCPA, and applicable anti-spam laws. This tool is intended for legitimate purposes only, including research, lead generation, and marketing in compliance with local regulations. For data-removal requests, contact 📧 <insightflowofficial@gmail.com>.

### 🆘 Support & Feedback

Have a question or found an issue with Xing Email Scraper? We’re here to help.

- 🐞 **Bug Reports:** Share issues through the project’s issue tracker.
- ✨ **Custom Solutions & Feature Requests:** Reach out if you need tailored Xing data extraction or additional workflow support.
- 📧 **Email:** <insightflowofficial@gmail.com>

Your feedback helps improve the Xing email scraper experience for everyone.

### MX Lookup

Every address is checked at the DNS level: the actor resolves the mail domain's
MX records and reports what it found.

| Field | Meaning |
| --- | --- |
| `mxFound` | `true` when the domain publishes at least one mail server |
| `mxHost` | The lowest-preference (primary) mail server |
| `mxRecords` | Every MX record found, in preference order |
| `mxProvider` | Who runs the mail: Google Workspace, Microsoft 365, Zoho, Proton, ... |
| `mxStatus` | `found`, `no_records`, `no_such_domain`, `timeout`, `error`, or `skipped` |

**Inputs**

- **MX Lookup** - turn the check on or off (default: on).
- **Only keep contacts whose domain has an MX record** - drop unreachable domains.
  Only a definite negative (`no_records` / `no_such_domain`) drops a contact; a
  timeout or resolver error is treated as unknown and the lead is kept.
- **MX lookup timeout (seconds)** - per-domain DNS budget, 1-15s.

This is a domain-level check. It confirms the domain can receive mail; it does
not verify that an individual mailbox exists.

# Actor input Schema

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

A list of keywords or queries to search for.

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

Location to filter search results.

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

List of custom email domains

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

Maximum number of emails to collect. The scraper will stop once this limit is reached. Setting a higher limit allows for more potential results but doesn't guarantee reaching that number. This helps save costs by controlling scraping time.

## `minLeadScore` (type: `integer`):

Drop any contact whose Lead Score (0-100) falls below this. Leave at 0 for no filter.

## `mxLookup` (type: `boolean`):

Resolve each address's domain to its mail servers. Adds the resolved MX hosts and the mail provider (Google Workspace, Microsoft 365, ...) to every result, and feeds the Lead Score. DNS-level only - it confirms the domain can receive mail, not that the individual mailbox exists.

## `requireMxRecord` (type: `boolean`):

Drop any contact whose domain provably accepts no mail. A lookup that times out or errors is treated as unknown and kept, so a DNS hiccup never silently deletes good leads.

## `mxTimeoutSecs` (type: `integer`):

How long to wait for each DNS answer. Clamped to 1-15 seconds.

## Actor input object example

```json
{
  "keywords": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "minLeadScore": 0,
  "mxLookup": true,
  "requireMxRecord": false,
  "mxTimeoutSecs": 3
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

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

// Run the Actor and wait for it to finish
const run = await client.actor("insightflow/xing-email-scraper-powerful-and-intelligent").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": [
        "manager",
        "founder",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("insightflow/xing-email-scraper-powerful-and-intelligent").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": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ]
}' |
apify call insightflow/xing-email-scraper-powerful-and-intelligent --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,insightflow/xing-email-scraper-powerful-and-intelligent"
        }
    }
}

```

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/QmgNtyxAh16KZsPtD/builds/JVCohOhg1te9c2y1b/openapi.json