# Linktree Email Scraper (`solid-scraper/linktree-email-scraper`) Actor 📧 Linktree Email Scraper extracts contact emails from Linktree pages fast and accurately. ✅ Great for lead gen, outreach, agencies, and sales teams—save time, build targeted lists, and boost conversions. - **URL**: https://apify.com/solid-scraper/linktree-email-scraper.md - **Developed by:** [SolidScraper](https://apify.com/solid-scraper) (community) - **Categories:** Lead generation, Automation, Developer tools - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $2.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/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are a software tools running on the Apify platform, for all kinds of web data extraction and automation use cases. 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. In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js.md): ```bash npm install apify-client ``` In Python projects, use official [Python client library](https://docs.apify.com/api/client/python.md): ```bash pip install apify-client ``` In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md): ````bash # MacOS / Linux curl -fsSL https://apify.com/install-cli.sh | bash # Windows irm https://apify.com/install-cli.ps1 | iex ```bash In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp.md). If your project is in a different language, use 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 ### Linktree Email Scraper 🔍 **Linktree Email Scraper** is an Apify actor that scrapes emails from Linktree profiles using your chosen keywords and email-domain filters. Whether you’re using a **Linktree email scraper** for lead generation, outreach list building, or research, this tool helps you extract emails from publicly available Linktree content and turn them into structured data—saving you hours of manual work. --- ### Why choose Linktree Email Scraper? | Feature | Benefit | | --- | --- | | ✅ **Keyword-based discovery** | Lets you search for Linktree audience email leads using your terms and context | | ✅ **Custom email-domain targeting** | Filters results to email domains you care about (for example, `@gmail.com`) | | ✅ **Proxy support for more reliable runs** | Helps keep scraping stable with built-in proxy configuration | | ✅ **Engine choice (cost-effective vs legacy)** | Pick the engine that fits your priorities for cost or reliability | | ✅ **Structured dataset output** | Produces consistent JSON rows with URL, keyword, email, and page text for analysis | | ✅ **Scales with run-time controls** | Use `maxEmails` to control how many emails to collect and how long the run may take | --- ### Key features - 🔎 **Accurate email extraction from Linktree bios**: Collects email addresses found in Linktree bio text tied to your keyword intent - 🧩 **Flexible input for lead generation**: Combine `keywords`, optional `location`, and `customDomains` to target the right audience - 🛡️ **Reliability-focused scraping support**: Includes resilience through proxy configuration and run robustness - 🔄 **Controlled collection volume**: Stop automatically once `maxEmails` is reached to avoid unnecessary scraping time - 💾 **Real-time data saving**: Each found email is pushed immediately to the output dataset - 📊 **Clear result context for analysts**: Every row includes the matched `keyword`, page `title`, `description`, and the source `url` - 🌐 **Linktree-first extraction**: Built specifically for Linktree email harvesting from publicly available Linktree profiles --- ### Input Provide input via an `input.json` file. Example structure: ```json { "keywords": ["fashion", "beauty"], "location": "", "platform": "Linktree", "customDomains": ["@gmail.com"], "maxEmails": 20, "engine": "legacy", "proxyConfiguration": {} } ```` #### Input Fields | Field | Required | Description | | --- | --- | --- | | `keywords` | ✅ Yes | A list of keywords to search for. The scraper uses these to find Linktree bios and posts related to your topic (this is the core input for any automated Linktree contact email finder workflow). | | `location` | ❌ No | Location to filter search results. Leave it empty to search without location constraints. | | `platform` | ❌ No | Select platform. This actor supports `Linktree` and defaults to `Linktree`. | | `customDomains` | ❌ No | List of custom email domains to target (for example `@gmail.com`). The actor uses these domains to filter extracted emails. | | `maxEmails` | ❌ No | Maximum number of emails to collect. The actor will stop once this limit is reached. Higher values may increase runtime (and still don’t guarantee reaching the exact number). | | `engine` | ❌ No | Choose the scraping engine. `cost-effective` uses residential proxies with async requests for faster, cheaper scraping. `legacy` uses a more traditional approach and is described as more reliable but slower and more expensive. | | `proxyConfiguration` | ❌ No | Configure proxies for this Actor. Use this if you want to control proxy behavior explicitly. | *** ### Output After execution, the actor saves each found email as a JSON row in the dataset. ```json [ { "network": "Linktree.com", "keyword": "fashion", "title": "No title", "description": "No data", "url": "https://linktr.ee/example", "email": "name@gmail.com" } ] ``` #### Output Fields | Field | Type | Description | | --- | --- | --- | | `network` | string | The network/source label used by the actor (always `Linktree.com`). | | `keyword` | string | The keyword from your input that led to the extracted result. | | `title` | string | Title text associated with the scraped result. | | `description` | string | Text snippet/description content used for email extraction. | | `url` | string | The source URL for the scraped result. | | `email` | string | The extracted email address that matched your `customDomains` filter. | Note: If you set `maxEmails`, the actor will stop once the limit is reached. *** ### How to use Linktree Email Scraper (via Apify Console) 1. **Open Apify Console**\ Log in at https://console.apify.com and open the Actors tab. 2. **Find Linktree Email Scraper**\ Search for **Linktree Email Scraper** and open the actor page. 3. **Enter your INPUT settings**\ In the INPUT section, use the built-in form: - Add your `keywords` (required). - Optionally set `location`. - Add one or more `customDomains` (recommended for targeted lead generation email lists). - Set `maxEmails` to control how many emails to collect. - Choose `engine` (`cost-effective` or `legacy`). - Configure `proxyConfiguration` if you want explicit proxy control. 4. **Choose your Run Options (if needed)**\ For large searches or higher email limits, allow more time. (The actor input description notes the default timeout is 3600s / 1 hr, and that increasing timeout can help.) 5. **Click Run ▶️**\ Start the run and monitor the logs. You’ll see progress as the actor finds and pushes extracted emails in real time. 6. **Review results in OUTPUT**\ Open the OUTPUT dataset to view the JSON rows with `keyword`, `url`, and `email`. 7. **Export to JSON/CSV**\ Use the dataset export options in Apify Console to download the results for analysis or CRM import.\ No coding required—get accurate Linktree Email Scraper results in minutes. *** ### Advanced features & SEO optimization - 🔧 **Engine choice for Linktree email extraction**: The Linktree email scraper supports both `cost-effective` and `legacy` engines so you can balance speed vs reliability depending on your use case (e.g. Linktree email list building vs deeper scraping). - 🧠 **Bio-focused email harvesting**: The scraper is designed to find emails from Linktree bios and posts related to your keywords—ideal for a Linktree bio email scraper workflow. - 🎯 **Better targeting with keyword + domain filters**: Use specific `keywords` and `customDomains` (like `@gmail.com`) to narrow results for a more useful Linktree contact email finder output. - ⏳ **Runtime awareness for large jobs**: Large searches or high email limits may take longer; tune expectations (and timeout via Run Options) for automated Linktree email scraper runs. *** ### Best use cases - 📈 **Marketing teams building outreach lists**: Collect emails from Linktree Email Scraper outputs to power faster prospecting and campaigns - 🎓 **Researchers studying creator audiences**: Analyze which keywords and bio styles correlate with published contact emails - 👩‍💼 **Recruiters sourcing talent contact**: Use Linktree email harvesting software results to find publicly listed contact addresses - 🧠 **Content strategy teams validating niches**: Test keyword sets to see where contact information appears most frequently - 🛍️ **E-commerce brands finding influencer leads**: Gather Linktree audience email leads to reach creators in specific categories - 💻 **Data analysts enriching CRM pipelines**: Join the dataset fields (`keyword`, `url`, `title`, `description`, `email`) with internal datasets for downstream reporting - 🧾 **Sales ops automations**: Feed scraped Linktree email extraction rows into spreadsheets or automation pipelines for consistent lead processing *** ### Technical specifications - **Supported Input Formats** - ✅ `keywords` as an array of strings - ✅ Optional `location` as a string - ✅ `customDomains` as an array (e.g. `@gmail.com`) - ✅ `proxyConfiguration` as an object - **Proxy Support** - ✅ Yes—use `proxyConfiguration` to configure proxies for the actor - **Retry Mechanism** - ✅ The actor includes resilience through retries/fallback behavior (especially helpful when results are sparse or blocked) - **Dataset Structure** - ✅ JSON rows with: `network`, `keyword`, `title`, `description`, `url`, `email` - **Rate Limits & Performance** - ✅ Runtime depends on search size and `maxEmails` (large searches and higher limits can take longer) - ✅ The actor stops once `maxEmails` is reached (if provided) - **Limitations** - ❌ Results can be lower than expected depending on what is publicly available on Linktree bios/posts - ❌ Private/restricted or non-public contact info is not available for extraction *** ### FAQ #### What does Linktree Email Scraper extract emails from? ✅ It extracts email addresses that appear in Linktree bios and posts that are related to your provided `keywords`. This makes it useful as an automated Linktree email extractor for audience lead generation. #### How do `customDomains` help my Linktree email list? ✅ `customDomains` lets you restrict extracted emails to specific domains (for example, `@gmail.com`). This means the actor will only keep emails that match your domain filters, which helps you build cleaner outputs faster. #### Why are results low when I run the Linktree scraper? ❌ If results seem low, the actor’s input guidance suggests re-running with broader keywords and more related terms, or adding more domains. Availability varies depending on what creators and profiles publicly display. #### Is `keywords` required? ✅ Yes. `keywords` is the only required input field in the schema. #### Can I control how many emails I collect? ✅ Yes. Use `maxEmails` to set a maximum collection target. The scraper stops once the limit is reached (but higher values don’t guarantee you’ll reach that exact number). #### Do I need code to run Linktree Email Scraper? ✅ No. You can run it directly in Apify Console by filling in the input form (keywords, domains, optional location, and engine choice). #### Does this actor support proxies? ✅ Yes. You can configure proxies using `proxyConfiguration`, and you can also choose between `engine` options (`cost-effective` or `legacy`) based on how you want the run to behave. #### How can I request a feature or custom enhancement? 💡 You can share a feature request by contacting . *** ### Support & feature requests If you’re using Linktree Email Scraper for Linktree email scraper lead generation and want improvements, we’d love to hear from you. 💬 - 💡 **Feature Requests**: Ideas like CSV export convenience, expanding output context, or additional filtering options are welcome. - 📧 **Contact**: For help or feature requests, email . Your feedback helps shape the roadmap for this Linktree scraper and keeps the Linktree email harvesting software workflow more useful over time. *** - *Get the most comprehensive Linktree Email Scraper workflow for extracting Linktree contact emails—engineered for practical lead generation at scale.* \* ### Disclaimer **This tool only accesses publicly accessible sources.** It does not access private profiles, authenticated data, or password-protected pages. It’s your responsibility to comply with applicable laws (including GDPR/CCPA where relevant), spam regulations, and each platform’s terms of service. For data-removal requests, contact . Please use Linktree Email Scraper responsibly, ethically, and for legitimate purposes only. # Actor input Schema ## `keywords` (type: `array`): A list of keywords to search for. ## `location` (type: `string`): Location to filter search results. ## `platform` (type: `string`): Select platform. ## `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. ## `engine` (type: `string`): Choose scraping engine. 🚀 Cost Effective (New): Uses residential proxies with async requests for faster, cheaper scraping. 🔧 Legacy: Uses GOOGLE\_SERP proxy with traditional selectors - more reliable but slower and more expensive. ## `proxyConfiguration` (type: `object`): Configure proxies for this Actor. ## Actor input object example ```json { "keywords": [ "fashion" ], "location": "", "platform": "Linktree", "customDomains": [ "@gmail.com" ], "maxEmails": 20, "engine": "legacy" } ``` # 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": [ "fashion" ], "location": "", "customDomains": [ "@gmail.com" ] }; // Run the Actor and wait for it to finish const run = await client.actor("solid-scraper/linktree-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": ["fashion"], "location": "", "customDomains": ["@gmail.com"], } # Run the Actor and wait for it to finish run = client.actor("solid-scraper/linktree-email-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).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": [ "fashion" ], "location": "", "customDomains": [ "@gmail.com" ] }' | apify call solid-scraper/linktree-email-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=solid-scraper/linktree-email-scraper", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "Linktree Email Scraper", "description": "📧 Linktree Email Scraper extracts contact emails from Linktree pages fast and accurately. ✅ Great for lead gen, outreach, agencies, and sales teams—save time, build targeted lists, and boost conversions.", "version": "0.0", "x-build-id": "WZmL59le9rGZWDoib" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/solid-scraper~linktree-email-scraper/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-solid-scraper-linktree-email-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/solid-scraper~linktree-email-scraper/runs": { "post": { "operationId": "runs-sync-solid-scraper-linktree-email-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/solid-scraper~linktree-email-scraper/run-sync": { "post": { "operationId": "run-sync-solid-scraper-linktree-email-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "required": [ "keywords" ], "properties": { "keywords": { "title": "Keywords", "type": "array", "description": "A list of keywords to search for.", "default": [ "fashion" ], "items": { "type": "string" } }, "location": { "title": "Location", "type": "string", "description": "Location to filter search results.", "default": "" }, "platform": { "title": "Platform", "enum": [ "Linktree" ], "type": "string", "description": "Select platform.", "default": "Linktree" }, "customDomains": { "title": "Custom Email Domains", "type": "array", "description": "List of custom email domains", "default": [ "@gmail.com" ], "items": { "type": "string" } }, "maxEmails": { "title": "Max Emails", "minimum": 1, "maximum": 10000, "type": "integer", "description": "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.", "default": 20 }, "engine": { "title": "Engine", "enum": [ "cost-effective", "legacy" ], "type": "string", "description": "Choose scraping engine. 🚀 Cost Effective (New): Uses residential proxies with async requests for faster, cheaper scraping. 🔧 Legacy: Uses GOOGLE_SERP proxy with traditional selectors - more reliable but slower and more expensive.", "default": "legacy" }, "proxyConfiguration": { "title": "Proxy Configuration", "type": "object", "description": "Configure proxies for this Actor." } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } } } } } } } } } ```