# Line Email Scraper - Keyword Search & Domain Filter (`parse-point/line-email-scraper-lightning-fast-and-accurate`) Actor

💚 LINE Email Scraper extracts public account and business emails using keyword and location filters. 🎯 Domain restriction, decoding and duplicate skipping. 🇯🇵 Fast LINE lead generation for Japan & SEA outreach.

- **URL**: https://apify.com/parse-point/line-email-scraper-lightning-fast-and-accurate.md
- **Developed by:** [Parse Point](https://apify.com/parse-point) (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 $1.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 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

### Line Email Scraper

**Line Email Scraper** helps you collect publicly available email addresses from Line using your chosen keywords and filters. It’s built for marketers, analysts, and researchers who need a fast Line email extractor and a practical Line lead generation workflow without manual searching. With keyword-based targeting, domain filtering, and structured output, this messaging app scraper makes contact harvesting and automated data extraction far easier at scale. 🚀

### What Does Line Email Scraper Do? 🤖

Line Email Scraper scrapes publicly available data from Line and collects email addresses that match the keywords and email-domain filters you provide. During a run, it processes your keyword list, optional location filter, and custom email domains to find relevant contacts, then exports each result to your Apify dataset. This Line contact scraper is designed to support data collection for lead generation, email collection, and user data scraping while keeping the workflow simple for mid-level users. Compared with manual research, it saves time and makes large-scale social app email scraper tasks much more efficient. ✅

### What Can Line Email Scraper Extract? 📊

This actor captures a small but useful set of lead data fields from publicly available Line pages. Each record is focused on contact discovery and profile context, making it useful for LINE data extraction, LINE user email extraction, and broader social media scraping workflows.

| Data Type | Field Name | Description |
|---|---|---|
| Discovery | `keyword` | The keyword that surfaced the result |
| Identity | `title` | The title or profile headline |
| Context | `description` | The profile description or visible text associated with the result |
| Navigation | `url` | Direct link to the source page |
| Contact | `email` | The extracted email address |

#### Key Features of Line Email Scraper ⚡

- ✅ **Keyword-Driven Search:** Use your own keywords to focus on the most relevant Line profiles and improve contact harvesting results.
- 🌍 **Location Filter:** Narrow results by location when you want more targeted lead generation.
- 📧 **Custom Domain Filtering:** Add domains like `@gmail.com` or `@yahoo.com` to improve email collection precision.
- 🔄 **Built-In Proxy Support:** Designed for reliable public web data scraping with built-in proxy support.
- 📊 **Structured JSON Output:** Each result is saved in a clean dataset format that’s easy to export and analyze.
- 💾 **Real-Time Saving:** Results are pushed during the run, so you don’t lose progress if the job stops early.
- ⚙️ **Configurable Limits:** Control how many emails you want to collect with `maxEmails`.

### How to Use Line Email Scraper 🚀

1. **Open the Actor** — Find Line Email Scraper in the Apify Store.
2. **Go to Input** — Open the Input tab in the Apify Console.
3. **Add Keywords** — Enter one or more search terms such as job titles, roles, or industries.
4. **Set Optional Filters** — Add a location and custom email domains if needed.
5. **Choose Your Limit** — Set `maxEmails` to control the run size and cost.
6. **Start the Run** — Launch the actor and monitor progress in the logs.
7. **Download Results** — Export your dataset in JSON or CSV once the run finishes.

No coding required. ✨

### Line Email Scraper Output Format 📦

The actor saves results to an Apify dataset in structured JSON format. Below is a realistic example using the exact fields returned by the dataset output schema.

#### Input Example

```json
{
  "keywords": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20
}
```

| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| `keywords` | Array | ✅ Yes | `["manager", "founder"]` | One or more keywords or queries used to find relevant Line profiles. |
| `location` | String | No | `""` | Optional location filter to narrow the results. |
| `customDomains` | Array | No | `["@gmail.com", "@yahoo.com"]` | Email domains to look for in public data. |
| `maxEmails` | Integer | No | `20` | Maximum number of emails to collect in one run. |

#### Output Example

```json
[
  {
    "keyword": "manager",
    "title": "Jane Smith",
    "description": "Marketing manager with experience in digital campaigns and partnerships.",
    "url": "https://line.me/ti/p/8aBcD123Ef",
    "email": "janesmith@gmail.com"
  }
]
```

| Field | Label | Format | Description |
|---|---|---|---|
| `keyword` | Keyword | text | The keyword associated with the result. |
| `title` | Title | text | The title or profile headline from the result. |
| `description` | Description | text | The visible description or text content tied to the result. |
| `url` | Url | link | Direct link to the source page. |
| `email` | Email | text | The extracted email address. |

### 🎯 Use Cases of Line Email Scraper

**B2B Lead Generation:** Build targeted contact lists from public Line data to support outreach campaigns and prospecting workflows.

**Email Marketing Campaigns:** Collect emails from relevant Line profiles for newsletters, promotions, and automated follow-ups.

**Research and Intelligence:** Use LINE profile scraper results to study niche audiences, public contact patterns, and communication trends.

**CRM Enrichment:** Add discovered emails and profile context into your CRM to improve segmentation and personalization.

**Social App Email Scraper Workflows:** Combine LINE data extraction with other public sources to expand your contact database responsibly.

### How Much Will Line Email Scraper Cost You? 💰

Line Email Scraper uses `maxEmails` to help you control the size of each run and keep costs predictable. The Apify platform charges based on usage, so setting a clear limit is the easiest way to manage spending. New users may also benefit from Apify’s free tier. If you’re running larger lead generation jobs, start with a smaller batch and increase it once you confirm the keyword and domain mix is working well. 📈

### Is It Legal to Scrape Line? ⚖️

This actor only works with publicly available data from Line, not private accounts or password-protected content. In general, scraping public web data is a common practice, but you are responsible for following Line’s terms, applicable privacy laws, and anti-spam rules in your region. Use the results for legitimate research, marketing, or outreach purposes. If you have questions or data-removal requests, contact <hello.parsepoint@gmail.com>. ✅

### Line Email Scraper Input Parameters 📋

```json
{
  "keywords": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20
}
```

| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| `keywords` | Array | ✅ Yes | `["manager", "founder"]` | A list of keywords or queries to search for. |
| `location` | String | No | `""` | Location to filter search results. |
| `customDomains` | Array | No | `["@gmail.com", "@yahoo.com"]` | List of custom email domains. |
| `maxEmails` | Integer | No | `20` | Maximum number of emails to collect. The scraper stops when this limit is reached. |

### During the Actor Run ⏱️

While the actor is running, you can watch live logs in the Apify Console and see results saved in real time. The total duration depends on your keyword list, domain filters, and `maxEmails` setting. If results are lower than expected, try broader keywords, additional domain options, or removing the location filter for wider coverage. This is especially useful for messaging app scraper and automated data extraction workflows. ⚙️

### Final Note ✉️

Start extracting Line emails in minutes with Line Email Scraper — no code, no setup, just scalable results. If you need help or want to share feedback, reach out at <hello.parsepoint@gmail.com>. 🚀

### FAQ — Line Email Scraper ❓

#### How does Line Email Scraper find emails?

Line Email Scraper uses your keywords and email-domain filters to find relevant contacts in publicly available Line data. It extracts email addresses that appear in the collected public content and saves them in a structured dataset.

#### What types of Line profiles can I scrape?

You can scrape public Line profiles and public result pages that contain visible email addresses or contact details. Private or restricted content is not covered.

#### Why use a Line contact scraper for lead generation?

A Line contact scraper helps you turn manual public-profile research into a repeatable lead generation process. It’s useful when you need contact harvesting at scale instead of checking profiles one by one.

#### How much does Line Email Scraper cost to use?

Your cost depends on how much data you collect and how long the run takes. The easiest way to control usage is to set `maxEmails` before starting the actor.

#### How does Line Email Scraper help with email collection?

It saves time by automating public web data collection, filtering results by keyword and domain, and exporting them in a clean dataset you can use for outreach or analysis.

#### What are the limits of a social app email scraper like this?

Result volume depends on how many public profiles match your keywords and domains. Some searches return many leads, while others may be more limited if fewer public emails are available.

#### How can I improve my LINE data extraction results?

Use more specific keywords, add related terms, expand your domain list, or remove the location filter if your results are too narrow. These small changes often improve coverage.

#### Where can I get support for Line Email Scraper?

For help, feedback, or custom requests, contact <hello.parsepoint@gmail.com>.

### Run Memory

**Skip keywords already scraped in a previous run** - the actor keeps a
persistent record of every keyword it finishes, in a named key-value store that
survives between runs. Turn this on and a repeat run silently drops the keywords
it has already covered, so a scheduled job over a fixed list only pays for new
ground.

A keyword is identified by the keyword *plus* the set of email domains it was
searched against, so re-running `fitness` against a new domain list is correctly
treated as new work rather than a duplicate.

**Reset keyword history** - wipe that record before the run starts, so
everything counts as new again.

**Max emails per keyword** - cap how many results any single keyword may
produce before the actor moves on to the next one. Stops one broad term from
consuming the entire run budget. `0` means no per-keyword limit.

These sit alongside the existing address-level deduplication: *Skip previous
runs* prevents re-pushing an individual mailbox, while *Skip duplicate keywords*
prevents re-running the search at all.

# Actor input Schema

## `keywords` (type: `array`):

A list of keywords or queries to search for.

## `location` (type: `string`):

Location to filter search results.

## `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.

## `decodeProtectedEmails` (type: `boolean`):

Read addresses the page hides behind Cloudflare protection or HTML entities. These are invisible to a plain text scan.

## `decodeWrittenEmails` (type: `boolean`):

Read addresses written to defeat scrapers, such as 'name \[at] example \[dot] com'.

## `decodeEncodedEmails` (type: `boolean`):

Read addresses stored base64-encoded in the page markup.

## `mergeAliasDuplicates` (type: `boolean`):

Collapse different spellings that reach the same inbox (e.g. j.o.h.n+news@gmail.com and john@gmail.com) into a single result, so you are not billed twice for one lead.

## `skipPreviousRuns` (type: `boolean`):

Do not return leads that an earlier run of this Actor already returned. Skipped leads are never charged.

## `duplicateHandling` (type: `string`):

What to do when several spellings reach the same inbox: merge them into one result, keep them apart but flag them, or keep everything as found.

## `skipDuplicateKeywords` (type: `boolean`):

Remember every keyword this actor completes and skip it next time. Ideal for a scheduled run over a fixed keyword list - you only pay for ground you have not covered. A keyword searched against a different set of email domains counts as new work, not a duplicate.

## `resetKeywordHistory` (type: `boolean`):

Clear the remembered keywords before this run starts, so everything is treated as new again. Use after changing your target list.

## `maxEmailsPerKeyword` (type: `integer`):

Stop collecting for a keyword once it has produced this many results, then move on to the next one. Keeps one broad term from consuming the whole run. Leave at 0 for no per-keyword limit.

## Actor input object example

```json
{
  "keywords": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "decodeProtectedEmails": true,
  "decodeWrittenEmails": true,
  "decodeEncodedEmails": true,
  "mergeAliasDuplicates": true,
  "skipPreviousRuns": false,
  "duplicateHandling": "merge",
  "skipDuplicateKeywords": false,
  "resetKeywordHistory": false,
  "maxEmailsPerKeyword": 0
}
```

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "manager",
        "founder"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("parse-point/line-email-scraper-lightning-fast-and-accurate").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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": [
        "manager",
        "founder",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("parse-point/line-email-scraper-lightning-fast-and-accurate").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": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ]
}' |
apify call parse-point/line-email-scraper-lightning-fast-and-accurate --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,parse-point/line-email-scraper-lightning-fast-and-accurate"
        }
    }
}

```

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 <APIFY_API_TOKEN>` 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/wezDq1uPC9ewAPeGt/builds/Ab4D0gM9k57GdR6IG/openapi.json