LINE Email Scraper

LINE Email Scraper

LINE Email Scraper for Japan, Taiwan and Thailand Contact Discovery

The LINE Email Scraper is an Apify Actor that collects publicly indexed contact emails from LINE (line.me and lin.ee) and returns them as a structured dataset. LINE is the dominant messenger in Japan, Taiwan and Thailand, and its Official Accounts are how a great many Asian businesses take enquiries.

Read this first: LINE exposes very few indexable public profile pages, and most of what Google has indexed is Official Account or sticker pages. Result volume from the LINE Email Scraper is therefore low compared with an open network like Instagram or Facebook. That is a property of LINE, not a fault in the Actor, and we would rather you know it before you run it.

With that stated plainly, the LINE Email Scraper does a narrow job well. It builds Google queries with site:line.me OR site:lin.ee, parses the result blocks and extracts the addresses businesses publish on their LINE landing pages.

You supply keywords, an optional location and the email domains you care about. You get account names, profile URLs, snippets and normalised, deduplicated emails.

Who this LINE email extractor is for

Teams doing outreach in Japan, Taiwan and Thailand who already accept that LINE is a thin channel and want whatever is there. Agencies mapping which local businesses run a LINE Official Account. Researchers studying Asian messenger commerce.

If you need volume, treat the LINE Email Scraper as a supplement to a broader campaign rather than its main source.

Key Features of the LINE Email Scraper

Feature	What it means in practice
Google-based contact discovery	The LINE Email Scraper reads publicly indexed line.me and lin.ee results — no login, no cookies, no browser
Dual-domain targeting	Both the main LINE domain and the lin.ee short-link domain are searched in one query
Query expansion	Each keyword runs as a base query, a quoted query, an intitle: query and one variant per modifier
Domain-filtered extraction	Only emails on your customDomains list are kept, so you can target @yahoo.co.jp or @gmail.com
Global deduplication	Every address is deduplicated across all queries and pages — important when yield is low and duplicates hurt
Email normalisation	Handles name [at] domain [dot] com, name (at) domain, name @ domain.com, zero-width characters and the full-width ＠ used in Japanese text
Junk filter	Rejects placeholders such as email@, yourname@, test@, xxx@ and single-character locals
Boundary-correct matching	@gmail.com will not match inside @gmail.company or @gmail.com.br
Soft-wrap repair	Drops a hit that is only the tail of another address in the same result block
Concurrency control	An asyncio worker pool runs several queries in parallel with a shared stop signal
Retry logic	Up to 3 attempts per page with exponential backoff and a fresh proxy session per request
Block detection	CAPTCHA, "unusual traffic" and consent pages are detected and retried, not treated as empty
Resumable state	Progress is checkpointed in the key-value store and survives PERSIST_STATE, MIGRATING and ABORTING events
Fallback parser	If Google's markup changes, the crawler degrades to "emails without account details" rather than "no results"
Structured output	Fourteen fields per row, exportable to CSV, JSON or Excel

The full-width ＠ handling matters here. Japanese and Thai pages frequently use full-width punctuation, and a naive regex misses those addresses entirely.

How the LINE Email Scraper Works

1. Read input. Keywords, location, email domains and limits are validated.
2. Build queries. The LINE Email Scraper composes searches such as site:line.me OR site:lin.ee カフェ お問い合わせ "@gmail.com".
3. Fetch search results. Pages are requested asynchronously through the Apify GOOGLE_SERP proxy using aiohttp.
4. Parse structurally. The parser locates each <h3> title, then the smallest surrounding block — it does not rely on Google's CSS class names.
5. Extract emails. A domain-filtered regex pulls addresses from the block text, including obfuscated and full-width forms.
6. Deduplicate and store. Each unique lead is pushed to the Apify dataset immediately.

Base queries run first, so the best matches arrive early. Blocked or failed queries are re-queued once at the end of the run.

The LINE Email Scraper never opens the LINE app or website. There is no browser, no JavaScript rendering, no authentication and no messenger access.

What Data Does It Extract?

Each row pairs one email with the account metadata Google printed beside it. On LINE that is usually an Official Account name, a shop title, or a sticker or theme creator name.

username and profileUrl are populated when Google exposes a LINE handle — typically the @-prefixed Official Account ID. Where Google shows only a display name, you still get accountName, fullName, the snippet and the email.

Because LINE landing pages are short, snippets are short too. That makes possiblyTruncated more relevant on this platform than on most others, so check it.

