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

🌐 Trip.com Email Scraper — turn Trip.com searches into a clean travel partner email list. Filter by keyword, location and domain, merge alias duplicates and decode hidden addresses. ✈️ For APAC travel tech & hotel partnerships.

- **URL**: https://apify.com/insightflow/trip-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

### Trip Email Scraper

**Trip Email Scraper** is a practical Apify actor for finding public email addresses from Trip using your chosen keywords and filters. It helps marketers, data analysts, and researchers turn manual travel inbox scraping into a fast, scalable workflow for travel email scraper, booking email scraper, and trip confirmation scraper use cases. 🚀

### What is Trip Email Scraper? 🔍

Trip Email Scraper is an automated web scraping tool built for collecting publicly available contact details from Trip-related public web data. You provide keywords, optional location filters, and email-domain preferences, and the actor returns structured results in an Apify dataset. It is designed to save time on manual research, improve scale, and support workflows like travel email parser, travel confirmation extractor, and reservation email scraper tasks.

For teams working on trip data extraction or email itinerary extraction, this actor offers a simple way to collect leads from public sources without repetitive copy-paste work. It is especially useful for marketers, recruiters, sales teams, and analysts who need clean, exportable results from a travel inbox scraper workflow. ✨

### What Data Does Trip Email Scraper Collect? 📊

This Trip email scraper captures a focused set of fields that make it easy to organize and review results. Each record includes the keyword used, the lead title, descriptive context, the source URL, and the extracted email address. That makes it useful for travel receipt scraper projects, booking confirmation parser workflows, and travel email extraction pipelines.

| Data Category | Fields Extracted | Description |
|---|---|---|
| Discovery | `keyword` | The keyword that produced the result |
| Identity | `title` | The page or lead title shown in the dataset |
| Context | `description` | Publicly visible description text from the result |
| Navigation | `url` | Direct link to the source page |
| Contact | `email` | Public email address found in the source content |

### What Do Results from Trip Email Scraper Look Like? 👀

Each result is saved as a structured JSON record in your Apify dataset. Here’s a realistic example of what the output can look like:

```json
{
  "keyword": "manager",
  "title": "Maria Johnson",
  "description": "Travel Operations Manager at Horizon Journeys. Contact for booking and itinerary coordination.",
  "url": "https://trip.com/profile/maria-johnson",
  "email": "maria.johnson@horizonjourneys.com"
}
```

Your results can be exported from the dataset in JSON or CSV format for reporting, CRM import, or further analysis. 📁

#### Core Features: Trip Email Scraper ⚡

| Feature | Benefit |
|---|---|
| ✅ Keyword-driven targeting | Use your own keywords to find relevant public Trip contacts |
| ✅ Custom email-domain filters | Focus on domains like `@gmail.com` or `@yahoo.com` |
| ✅ Location filter | Narrow results by location when needed |
| ✅ Configurable result cap | Control run size with `maxEmails` |
| ✅ Built-in proxy support | Helps runs stay reliable on larger jobs |
| ✅ Real-time data saving | Results are stored as they are found |
| ✅ Structured dataset output | Easy to export and analyze |
| ✅ Resume-friendly runs | Progress is persisted to support continuing work |

### Getting Started with Trip Email Scraper 🚀

1. **Open Apify Store** — Go to the Apify Store and open **Trip Email Scraper**.
2. **Create or sign in to your account** — You can run the actor from your Apify dashboard.
3. **Open the Input tab** — Configure your keywords, domains, and optional location.
4. **Add your keywords** — Use terms that match the contacts or travel contexts you want.
5. **Set email filters** — Add custom domains if you want to narrow the results.
6. **Choose a result cap** — Set `maxEmails` to control how many emails are collected.
7. **Start the run** — Launch the actor and watch the logs as results come in.
8. **Review the dataset** — Open the output dataset to preview or export your data.

No coding is required, and the setup is quick enough for fast travel data extraction workflows. ⚡

### Ways to Use Trip Email Scraper 💡

- 🎯 **B2B Lead Generation** — Build outreach lists from public Trip-related contacts
- 📣 **Email Marketing** — Gather contact addresses for newsletters and campaigns
- 🔬 **Market Research** — Study public travel profiles and contact patterns
- 🧾 **Travel Inbox Scraper Workflows** — Organize public travel-related contact data from keywords
- ✈️ **Booking Confirmation Parser Projects** — Support structured extraction for travel communications analysis
- 📊 **CRM Enrichment** — Add public contact information to your existing records

