# Trivago Email Scraper (`email_scraper/trivago-email-scraper`) Actor Trivago Email Scraper extracts publicly listed email addresses from Trivago search results using targeted keywords, locations, and custom email domains. Build structured Trivago lead lists for hotels, accommodation businesses, travel professionals, and outreach campaigns. - **URL**: https://apify.com/email\_scraper/trivago-email-scraper.md - **Developed by:** [Email Scraper](https://apify.com/email_scraper) (community) - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $1.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 ### Trivago Email Scraper The **Trivago Email Scraper** extracts publicly listed email addresses associated with Trivago search results using targeted keywords and optional geographic filtering. It is designed for users who need structured contact data for research, lead discovery, market analysis, and other data-collection workflows. Provide one or more keywords, select the email domain suffixes you want to search for, optionally specify a country, state, or city, and configure the maximum number of emails for each keyword-and-domain combination. The Actor returns structured records containing the keyword, result title, description, source URL, and discovered email address. The Actor works best with specific, relevant search phrases. Instead of using only broad terms such as `Hotel`, users can combine more focused searches such as `Hotel Manager`, `Boutique Hotel`, `Resort`, or `Travel Accommodation` to explore different types of publicly indexed Trivago-related results. ### What Is a Trivago Email Scraper? A **Trivago Email Scraper** is a data extraction tool that searches publicly indexed Trivago pages for email addresses matching the email domain suffixes configured in the Actor input. The workflow is keyword-driven. For every keyword and selected email-domain combination, the Actor searches for relevant Trivago results and examines their publicly indexed descriptions for matching email addresses. Relevant results can then be stored in the Apify dataset as structured records. This approach can be useful when you need contact-oriented information connected to hospitality, accommodation, travel, hotel, or other Trivago-related search topics. The Actor accepts: - Multiple search keywords or queries - An optional country, state, or city location - One or more email domain suffixes such as `@gmail.com` - A configurable maximum email target - Optional words or phrases for filtering out unwanted descriptions Results are pushed incrementally to the dataset as they are discovered. ### Key Features | **Feature** | **Description** | **User Benefit** | | ---------------------------- | -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ | | Keyword-based search | Searches Trivago-related results using your specified keywords or queries. | Helps target specific hospitality and travel-related topics. | | Multiple keywords | Accepts a list of search terms in a single run. | Expands research coverage without creating separate runs for every term. | | Location filtering | Supports an optional country, state, or city value. | Helps narrow searches to a geographic market. | | Custom email domains | Lets you specify email suffixes such as `@gmail.com` or `@yahoo.com`. | Targets the types of email addresses relevant to your workflow. | | Per-combination email target | The `maxEmails` setting is applied independently to each keyword + domain combination. | Provides predictable targeting across multiple search combinations. | | Exclude words | Filters out descriptions containing configured words or phrases. | Reduces unwanted results based on description content. | | Structured dataset output | Stores discovered records with consistent fields. | Makes extracted data easier to review and process. | | Incremental dataset storage | Results are pushed as they are collected. | Keeps discovered records available during the run. | ### What Data Can You Extract? The Trivago Email Scraper produces structured records focused on the relationship between a search keyword, a Trivago-related result, and a matching email address. Each collected record includes: - **Keyword** — the search term that produced the result. - **Title** — the title associated with the indexed result. - **Description** — the publicly indexed description or snippet used to identify the email address. - **URL** — the source result URL. - **Email** — the extracted email address matching one of the configured domain suffixes. The Actor also adds an internal dataset field named `network` with the value `Trivago.com` when the record is pushed. The default dataset table view highlights the five primary user-facing fields: keyword, title, description, URL, and email. Because extraction depends on publicly indexed information, the amount and quality of available data can vary between searches. ### Why Use This Actor? Manual searching for contact information can require repeating similar searches across many keywords, locations, and email-domain variations. This Actor automates that repetitive search workflow and organizes discovered email addresses into a consistent dataset. It can be useful when you need to: - Research hospitality and accommodation markets. - Build structured datasets from public search results. - Explore contacts associated with specific travel-related topics. - Perform keyword-based lead research. - Compare results across different locations. - Collect data for downstream analysis or business workflows. - Repeat searches using different email-domain suffixes. The Actor is particularly useful when your search strategy is more specific than a single broad keyword. ### Benefits #### Targeted Research Using several focused keywords can uncover different groups of relevant results. For example, hospitality research may use terms such as `Hotel`, `Resort`, `Boutique Hotel`, `Hotel Manager`, or `Accommodation`. #### Geographic Filtering The optional location field lets you narrow the search using a country, state, or city. Leaving the field empty allows the search to proceed without that geographic filter. #### Flexible Email Matching You can provide multiple email suffixes to search for different types of addresses. This allows the same keyword set to be tested against different domain patterns. #### Structured Results Every discovered address is associated with the keyword, title, description, and source URL that produced it. This makes the resulting dataset easier to inspect and analyze. ### How to Use the Trivago Email Scraper 1. Enter one or more relevant keywords in the **Keywords or Queries** field. 2. Add a country, state, or city in **Region / Location** when geographic targeting is required. 3. Enter one or more email suffixes in **E-mail domain suffixes**, such as `@gmail.com`. 4. Set `maxEmails` to the desired target for each keyword + domain combination. 5. Add words or phrases under **Exclude words** when certain descriptions should be ignored. 6. Start the Actor. 7. Review the structured records in the resulting dataset. For broader coverage, use several related keywords rather than relying on one generic term. ### Input Fields | **Field** | **Type** | **Required** | **Default** | **Description** | | --------------- | ---------------- | ------------ | ---------------------------- | ------------------------------------------------------------------------------------------------------ | | `keywords` | Array of strings | Yes | `["Hotel", "Accommodation"]` | Search keywords or queries to use for Trivago-related results. | | `location` | String | No | `""` | Optional country, state, or city used to narrow the search. | | `customDomains` | Array of strings | No | `["@gmail.com"]` | Email domain suffixes to search for. | | `maxEmails` | Integer | No | `5` | Maximum target per keyword + domain combination. Accepted range is 1–10,000 in the Actor input schema. | | `excludeWords` | Array of strings | No | `[]` | Words or phrases that cause matching result descriptions to be skipped. | The `keywords` field accepts multiple entries. The `location` field can be left blank when geographic filtering is unnecessary. For `excludeWords`, matching is case-insensitive. A single word is treated as a whole-word match, while a phrase is matched as a case-insensitive substring. ### Input Example ```json { "keywords": [ "Hotel", "Boutique Hotel", "Hotel Manager" ], "location": "United States", "customDomains": [ "@gmail.com", "@yahoo.com", "@outlook.com" ], "maxEmails": 10, "excludeWords": [ "crypto", "onlyfans" ] } ``` Each keyword and email-domain suffix is processed as its own search combination. Therefore, using more keywords or more domains can increase the overall number of combinations processed. ### Output The Actor stores extracted records in the Apify dataset. Results are generated incrementally during processing rather than being held until the end of the run. The primary output contains: | **Field** | **Description** | | ------------- | ---------------------------------------------------------------------------------------------- | | `network` | Identifies the source network as `Trivago.com`. | | `keyword` | The search keyword associated with the record. | | `title` | Title of the indexed search result. | | `description` | Description or snippet associated with the search result. | | `url` | Source URL associated with the result. | | `email` | Email address extracted from the result description and matching the configured domain suffix. | The default dataset view displays `keyword`, `title`, `description`, `url`, and `email` as its main table columns. ### Output Example ```json { "network": "Trivago.com", "keyword": "Boutique Hotel", "title": "Example Hotel", "description": "Contact us at example@gmail.com for accommodation information.", "url": "https://www.trivago.com/example", "email": "example@gmail.com" } ``` The values above are illustrative examples showing the output structure. Actual titles, descriptions, URLs, and email addresses depend on the publicly indexed results available for the selected search terms. ### Use Cases #### Hospitality Market Research Research hotel, accommodation, resort, and related travel topics using targeted search terms and optional geographic filters. #### Lead Research Create structured contact datasets from publicly indexed results where matching email addresses are available. #### Business Intelligence Combine keyword, location, source URL, description, and email data for research and analysis workflows. #### Dataset Creation Build organized datasets for later review, enrichment, categorization, or internal analysis. #### Competitive Research Explore publicly indexed Trivago-related information across different hospitality segments and geographic markets. #### Automated Research Workflows Use the Actor as part of a repeatable data-collection workflow on the Apify platform. ### Advantages The Actor provides several practical advantages for keyword-based Trivago research: - Multiple search keywords can be processed in a single run. - Geographic filtering can be enabled when required. - Email-domain suffixes are configurable. - Exclusion rules can remove descriptions containing unwanted terms. - Results are returned in a consistent structured format. - Duplicate email addresses are tracked so the same address is not repeatedly stored during the run. ### Limitations The Actor can only extract email addresses that are available in the publicly indexed search-result information it processes. A keyword, location, or email-domain combination may therefore produce few or no results. The requested `maxEmails` value is a target rather than a guarantee that the corresponding number of unique addresses will always be found. For free users, the Actor applies a maximum result limit of **100 emails** to the configured `maxEmails` value. Paid users do not receive this code-level free-tier cap. Because the configured target operates per keyword + domain combination, the total number of collected records across a run can differ from the value entered in `maxEmails`. Search coverage can also vary because publicly indexed information changes over time. ### Pros and Cons | **Pros** | **Cons** | | ------------------------------------------------- | --------------------------------------------------------- | | Multiple keywords can be searched in one run. | Results depend on publicly indexed information. | | Optional country, state, or city filtering. | Some keyword/domain combinations may return few results. | | Configurable email-domain suffixes. | The requested email target is not guaranteed. | | Exclusion words and phrases are supported. | Search coverage can vary over time. | | Structured records are saved to an Apify dataset. | Free users are subject to the 100-email code-level limit. | ### Comparison With Alternative Approaches | **Capability** | **This Actor** | **Manual / Typical Alternative** | | ---------------------------- | -------------------------------- | --------------------------------------------------------------- | | Keyword-based research | Supported | Usually performed manually for each search. | | Multiple search combinations | Supported | Requires repeating searches and organizing results manually. | | Location filtering | Supported | Requires adding location terms manually to individual searches. | | Email-domain targeting | Configurable | Typically requires separate search patterns. | | Exclusion filtering | Supported through `excludeWords` | Often handled manually during review. | | Structured output | Apify dataset records | May require manual copying and formatting. | | Incremental result storage | Supported | Usually depends on the user's manual workflow. | This comparison describes workflow differences rather than guaranteeing a particular result volume or quality. ### Best Practices For more useful searches, use specific keywords that clearly describe the audience or hospitality category you are researching. Start with a small `maxEmails` value to validate your keyword strategy before increasing the target. When results are sparse: - Add closely related keywords. - Try additional email-domain suffixes. - Broaden or remove the location filter. - Review whether exclusion terms are too restrictive. Use several focused searches rather than relying exclusively on one broad term. Review the returned descriptions and URLs before using the data in downstream workflows, especially for high-value research. ### Troubleshooting #### Invalid Input Check that `keywords`, `customDomains`, and `excludeWords` are supplied as arrays of strings. Ensure `maxEmails` is an integer within the documented 1–10,000 input range. #### Empty Results Try broader or more specific keywords, remove an overly restrictive location, or test additional email-domain suffixes. #### Partial Results A search may return fewer emails than requested because the relevant indexed pages may not contain matching public email addresses. #### Missing Fields Search-result content can vary. Some records may contain limited titles or descriptions depending on the available indexed information. #### Temporary Failures Review the Actor run logs and consider running the search again with validated inputs when a temporary processing issue occurs. ### Frequently Asked Questions #### What does the Trivago Email Scraper do? The Trivago Email Scraper searches publicly indexed Trivago-related results using your keywords and extracts email addresses matching the configured domain suffixes. #### What input does the Actor require? The only required input is `keywords`, which is an array of search terms or queries. #### Can I use multiple keywords? Yes. The `keywords` field accepts multiple values, allowing you to search several related topics in one run. #### Can I target a specific country or city? Yes. Use the optional `location` field and enter a country, state, or city. Leave it empty when geographic filtering is not needed. #### Can I search for different email providers? Yes. The `customDomains` field accepts multiple email suffixes, such as `@gmail.com`, `@yahoo.com`, and `@outlook.com`. #### What does `maxEmails` control? It sets the maximum target for each keyword + domain combination. It does not represent a guaranteed number of unique emails for the entire run. #### What happens when I use exclude words? The Actor skips a search-result description when it contains one of the configured excluded words or phrases. Matching is case-insensitive. #### Does the Actor guarantee the requested number of emails? No. The configured value is a collection target. Actual results depend on publicly indexed information and the availability of matching email addresses. #### What data is returned? Each result contains the network, keyword, title, description, URL, and extracted email address. The default dataset table highlights the keyword, title, description, URL, and email fields. #### Can I use this Actor for automated research? Yes. The Actor is designed to run as an Apify Actor and return structured dataset results that can be incorporated into repeatable data-collection workflows. #### Why did I receive fewer results than expected? The selected search terms may be too narrow, the location filter may be restrictive, or there may simply be limited publicly indexed pages containing matching email addresses. ### NLP Keywords - Trivago email extraction - Trivago contact data - Trivago profile data - Trivago search results - Trivago leads - hotel contact emails - hospitality email leads - hotel email addresses - accommodation contact data - travel industry contacts - hotel research data - hospitality lead research - public email extraction - keyword-based email search - geographic lead filtering - email domain filtering - structured contact dataset - hotel market research - travel business data - hospitality data collection ### Related Keywords - Trivago email scraper - Trivago email extractor - scrape Trivago emails - Trivago contact scraper - Trivago lead scraper - hotel email scraper - hotel contact extractor - accommodation email finder - hospitality contact scraper - hotel lead generation data - travel contact data extractor - hotel business email search - Trivago contact data extraction - hospitality email collection - hotel market research scraper - accommodation contact research - travel industry email leads - hotel directory email extraction - keyword-based hotel research - public hospitality email data ### Final Overview The **Trivago Email Scraper** provides a structured way to search Trivago-related public search results and identify email addresses that match your selected domain suffixes. Its configurable keywords, optional location filtering, exclusion rules, and per-combination email targets make it suitable for targeted hospitality and travel research. For the most relevant results, begin with focused keywords, validate a small test run, review the resulting dataset, and then expand your search strategy with related terms, additional locations, or additional email-domain suffixes as appropriate. **Contact me:** # Actor input Schema ## `keywords` (type: `array`): A list of keywords or queries to search for. ## `location` (type: `string`): Optional country, state or city used to narrow the search. Leave it empty to search without a geographic filter. ## `customDomains` (type: `array`): List of custom email domains ## `maxEmails` (type: `integer`): How many addresses each search keyword + domain suffix combination may collect before the finder moves on to the next one. This is a per-combination target, not a run-wide total: with 3 keyword and 2 Domains and a limit of 20, the run works through all 6 combinations and aims for up to 20 addresses in each, so up to 120 overall. Lower values finish sooner and cost less; higher values dig deeper but never guarantee a fuller result, since the run can only find what is publicly listed. ## `excludeWords` (type: `array`): Words or phrases you do not want to see. ## Actor input object example ```json { "keywords": [ "Hotel", "Accommodation" ], "location": "", "customDomains": [ "@gmail.com" ], "maxEmails": 5, "excludeWords": [] } ``` # 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "keywords": [ "Hotel", "Accommodation" ], "location": "", "customDomains": [ "@gmail.com" ], "excludeWords": [] }; // Run the Actor and wait for it to finish const run = await client.actor("email_scraper/trivago-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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "keywords": [ "Hotel", "Accommodation", ], "location": "", "customDomains": ["@gmail.com"], "excludeWords": [], } # Run the Actor and wait for it to finish run = client.actor("email_scraper/trivago-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": [ "Hotel", "Accommodation" ], "location": "", "customDomains": [ "@gmail.com" ], "excludeWords": [] }' | apify call email_scraper/trivago-email-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,email_scraper/trivago-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 ` 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/YvTNZDnRMMM30sX0H/builds/dBdd4IbGKh4yc9kLm/openapi.json