In short, the LINE Email Scraper returns a contact, an identity and the evidence behind both: the address, the account it belongs to and the snippet it came from.

Input Fields and Configuration

Field	Type	Default	Meaning
keywords	array (required)	["shop", "business"]	Search terms — niche, job title or industry
location	string	""	Optional location phrase added to every query
customDomains	array	["@gmail.com","@yahoo.com"]	Only emails on these domains are kept; the @ is optional
maxEmails	integer 1–10000	20	Stop after this many unique emails
countryCode	string	""	Two-letter country for the search proxy (US, GB, DE...)
expandQueries	boolean	true	Search each keyword × domain pair in several phrasings
queryModifiers	array	["email","contact","business","inquiry"]	Extra words combined with each keyword when expansion is on
maxPagesPerQuery	integer 1–50	30	Pagination cap per query
maxConcurrency	integer 1–20	5	Parallel queries

Using countryCode with the LINE Email Scraper

countryCode is the most valuable single setting on this Actor. LINE's indexed footprint is split across three quite separate national markets, and a default search will not cover all of them.

Set JP for Japan, TW for Taiwan and TH for Thailand. Each returns a materially different result set, and running all three is the practical way to raise the LINE Email Scraper's low base yield.

Because deduplication is per run, merging the three exports and dropping duplicates in your CRM is straightforward.

Choosing the right email domains

The defaults @gmail.com and @yahoo.com are reasonable starting points, but @yahoo.co.jp is the one most people forget — it is very common on Japanese business pages.

Also try @icloud.com, @hotmail.com, @outlook.jp and, for Taiwan, @gmail.com plus company domains. The LINE Email Scraper accepts any domain list, with or without the leading @.

Every address the LINE Email Scraper keeps is checked against your list with boundary-correct matching, so a near-miss domain never sneaks into the dataset.

Choosing keywords

Keywords are placed into the Google query verbatim, so Japanese, Traditional Chinese and Thai all work. カフェ, 美容室, 不動產, ร้านค้า and นวด are valid inputs.

Replacing the default modifiers with local terms helps: お問い合わせ and 連絡先 for Japan, 聯絡 and 合作 for Taiwan, ติดต่อ for Thailand.

Output Schema and Dataset Fields

Field	Meaning
network	Platform name
keyword	The keyword that produced the lead
query	The exact Google query used
title	Raw result title
accountName	Account label Google prints (handle or display name)
fullName	Display name parsed from a profile-style title; empty for post captions
username	URL-safe handle when LINE exposes one; otherwise null
profileUrl	Canonical account URL when a handle is known; otherwise empty
url	Direct platform link when exposed, else the profile URL
description	Bio or page snippet, cleaned of labels and counters
email	Lower-cased email address
emailDomain	The matched domain, e.g. @yahoo.co.jp
possiblyTruncated	true when Google's snippet ellipsis touched the email — verify before sending
foundAt	ISO 8601 UTC timestamp

query and keyword on every row make the output auditable, which is especially useful on a low-yield platform: you can see precisely which phrasings are producing anything at all.

How to Use the LINE Email Scraper

1. Open the LINE Email Scraper on Apify and click Try for free.
2. Enter two or three specific keywords, ideally in the local language.
3. Add @yahoo.co.jp and any local providers to customDomains.
4. Set countryCode to JP, TW or TH — and plan to run all three.
5. Set maxEmails modestly at first; LINE will not fill a large target quickly.
6. Run it, then export the dataset as CSV, JSON or Excel.

Leave maxPagesPerQuery and maxConcurrency at their defaults for a first pass. Raising concurrency will not create pages that Google never indexed.

The LINE Email Scraper is callable from the Apify API and SDK clients, so you can schedule small recurring sweeps rather than one large disappointing run.

Use Cases for the LINE Email Scraper

Use case	How the LINE Email Scraper helps
Local business prospecting in Japan	Find shops and salons whose LINE Official Account page lists an enquiry email
Taiwan SME outreach	Surface Traditional Chinese business pages with a 聯絡 address
Thailand commerce research	Locate Thai retail and service accounts using LINE as a storefront
Sticker and theme creator outreach	Reach creators whose LINE Store pages carry a contact address
Agency market mapping	Measure which local categories actually maintain a LINE presence
Cross-channel enrichment	Match a LINE Official Account to a brand you already track elsewhere
Partnership sourcing	Identify Asian businesses open to messenger-based collaborations
CRM enrichment	Add public LINE contact emails to records you already hold