#### Input Parameters — Trip Email Scraper

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

| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| `keywords` | Array | Yes | `["manager","founder"]` | A list of keywords or queries to search for. |
| `location` | String | No | `""` | Location to filter search results. |
| `customDomains` | Array | No | `["@gmail.com","@yahoo.com"]` | List of custom email domains to look for. |
| `maxEmails` | Integer | No | `20` | Maximum number of emails to collect before the actor stops. |

#### Output Parameters — Trip Email Scraper

```json
{
  "keyword": "manager",
  "title": "Maria Johnson",
  "description": "Travel Operations Manager at Horizon Journeys. Contact for booking and itinerary coordination.",
  "url": "https://trip.com/profile/maria-johnson",
  "email": "maria.johnson@horizonjourneys.com"
}
```

| Field | Label | Format | Description |
|---|---|---|---|
| `keyword` | Keyword | text | The keyword used to find the result. |
| `title` | Title | text | The result title shown in the dataset. |
| `description` | Description | text | The publicly visible description text associated with the result. |
| `url` | Url | link | The source page URL. |
| `email` | Email | text | The public email address extracted from the source content. |

### Why Choose Trip Email Scraper? 🏆

Trip Email Scraper is a useful choice when you need public contact extraction with a simple setup and clean structured output. It supports keyword targeting, domain filtering, and location filtering, which makes it flexible for travel email scraper, hotel email scraper, and trip confirmation scraper projects. Built-in proxy support and saved progress help make larger runs more reliable, while the dataset output stays easy to export and reuse. For support, contact <insightflowofficial@gmail.com>. 💬

### How Many Results Can You Scrape? 📈

You can set `maxEmails` anywhere from 1 to 10,000. Actual volume depends on how many public Trip results match your keywords and email-domain filters. Larger runs may take longer, and you can extend the timeout in Run Options if needed. The Apify dataset can store the results as they are found, so you can export data whenever you’re ready.

### Legal Guidelines for Scraping Trip ⚖️

This actor works with publicly available data only. It does not use logins or access private content. Users are responsible for following Trip’s terms, local privacy laws, and applicable email and outreach rules. Use the collected data only for legitimate purposes, and respect opt-out or data-removal requests. For data removal requests, contact <insightflowofficial@gmail.com>. ✅

### FAQ — Trip Email Scraper ❓

#### How does Trip Email Scraper find results?

Trip Email Scraper uses your keywords and email-domain filters to find relevant public contacts from Trip-related public data, then saves matching records to your dataset.

#### What kind of Trip data can I scrape?

You can collect records that include the keyword, title, description, source URL, and public email address when available.

#### Can I use Trip Email Scraper for travel confirmation parsing?

Yes. It can support travel confirmation parser, itinerary email parser, and travel receipt scraper workflows when your use case focuses on public contact extraction and structured travel data review.

#### Does Trip Email Scraper work for booking emails and hotel email scraper workflows?

Yes, it can be useful for booking email scraper, hotel email scraper, and reservation email scraper tasks where public email discovery is the goal.

#### How do I improve my results?

Try broader keywords, add related terms, include more email domains, or adjust the location filter if your results are too limited.

#### How much does Trip Email Scraper cost?

Your cost depends on Apify usage and how large your run is. Use `maxEmails` to control the size of each run and keep results predictable.

#### Is the output easy to export?

Yes. Results are saved in an Apify dataset and can be exported in formats like JSON or CSV from the platform interface.

#### Who should use Trip Email Scraper?

It is a strong fit for marketers, data analysts, researchers, and anyone building travel email extraction or trip data extraction workflows from public sources.

### Conclusion 🏁

Trip Email Scraper is a fast, practical way to collect public email contacts from Trip-related public data with keyword-based targeting, filters, and structured dataset output. If you need a reliable trip email scraper for research, outreach, or analysis, this actor gives you a simple path from search to export. 🚀

### 🆘 Support & Feedback

Have a question or feature request for Trip Email Scraper?

For support, bug reports, or custom solution requests, contact <insightflowofficial@gmail.com>.

### 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/trip-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/trip-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/trip-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/trip-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/8b5ZJB9atUBltLjnz/builds/nTeRkcEGuTMLzqcEb/openapi.json