# Linktree Email Scraper (`scraperoka/linktree-email-scraper`) Actor 📩 Linktree Email Scraper extracts contact emails from Linktree pages with precision and speed. ⚡ Perfect for lead gen, outreach, and B2B research. 🔎 Save time, find verified emails, and grow your pipeline. - **URL**: https://apify.com/scraperoka/linktree-email-scraper.md - **Developed by:** [Scraperoka](https://apify.com/scraperoka) (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 $0.01 / 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 🚀 Manually visiting hundreds of Linktree profiles to collect emails wastes hours you don’t have. **Linktree Email Scraper** automatically extracts email addresses related to your keywords from publicly available Linktree bios—ideal for marketers, recruiters, and growth teams. Use Linktree Email Scraper to build a **Linktree email scraper** lead list, or a **Linktree subscriber email extractor** dataset, at scale—often thousands of records in a single run. --- ### What You Get: Sample Output Here’s a sample record from a single run: ```json { "network": "Linktree.com", "keyword": "fashion", "title": "Fashion & Style Studio", "description": "Brand updates and styling tips. Contact us at hello@gmail.com", "url": "https://example.com/some-linktree-link", "email": "hello@gmail.com" } ```` | Field | Type | What It Tells You | |---|---|---| | `network` | string | Confirms the source network as `Linktree.com` for easier reporting | | `keyword` | string | Which of your input keywords this email was found under | | `title` | string | The page/result title associated with the email (useful for context) | | `description` | string | The text content where the email was detected (helps with verification) | | `url` | string | The associated link where the result was found | | `email` | string | The extracted email address that matches your `customDomains` filtering | | `status` | — | Not present in the pushed dataset rows; results are written immediately as records | Export your dataset as JSON, CSV, or Excel — straight from the Apify dashboard. *** ### Why Linktree Email Scraper? There are a lot of ways to pull data from Linktree—here’s what sets **Linktree Email Scraper** apart. #### Keyword-led lead discovery **Linktree Email Scraper** finds emails from Linktree bios and posts related to your provided keywords. This makes the output feel targeted, not random, which is perfect for **Linktree lead generation tool** workflows. #### Domain filtering for cleaner outreach lists With `customDomains`, you can focus on specific email domains (for example, `@gmail.com`). This is a practical way to run a **Linktree contact email scraper** with less noise. #### Resilient scraping for larger batches The actor supports two scraping engines (`engine`): **Cost Effective (New)** and **Legacy**. It includes resilience logic so runs keep moving even when some pages don’t return results reliably—helpful for **automated Linktree email scraper** use cases. #### Controlled collection size (cost + time friendly) Use `maxEmails` to stop the run once you hit your desired volume. This helps you balance results vs. runtime—especially when doing **Linktree email harvesting** at scale. *** ### Configuring Your Run Drop this into your `input.json` to get started: ```json { "keywords": ["fashion", "stylist"], "location": "Germany", "platform": "Linktree", "customDomains": ["@gmail.com", "@outlook.com"], "maxEmails": 50, "engine": "legacy", "proxyConfiguration": {} } ``` | Parameter | Required | What It Does | |---|---:|---| | `keywords` | ✅ | A list of keywords to search for (drives what kinds of Linktree bios/posts are targeted). | | `location` | ⬜ | Location to filter search results (leave empty for no location filtering). | | `platform` | ⬜ | Select platform (only `Linktree` is available). | | `customDomains` | ⬜ | List of custom email domains to focus results on (for example `@gmail.com`). | | `maxEmails` | ⬜ | Maximum number of emails to collect; the scraper stops once this limit is reached. | | `engine` | ⬜ | Choose scraping engine: `cost-effective` (Cost Effective (New)) or `legacy` (Legacy). | | `proxyConfiguration` | ⬜ | Configure proxies for this Actor run. | *** ### Core Capabilities #### Keyword-based email extraction This **Linktree Email Scraper** uses your input `keywords` to target Linktree bios and posts that are related to those terms. It then extracts email addresses that match your domain filters, helping you build a more relevant **Linktree email list building** dataset. #### Custom email-domain targeting By using `customDomains`, you can restrict extraction to the domains you care about. That makes the output more usable for outreach lists and reduces irrelevant results for your **Linktree marketing email list**. #### Pagination with practical stop conditions The actor collects results until either pagination ends or `maxEmails` is reached. This makes it easy to run quick tests or larger jobs without guessing how long the run will take. #### Two engine options for reliability vs. cost The `engine` input lets you select between `cost-effective` and `legacy` depending on your needs. Choose `cost-effective` for faster/cheaper scraping behavior, or `legacy` if you prefer the alternative approach that can be more reliable in some scenarios. #### Structured dataset records, written as you go Each discovered email is pushed as a dataset record containing `network`, `keyword`, `title`, `description`, `url`, and `email`. That means you can start exporting immediately after the run completes—no post-processing required to get started. *** ### Who Gets the Most Out of This Here’s how different teams put **Linktree Email Scraper** to work: **Growth teams and marketers** use it to turn Linktree audiences into a focused prospect list by running **scrape Linktree emails** with keyword and domain filters, then exporting directly into their CRM or outreach tooling. **Sales development reps** use this as a **find emails from Linktree** lead generation tool: provide industry-related `keywords`, narrow with `customDomains`, collect a capped number with `maxEmails`, and move faster from prospecting to first-touch. **Recruiters and talent sourcers** use **Linktree email extraction software** to identify contact emails tied to creator bios and contact mentions—especially when the target niche has Linktree-heavy presence. **Data analysts and researchers** treat Linktree Email Scraper as a repeatable dataset source, capturing consistent fields like `keyword`, `title`, `description`, `url`, and `email` for downstream analysis and enrichment. **Automation and integration specialists** integrate the actor run results into their pipelines via Apify’s dataset export and API-driven workflows, enabling scheduled runs for ongoing lead list refreshes. *** ### Step-by-Step: How to Use It No coding needed. Here's how to run **Linktree Email Scraper** from start to finish: 1. **Open the actor on Apify** — go to [console.apify.com](https://console.apify.com) and find **Linktree Email Scraper**. 2. **Enter your inputs** — add your `keywords` (required), optionally set `customDomains`, `location`, and `maxEmails`. 3. **Configure proxy settings** — if you want proxy support for your run, set `proxyConfiguration`. 4. **Hit Run and watch the live log** — keep an eye on progress to confirm it’s collecting results. 5. **View results in the dataset tab** — each record includes `network`, `keyword`, `title`, `description`, `url`, and `email`. 6. **Export as JSON, CSV, or Excel** — download from the dataset tab once the run finishes. The whole process takes under 5 minutes to set up. *** ### Integrations & Export Options Once your data is collected, **Linktree Email Scraper** plugs directly into your existing workflow. You can export your results from the Apify dataset tab in **JSON**, **CSV**, or **Excel**. This makes it easy to move your **Linktree subscriber email extractor** output into spreadsheets, CRM imports, or lead management tools. You can also connect the actor run to automations using Apify’s capabilities like API access, webhooks, no-code tools such as **Zapier / Make**, and scheduled runs—see Apify documentation for full setup details: https://apify.com/docs/api *** ### Pricing & Free Trial **Linktree Email Scraper** runs on the Apify platform, which offers a **free tier** — no credit card required to get started. You’ll be able to run several tests with platform credits, which is great for validating your **Linktree email scraper** keyword and domain strategy. After that, pricing is typically pay-as-you-go based on Apify platform usage (compute units). For the most up-to-date plan details and limits, check the Apify pricing page on apify.com. Start for free at [apify.com](https://apify.com) and scale when you're ready. *** ### Reliability & Performance | What We Handle | How | |---|---| | Rate limits and access friction | Built-in engine options and resilience logic to keep runs productive | | Proxy support | Supports proxy configuration for more reliable scraping | | Empty/low-result pages | Includes fallback behavior to continue collecting when possible | | Large jobs | Works with bulk inputs; use `maxEmails` to control how much data is collected | | Immediate dataset output | Records are pushed to your dataset as soon as emails are found | Limitations: The actor collects emails from **publicly available sources** and focuses on emails found in Linktree bios/posts related to your keywords and filtered by `customDomains`. Private, login-gated, or non-public contact information is not accessible. For enterprise-scale runs, contact us to discuss custom configurations. *** ### Frequently Asked Questions #### Is there a free plan or trial? Yes—Apify offers a free tier to help you run **Linktree Email Scraper** tests without committing upfront. Use a small `maxEmails` and a couple of `keywords` first to confirm your targeting. #### Do I need to log in to Linktree to use this? No, this actor is designed to work with publicly available content. You provide `keywords` and optional filters like `customDomains`, and the actor extracts matching emails from publicly accessible Linktree bios/posts. #### How accurate is the data? The actor extracts email addresses it detects from Linktree content and pushes them with the surrounding context (`description`, `title`, `url`). Accuracy depends on what the Linktree profile actually publishes and how closely your `keywords` and `customDomains` match. #### How many results can I get per run? You control the volume with `maxEmails`. The scraper will stop once it reaches that maximum number, so you can cap **scrape Linktree emails** runs for testing or larger list builds. #### How often is the data updated / how fresh is it? Freshness depends on when you run the actor—each run scrapes public data at runtime. If you need regularly updated **Linktree email list building**, schedule recurring runs and compare new exports. #### Is this legal? Does it comply with GDPR / CCPA? You should treat this as a tool for collecting from publicly available data and handle compliance yourself. It’s your responsibility to follow GDPR, CCPA, and any applicable platform policies when storing or using the results. #### Can I export results to Google Sheets or Excel? Yes. You can export from the Apify dataset tab as **JSON**, **CSV**, or **Excel**, which works well for Google Sheets imports and other spreadsheet tools. #### Can I run this on a schedule automatically? Yes—Apify supports scheduled runs. This is ideal for keeping your **Linktree contact email scraper** dataset up to date automatically. #### Can I access this via API? Yes. You can programmatically access actor runs and results using Apify’s API. See: https://apify.com/docs/api #### What happens if the actor hits an error? If the run encounters issues, it will continue collecting what it can and stop when limits are reached (like `maxEmails`) or when pagination ends. Results are written to the dataset as they’re found, so partial data is still captured. *** ### Need Help or Have a Request? Got a question about **Linktree Email Scraper** or want a new feature added? Reach out at . Share your keyword strategy, desired output volume, or an integration idea (like webhook on completion or pushing results to a workflow), and we’ll help where we can. *** ### Disclaimer & Responsible Use *Linktree Email Scraper is the fastest, most reliable way to build keyword-led Linktree email lists—start your free run today.* This actor collects **publicly available data** from Linktree bios and posts related to your provided keywords. It does not access private accounts, login-gated content, or password-protected pages. You’re responsible for complying with GDPR, CCPA, applicable platform Terms of Service, and all relevant laws when using or storing the extracted data. For data removal requests, contact . Use responsibly, ethically, and only for lawful purposes. # 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("scraperoka/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("scraperoka/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 scraperoka/linktree-email-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=scraperoka/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 with precision and speed. ⚡ Perfect for lead gen, outreach, and B2B research. 🔎 Save time, find verified emails, and grow your pipeline.", "version": "0.0", "x-build-id": "lUM3xVtq5Vl3WAiVM" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/scraperoka~linktree-email-scraper/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-scraperoka-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/scraperoka~linktree-email-scraper/runs": { "post": { "operationId": "runs-sync-scraperoka-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/scraperoka~linktree-email-scraper/run-sync": { "post": { "operationId": "run-sync-scraperoka-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 } } } } } } } } } } ```