Because LINE yield is low, most teams use it alongside broader sources. The Instagram Email Scraper and Facebook Email Scraper cover the same Japanese and Thai businesses with far more indexed pages.

For a full East Asia messenger sweep, run the LINE Email Scraper next to the KakaoTalk Email Scraper for Korea and the WeChat Email Scraper for China. All three share the same input schema.

Why Use This LINE Email Scraper

Because when a LINE contact exists in Google's index, you want it found and normalised properly rather than missed.

The LINE Email Scraper is configured specifically for the platform: both line.me and lin.ee are searched, the profile template matches LINE's R/ti/p/ form, and the modifiers include inquiry, which mirrors how Asian business pages phrase contact lines.

Parsing is structural rather than cosmetic, so a Google layout change degrades quality instead of breaking the run. Full-width and obfuscated addresses are normalised before matching.

And the Actor is honest about a thin platform. It will not pretend a low-yield channel is a goldmine.

Limitations of the LINE Email Scraper

Read all of these before you buy. The first one is the most important.

• LINE exposes very few indexable public profile pages, and most indexed results are Official Account or sticker pages. Result volume is low. No configuration changes this. If you need thousands of leads, LINE is the wrong source.
• Only publicly indexed emails. The LINE Email Scraper finds addresses already visible in Google's index. Private data, chats and login-gated content are out of reach.
• Google caps a single query at roughly 300 results. Query expansion exists to work around that ceiling.
• Google indexes LINE far less completely than Western networks. Regional messengers are crawled thinly, and most indexed text is Japanese, Chinese or Thai.
• username and profileUrl may be empty. They are only filled when Google exposes a handle. Some rows carry accountName and fullName only — a Google limitation, not a bug.
• possiblyTruncated: true means verify. Short LINE snippets make ellipsis clipping relatively common here.
• Requires the Apify GOOGLE_SERP proxy. The Actor cannot run without Apify proxy credentials.
• Free Apify plans are capped at 100 emails per run. Paid plans are uncapped.
• No volume guarantee. Results vary with keywords, domains, country code and location.

The LINE Email Scraper is not affiliated with, endorsed by or connected to LINE or LY Corporation. Use the output in line with APPI, PDPA, GDPR and your own outreach policy.

Related Actors

Actor	What it collects
LINE Email and Phone Number Scraper	Emails and phone numbers from LINE
LINE Phone Number Scraper	Public phone numbers from LINE
Behance Email Scraper	Public contact emails from Behance
Bigo Live Email Scraper	Public contact emails from Bigo Live
Bluesky Email Scraper	Public contact emails from Bluesky
Bumble Email Scraper	Public contact emails from Bumble
Clubhouse Email Scraper	Public contact emails from Clubhouse
Dailymotion Email Scraper	Public contact emails from Dailymotion
DeviantArt Email Scraper	Public contact emails from DeviantArt
Discord Email Scraper	Public contact emails from Discord
Dribbble Email Scraper	Public contact emails from Dribbble
Facebook Email Scraper	Public contact emails from Facebook
Goodreads Email Scraper	Public contact emails from Goodreads
Hinge Email Scraper	Public contact emails from Hinge
Instagram Email Scraper	Public contact emails from Instagram
KakaoTalk Email Scraper	Public contact emails from KakaoTalk
Kick Email Scraper	Public contact emails from Kick
Lemon8 Email Scraper	Public contact emails from Lemon8
Likee Email Scraper	Public contact emails from Likee
LinkedIn Email Scraper	Public contact emails from LinkedIn
Mastodon Email Scraper	Public contact emails from Mastodon
Medium Email Scraper	Public contact emails from Medium
Mixcloud Email Scraper	Public contact emails from Mixcloud
Patreon Email Scraper	Public contact emails from Patreon
Pinterest Email Scraper	Public contact emails from Pinterest
Quora Email Scraper	Public contact emails from Quora
Reddit Email Scraper	Public contact emails from Reddit
Rumble Email Scraper	Public contact emails from Rumble
Snapchat Email Scraper	Public contact emails from Snapchat
SoundCloud Email Scraper	Public contact emails from SoundCloud
Substack Email Scraper	Public contact emails from Substack
Telegram Email Scraper	Public contact emails from Telegram
Threads Email Scraper	Public contact emails from Threads
TikTok Email Scraper	Public contact emails from TikTok
Tinder Email Scraper	Public contact emails from Tinder
Tumblr Email Scraper	Public contact emails from Tumblr
Twitch Email Scraper	Public contact emails from Twitch
Vimeo Email Scraper	Public contact emails from Vimeo
VK Email Scraper	Public contact emails from VK
WeChat Email Scraper	Public contact emails from WeChat
Weibo Email Scraper	Public contact emails from Weibo
X Email Scraper	Public contact emails from X

