# Email Extractor (`ryua_marines/email-extractor`) Actor Scans blocks of text, extracts every email address, normalizes them and flags the ones already seen. - **URL**: https://apify.com/ryua\_marines/email-extractor.md - **Developed by:** [Ryusuke Asai](https://apify.com/ryua_marines) (community) - **Categories:** Developer tools, Automation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.20 / 1,000 extracted emails This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. 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 ## Email Extractor Point it at text you already have. Get back every email address in it, normalised, with repeats flagged. Addresses arrive buried in things that were never meant to be parsed: pasted signatures, scraped page text, support transcripts, CSV cells with three contacts in one field. A regex gets you most of the way and then quietly drops `bob+news@example.com` or keeps `Bob@Example.COM` and `bob@example.com` as two different people. ### What you get back One row per address found, in the order they appear. ```json { "source": 0, "email": "alice@example.com", "isDuplicate": false } { "source": 0, "email": "bob@example.com", "isDuplicate": false } { "source": 1, "email": "alice@example.com", "isDuplicate": true } ``` `source` is the index of the text the address came from, so you can trace every row back. A text with no address in it still produces a row, with `error: "no email found"`. Nothing is silently dropped, so the output always accounts for the input. ### Input | Field | Type | Default | | |---|---|---|---| | `texts` | array | — | required. The blocks of text to scan | | `dedupe` | boolean | `true` | flag an address that was already seen | | `maxPerText` | integer | `50` | upper limit of addresses taken from one text | ### What it handles that a quick regex does not - `Bob@Example.COM` and `bob@example.com` are the same person - `mailto:bob@example.com` gives you the address, not the prefix - `write to bob@example.com.` does not keep the sentence's full stop - `user2024@example.com` and `bob+news@example.com` are addresses, not near-misses - `bob@example.co` is a real address; two-letter country domains are not truncated - `a@`, `@b.com` and `c@d` are not addresses and are not returned ### What it does not do - It does not fetch anything. It reads the text you pass in, nothing else. - It does not verify that an address accepts mail. A syntactically valid address can still bounce. - It does not find addresses written to defeat scrapers (`bob [at] example [dot] com`). - It does not enrich, score, or look up who owns an address. ### Before you use it Email addresses are personal data in most places you might be sitting. Extracting them does not by itself give you a basis to contact anyone. Check what you are allowed to do with the list before you build one. # Actor input Schema ## `texts` (type: `array`): Text blocks to scan ## `dedupe` (type: `boolean`): Flag an address that was already seen ## `maxPerText` (type: `integer`): Upper limit of addresses taken from one text ## Actor input object example ```json { "texts": [ "Contact alice@example.com or bob@example.com for details.", "Reach me at Alice@Example.COM" ], "dedupe": true, "maxPerText": 50 } ``` # Actor output Schema ## `results` (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 = { "texts": [ "Contact alice@example.com or bob@example.com for details.", "Reach me at Alice@Example.COM" ], "dedupe": true, "maxPerText": 50 }; // Run the Actor and wait for it to finish const run = await client.actor("ryua_marines/email-extractor").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 = { "texts": [ "Contact alice@example.com or bob@example.com for details.", "Reach me at Alice@Example.COM", ], "dedupe": True, "maxPerText": 50, } # Run the Actor and wait for it to finish run = client.actor("ryua_marines/email-extractor").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 '{ "texts": [ "Contact alice@example.com or bob@example.com for details.", "Reach me at Alice@Example.COM" ], "dedupe": true, "maxPerText": 50 }' | apify call ryua_marines/email-extractor --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,ryua_marines/email-extractor" } } } ``` 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/qeadYxBdm3bsLFnOi/builds/djrXSaFJAjH3a62ON/openapi.json