# IndustryBuying Email Scraper (`email_scraper/industrybuying-email-scraper`) Actor IndustryBuying Email Scraper extracts publicly indexed emails from IndustryBuying using targeted keywords, location filters, custom email domains, and exclusion terms. Build structured contact datasets for supplier discovery, manufacturer research, B2B leads, and industrial business research. - **URL**: https://apify.com/email\_scraper/industrybuying-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 ### IndustryBuying Email Scraper IndustryBuying Email Scraper is an Apify Actor designed to find publicly indexed email addresses associated with IndustryBuying pages and profiles using targeted search keywords. It helps turn keyword-based IndustryBuying research into structured contact data containing the search keyword, result title, description, URL, and extracted email address. You provide one or more search keywords, optionally specify a country, state, or city, select the email domains you want to search for, and optionally exclude results containing particular words or phrases. The Actor then processes the configured keyword and email-domain combinations and adds discovered email records to an Apify dataset. The IndustryBuying Email Scraper is useful for supplier discovery, manufacturer research, industrial business research, B2B lead research, market analysis, and other workflows where publicly indexed IndustryBuying contact information can support data collection. ### What Is an IndustryBuying Email Scraper? An IndustryBuying Email Scraper is a keyword-driven data collection tool focused on email addresses that appear in publicly indexed IndustryBuying search results. Instead of manually searching IndustryBuying-related pages and checking individual results for contact information, you can provide targeted search terms and let the Actor process the search combinations automatically. The resulting dataset is structured around useful lead information: - Search keyword used - Result title - Result description - Result URL - Extracted email address - Network identifier included in the generated record The Actor is designed for research and data collection workflows where structured email records are more useful than manually reviewing search results one by one. ### Key Features | Feature | Description | User Benefit | | ---------------------------- | -------------------------------------------------------------------- | ----------------------------------------------------------- | | Keyword-based search | Search using one or multiple keywords or queries | Target specific IndustryBuying categories or business types | | Multiple keywords | Process a list of search terms in one run | Cover different search intents in the same dataset | | Location filtering | Optionally add a country, state, or city | Narrow research toward a geographic area | | Custom email domains | Specify domains such as `@gmail.com` or `@yahoo.com` | Focus collection on relevant email types | | Per-combination email target | Configure the maximum emails for each keyword and domain combination | Control the amount of data collected | | Exclude words | Skip descriptions containing selected words or phrases | Reduce unwanted records | | Duplicate prevention | Previously collected email addresses are not added again | Keep the dataset cleaner | | Incremental dataset results | Results are added to the Apify dataset during processing | Review collected records as the run progresses | ### What Data Can You Extract? The IndustryBuying Email Scraper produces structured records containing contact and search-result information. The primary data categories are: - **Keyword:** The keyword associated with the search that produced the result. - **Title:** The title of the indexed result. - **Description:** The description or search-result snippet associated with the result. - **URL:** The URL associated with the indexed IndustryBuying result. - **Email:** An email address detected in the result description that matches one of the configured domains. - **Network:** The generated record also contains the value `IndustryBuying.com` as a network identifier. The standard Apify dataset view is configured to prominently display the keyword, title, description, URL, and email fields. ### Why Use the IndustryBuying Email Scraper? Manual contact research can require repeatedly searching for different business categories, reviewing results, checking descriptions, and recording contact information. This Actor provides a structured workflow for that type of research. You can create a list of targeted queries such as: - manufacturer - industrial tools - industrial equipment - machinery supplier - electrical supplier - safety equipment supplier You can then combine those terms with selected email domains and, when appropriate, a location filter. This approach makes it easier to create a repeatable IndustryBuying contact research process without manually recording every result. ### Benefits The IndustryBuying Email Scraper provides several practical benefits for data collection: - **Automated research:** Reduce repetitive manual searching for publicly indexed contact information. - **Structured datasets:** Results are stored as organized records in an Apify dataset. - **Targeted discovery:** Specific keywords can focus searches on relevant business categories. - **Geographic targeting:** Optional location terms can narrow searches by country, state, or city. - **Domain targeting:** Search for particular email domain suffixes according to your research requirements. - **Filtering:** Exclude unwanted descriptions using words or phrases. - **Duplicate reduction:** The Actor avoids adding the same email address more than once during the run. - **Scalable keyword research:** Multiple keyword and domain combinations can be configured in a single run. ### How to Use the IndustryBuying Email Scraper The basic workflow is straightforward: 1. Add one or more keywords to the `keywords` field. 2. Optionally enter a country, state, or city in `location`. 3. Add the email domain suffixes you want to search for in `customDomains`. 4. Set `maxEmails` according to the desired collection target. 5. Optionally add terms to `excludeWords`. 6. Start the Actor. 7. Review the resulting records in the Apify dataset. For better targeting, use several specific search phrases rather than relying on one very broad keyword. For example, instead of only searching for `industrial`, you could test terms such as `industrial tools`, `industrial equipment`, `machinery supplier`, or `industrial manufacturer`. ### Input The Actor accepts a JSON object with one required field and four optional configuration fields. | Field | Type | Required | Default | Description | | --------------- | ---------------- | -------- | -------------------------------------- | ------------------------------------------------------------------------------- | | `keywords` | Array of strings | Yes | `["manufacturer", "industrial tools"]` | Search keywords or queries used to find relevant IndustryBuying 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 include in email extraction | | `maxEmails` | Integer | No | `5` | Maximum target for each keyword + domain combination; allowed range is 1–10,000 | | `excludeWords` | Array of strings | No | `[]` | Words or phrases that cause matching result descriptions to be skipped | ### Keywords `keywords` is the only required input. It accepts an array of strings. Each keyword can represent a business category, product type, job-related phrase, industry term, or another relevant search query. More specific keywords can help target a narrower research intent. Example: ```json { "keywords": [ "industrial tools", "machinery supplier", "manufacturer", "electrical equipment supplier" ] } ``` ### Location The optional `location` field accepts a country, state, city, or other geographic phrase. Leave it empty when geographic targeting is not required. Example: ```json { "location": "Mumbai" } ``` A location filter is useful when your research focuses on a particular market or region. ### Custom Email Domains The `customDomains` field accepts an array of email domain suffixes. The default value is: ```json [ "@gmail.com" ] ``` You can add other domains such as: ```json [ "@gmail.com", "@yahoo.com", "@outlook.com" ] ``` You can also specify company-domain suffixes when they are relevant to your research. ### Maximum Emails `maxEmails` controls the target number of emails collected for each keyword and email-domain combination. The accepted range is **1 to 10,000**, with a default of **5**. For example, if you configure: - 3 keywords - 2 email domains - `maxEmails` = 20 the Actor processes six keyword/domain combinations, with a target of up to 20 emails for each combination. This means the potential overall collection can be greater than 20. The requested target is not a guarantee. Results depend on the publicly indexed information available for the selected searches. On the free tier, the Actor applies a maximum limit of 100 emails when the requested limit is missing or exceeds 100. ### Exclude Words The optional `excludeWords` field lets you skip result descriptions containing unwanted words or phrases. For example: ```json { "excludeWords": [ "crypto", "onlyfans" ] } ``` Matching is case-insensitive. Single-word exclusions use whole-word matching, while phrases are matched as phrases within the description. If a description matches an exclusion term, the complete result snippet is skipped and no email is extracted from that result. ### Input Example ```json { "keywords": [ "manufacturer", "industrial tools", "machinery supplier" ], "location": "Mumbai", "customDomains": [ "@gmail.com", "@yahoo.com", "@outlook.com" ], "maxEmails": 20, "excludeWords": [ "crypto", "onlyfans" ] } ``` ### Output The Actor adds discovered records to an Apify dataset. The principal dataset fields are: | Field | Description | | ------------- | ------------------------------------------------------------------------ | | `keyword` | Search keyword that produced the result | | `title` | Title of the indexed result | | `description` | Description or search-result snippet | | `url` | URL associated with the result | | `email` | Extracted email address matching a configured domain | | `network` | Network identifier generated for the record, set to `IndustryBuying.com` | The standard dataset view is configured to display `keyword`, `title`, `description`, `url`, and `email` as a table. Email addresses are extracted when they are present in the available result description and match the configured domain suffixes. ### Output Example ```json { "network": "IndustryBuying.com", "keyword": "industrial tools", "title": "Industrial Tools and Equipment", "description": "Industrial tools and equipment supplier. Contact example@gmail.com for business inquiries.", "url": "https://www.industrybuying.com/example", "email": "example@gmail.com" } ``` The example above illustrates the output structure. Actual titles, descriptions, URLs, and email addresses depend on the indexed search results available during a run. ### Use Cases The IndustryBuying Email Scraper can support several legitimate research and data-collection workflows. - **Supplier research:** Find publicly indexed contact information associated with supplier-related searches. - **Manufacturer discovery:** Research manufacturers and industrial businesses using targeted industry keywords. - **B2B lead research:** Build structured contact datasets for business development research. - **Industrial market research:** Collect search-result information across different industrial categories. - **Business intelligence:** Organize publicly indexed business information for further analysis. - **Market segmentation:** Combine keywords and locations to investigate different business segments. - **Contact research:** Identify publicly indexed email addresses associated with relevant search results. - **Dataset creation:** Build structured datasets for downstream research and analysis. Users should validate collected information before relying on it for important business decisions or communications. ### Advantages The Actor combines several configuration options in one workflow. - Multiple search keywords can be processed in a single run. - Location can be used when geographic targeting is important. - Multiple email-domain suffixes can be configured. - Email targets can be adjusted for each keyword/domain combination. - Exclusion terms provide an additional way to control unwanted results. - Duplicate email addresses are not repeatedly added to the collected dataset. - Results are stored in structured Apify dataset records. These capabilities make the Actor suitable for repeatable IndustryBuying research where consistent input configuration and structured output are useful. ### Limitations There are several practical limitations to consider. - The Actor depends on publicly indexed search information, so not every IndustryBuying page or business will produce an email address. - An email address must appear in the available result description and match a configured domain pattern to be extracted. - A requested `maxEmails` value is a target, not a guarantee that the target will be reached. - Narrow keywords may produce fewer relevant results. - A restrictive location filter may reduce the number of available results. - Exclusion terms can intentionally remove results that otherwise contain usable email information. - Duplicate email addresses are filtered, so the number of unique records can be lower than the combined per-combination targets. - Free-tier runs are subject to the Actor's 100-email maximum when the requested limit is missing or greater than 100. ### Pros and Cons | Pros | Cons | | --------------------------------- | -------------------------------------------------------------- | | Supports multiple keyword queries | Results depend on publicly indexed information | | Optional geographic targeting | Narrow searches can return fewer results | | Custom email-domain filtering | Not every result contains an email | | Exclusion-word filtering | Exclusion terms may remove otherwise useful results | | Structured Apify dataset output | Requested email targets are not guaranteed | | Duplicate email prevention | Free-tier runs have a 100-email maximum in the specified cases | ### Comparison With Alternative Approaches | Capability | IndustryBuying Email Scraper | Manual / Typical Alternative | | -------------------------- | ------------------------------ | -------------------------------------------- | | Keyword-based research | Supported | Usually requires repeated searches | | Multiple keywords | Supported | Often handled separately | | Location targeting | Supported | Depends on the search workflow | | Email-domain targeting | Supported | Usually requires manual filtering | | Exclusion filtering | Supported | Requires manual review or separate filtering | | Structured dataset | Apify dataset | May require manual organization | | Duplicate email prevention | Supported | Usually requires manual checking | | Repeatable configuration | Supported through Actor inputs | Often more manual | This comparison describes workflow differences rather than claiming that one approach is suitable for every research task. ### Best Practices For more focused research, consider the following practices: - Start with a small test run before using a large email target. - Use specific keywords that clearly describe the businesses or products you want to research. - Add several related keywords when one term produces limited results. - Leave `location` empty when you want broader geographic coverage. - Use a location only when regional targeting is important. - Add multiple relevant email domains when appropriate. - Keep exclusion terms focused on genuinely unwanted results. - Review a sample of the dataset to confirm that the results match your research intent. - Use reasonable `maxEmails` values rather than assuming every search can provide the requested number. - Validate important contact information before using it in downstream business workflows. ### Troubleshooting **Empty Results** Try broadening the keywords, removing an overly restrictive location, or adding relevant email domains. Very narrow combinations may have limited publicly indexed information. **Fewer Emails Than Requested** `maxEmails` is a target rather than a guarantee. The Actor can only collect email addresses that are available in the relevant indexed results and match the configured domains. **Too Many Unwanted Results** Use the `excludeWords` field to filter descriptions containing specific unwanted words or phrases. Make sure the exclusion terms are not so broad that they remove relevant records. **Location Produces Limited Results** Try a broader geographic phrase or temporarily leave the location field empty to determine whether additional results are available without geographic filtering. **Unexpected Duplicate-Looking Results** The Actor prevents the same email address from being added repeatedly, but different search results can contain related titles, descriptions, or URLs. Review the complete record when assessing duplicates. **Invalid Input** Check that `keywords`, `customDomains`, and `excludeWords` are arrays of strings and that `maxEmails` is an integer between 1 and 10,000. **Partial Results** Search availability can vary. If a run produces fewer records than expected, review the keyword specificity, location, email domains, and exclusion settings before running a broader search. ### Frequently Asked Questions **What does the IndustryBuying Email Scraper do?** It searches for publicly indexed IndustryBuying results using your keywords and extracts matching email addresses from available result descriptions. **What data does the IndustryBuying Email Scraper return?** The generated records contain the keyword, title, description, URL, email, and a `network` identifier set to `IndustryBuying.com`. **Can I use multiple keywords?** Yes. The `keywords` field accepts an array of search terms, allowing multiple research topics to be processed in one run. **Can I search for a specific city or country?** Yes. Use the optional `location` field to add a country, state, city, or other geographic phrase. **Can I choose which email domains are collected?** Yes. Use `customDomains` to specify the email suffixes you want the Actor to search for, such as `@gmail.com`, `@yahoo.com`, or `@outlook.com`. **What does `maxEmails` control?** It sets the collection target for each keyword and email-domain combination. The accepted value is from 1 to 10,000, with a default of 5. **Will the Actor always collect the number specified in `maxEmails`?** No. The value is a target. The available indexed results and matching email addresses determine how many records can actually be collected. **Can I exclude unwanted results?** Yes. Add words or phrases to `excludeWords`. Matching descriptions are skipped before an email is extracted. **Does the Actor collect duplicate email addresses?** The Actor tracks collected email addresses and does not add the same email address repeatedly during the run. **Why did my run return fewer results than expected?** Possible reasons include narrow keywords, restrictive location settings, limited indexed results, selected email domains, exclusion terms, or simply insufficient publicly indexed email information. **Is the Actor suitable for automated research workflows?** Yes. Its configurable inputs and structured Apify dataset output make it suitable for repeatable data-collection and research workflows. ### NLP Keywords - IndustryBuying email scraper - IndustryBuying email extraction - IndustryBuying contact data - IndustryBuying business contacts - IndustryBuying lead data - IndustryBuying supplier research - IndustryBuying manufacturer research - IndustryBuying business research - IndustryBuying contact extraction - IndustryBuying email finder - industrial supplier leads - industrial manufacturer contacts - B2B contact research - industrial business data - business email extraction - public email data - keyword-based email extraction - structured contact dataset - IndustryBuying lead generation research - industrial market research ### Related Keywords - IndustryBuying contact scraper - IndustryBuying business scraper - IndustryBuying lead scraper - IndustryBuying email finder - scrape IndustryBuying emails - extract IndustryBuying emails - IndustryBuying supplier leads - IndustryBuying manufacturer leads - IndustryBuying B2B leads - IndustryBuying business leads - industrial supplier email list - industrial manufacturer email list - industrial business email research - B2B email data collection - business contact data extraction - supplier contact discovery - manufacturer contact discovery - IndustryBuying data extraction - IndustryBuying keyword search - industrial lead research ### Final Overview IndustryBuying Email Scraper provides a structured way to research publicly indexed IndustryBuying contact information using targeted keywords, optional geographic filters, configurable email domains, and exclusion terms. Its input structure lets you define the type of businesses or products you want to research, while its dataset output organizes the resulting keyword, title, description, URL, and email information into records suitable for further review and analysis. For better coverage, use multiple specific keywords, select relevant email domains, and avoid unnecessarily restrictive filters. Start with a small test run, review the resulting dataset, and then adjust your search configuration based on the information available for your research. *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": [ "manufacturer", "industrial tools" ], "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": [ "manufacturer", "industrial tools" ], "location": "", "customDomains": [ "@gmail.com" ], "excludeWords": [] }; // Run the Actor and wait for it to finish const run = await client.actor("email_scraper/industrybuying-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": [ "manufacturer", "industrial tools", ], "location": "", "customDomains": ["@gmail.com"], "excludeWords": [], } # Run the Actor and wait for it to finish run = client.actor("email_scraper/industrybuying-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": [ "manufacturer", "industrial tools" ], "location": "", "customDomains": [ "@gmail.com" ], "excludeWords": [] }' | apify call email_scraper/industrybuying-email-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,email_scraper/industrybuying-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/ybMadlZZzNQmEJr27/builds/6gVCCqPpdTINPJqjG/openapi.json