Example Run

A realistic LINE Email Scraper input for Japanese café and salon Official Accounts:

{
  "keywords": ["カフェ", "美容室", "shop"],
  "location": "大阪",
  "customDomains": ["@gmail.com", "@yahoo.co.jp", "@icloud.com"],
  "maxEmails": 60,
  "countryCode": "JP",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "business", "inquiry"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}

One dataset item from that run:

{
  "network": "LINE",
  "keyword": "カフェ",
  "query": "site:line.me OR site:lin.ee カフェ inquiry \"@yahoo.co.jp\" \"大阪\"",
  "title": "さくらカフェ (@sakura-cafe) | LINE Official Account",
  "accountName": "@sakura-cafe",
  "fullName": "さくらカフェ",
  "username": "@sakura-cafe",
  "profileUrl": "https://line.me/R/ti/p/@sakura-cafe",
  "url": "https://line.me/R/ti/p/@sakura-cafe",
  "description": "大阪市中央区のカフェ。ご予約・お問い合わせ sakura.cafe.osaka@yahoo.co.jp",
  "email": "sakura.cafe.osaka@yahoo.co.jp",
  "emailDomain": "@yahoo.co.jp",
  "possiblyTruncated": false,
  "foundAt": "2025-03-14T09:41:22Z"
}

Every row the LINE Email Scraper writes carries all fourteen fields, so the JSON shape is stable and safe to map into a database schema.

Leads are pushed as they are found, so even a small run gives you usable data before it finishes.

LINE Email Scraper FAQ

What is the LINE Email Scraper?

An Apify Actor that extracts publicly indexed contact emails from line.me and lin.ee search results and returns them as a structured dataset.

Why does the LINE Email Scraper return so few results?

Because LINE exposes very few indexable public profile pages, and most of what Google has indexed is Official Account or sticker pages. Low volume is expected on this platform.

Can it read LINE chats or contacts?

No. The LINE Email Scraper never opens the app, never authenticates and has no access to messages, friend lists or private data.

Does it use LINE's API?

No. All data comes from publicly indexed Google search results.

Which country code should I use?

JP, TW and TH are the three markets worth running. Doing all three is the main way to increase yield.

Which email domains work best?

@gmail.com, @yahoo.co.jp, @icloud.com and @hotmail.com, plus company domains. @yahoo.co.jp is especially common in Japan.

Do Japanese, Chinese and Thai keywords work?

Yes. Keywords are placed into the Google query as written, and full-width ＠ characters in results are normalised before matching.

What does possiblyTruncated mean?

Google's snippet ellipsis may have clipped the email. LINE snippets are short, so verify these rows carefully.

Why are some username and profileUrl values empty?

Google sometimes prints only a display name with no handle. The LINE Email Scraper fills those fields when a handle is exposed and leaves them empty otherwise.

Does the LINE Email Scraper need a proxy?

Yes. It requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials.

How many emails can I collect per run?

Free Apify plans are capped at 100 emails per run and paid plans are uncapped — but on LINE the practical ceiling is what Google has indexed, which is well below either limit.

Can I run the LINE Email Scraper on a schedule?

Yes. Use Apify Schedules or the API. Small, frequent LINE Email Scraper sweeps suit a low-yield platform better than one large run.

What export formats are supported?

The LINE Email Scraper writes to a standard Apify dataset, which exports to JSON, CSV, Excel, XML and HTML.

Is the LINE Email Scraper affiliated with LINE?

No. It is an independent Apify Actor with no affiliation with or endorsement from LINE.

Leave a review

If the LINE Email Scraper saved you time, please leave a star rating and a short review on the Actor page.

Reviews are how other buyers judge whether a tool works, and they tell us which features to build next.

If something did not work, email neurodata.apify@gmail.com instead - bugs get fixed faster than they get complained about.

Support

Questions, feature requests or need a custom build? Email neurodata.apify@gmail.com and we will get back to you.