KakaoTalk Email Scraper

KakaoTalk Email Scraper

KakaoTalk Email Scraper for South Korean Contact Discovery

The KakaoTalk Email Scraper is an Apify Actor that collects publicly indexed contact emails from the Kakao ecosystem — pf.kakao.com, kakao.com and open.kakao.com — and returns them as a structured dataset. KakaoTalk is the default messenger in South Korea, and Kakao Channels are how many Korean businesses take enquiries.

Read this first: KakaoTalk exposes very few indexable public profile pages, so result volume is low. The KakaoTalk Email Scraper will not produce lead lists on the scale of an open network like Instagram. That is a property of the platform, not a defect in the Actor, and you should know it before you run anything.

With that said plainly, the KakaoTalk Email Scraper does a narrow job carefully. It builds Google queries with site:pf.kakao.com OR site:kakao.com OR site:open.kakao.com, parses the result blocks and extracts the addresses Korean businesses publish on their channel pages.

Give it keywords, an optional location and the email domains you want. You get channel names, profile URLs, snippets and normalised, deduplicated emails.

Who this KakaoTalk email extractor is for

Teams doing outreach into South Korea who understand Kakao is a thin public channel. Agencies mapping which Korean businesses run a Kakao Channel. Localisation and market-entry researchers. Anyone enriching a Korean prospect list from a second source.

If you need volume, use the KakaoTalk Email Scraper as a supplement rather than your primary source.

Key Features of the KakaoTalk Email Scraper

Feature	What it means in practice
Google-based contact discovery	The KakaoTalk Email Scraper reads publicly indexed Kakao results — no login, no cookies, no browser
Triple-domain targeting	pf.kakao.com channel pages, kakao.com and open.kakao.com open chats are covered 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 @naver.com or @daum.net
Global deduplication	Every address is deduplicated across all queries and pages — valuable when yield is low
Email normalisation	Handles name [at] domain [dot] com, name (at) domain, name @ domain.com, zero-width characters and the full-width ＠ used in Korean 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

Covering all three Kakao domains in one query matters on a thin platform. Every additional indexed page is worth having when the total is small.

How the KakaoTalk Email Scraper Works

1. Read input. Keywords, location, email domains and limits are validated.
2. Build queries. The KakaoTalk Email Scraper composes searches such as site:pf.kakao.com OR site:kakao.com OR site:open.kakao.com 쇼핑몰 contact "@naver.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 depend 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 strongest matches land early. Blocked or failed queries are re-queued once at the end of the run.

The KakaoTalk Email Scraper never opens the KakaoTalk app. There is no browser, no JavaScript rendering, no authentication and no messenger access whatsoever.

What Data Does It Extract?

Each row pairs one email with the account metadata Google printed beside it. On Kakao that is usually a Channel name, a shop title, or an open-chat room name.

username and profileUrl are populated when Google exposes a Kakao channel handle such as pf.kakao.com/_abcdef. Where only a Korean display name appears, you still get accountName, fullName, the snippet and the email.

Kakao channel pages are short, so snippets are short. That makes the possiblyTruncated flag more relevant here than on text-heavy platforms — check it before you send.

In short, the KakaoTalk Email Scraper returns a contact, an identity and the evidence behind both: the address, the channel 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 KakaoTalk Email Scraper

countryCode is worth setting deliberately on a single-market platform like this one. Kakao's indexed content is almost entirely Korean, and Google's result set differs by search region.

KR is the obvious first choice and usually the most productive. US is worth a second run: it surfaces bilingual Kakao Channels aimed at the Korean diaspora and at international customers.

Because deduplication happens per run, running KR and US and merging the two exports is a simple way to lift the KakaoTalk Email Scraper's low base yield.

Choosing the right email domains

The defaults @gmail.com and @yahoo.com will find some leads, but they are not where Korean businesses live. Korean accounts overwhelmingly publish @naver.com, @daum.net, @hanmail.net, @kakao.com and @nate.com addresses.

Setting customDomains to those providers is the single most effective change you can make. Add @gmail.com alongside them for startups and export-facing brands.

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

Choosing keywords

Keywords go into the Google query verbatim, so Hangul works exactly as well as English. 쇼핑몰, 카페, 학원, 공방, 헤어샵 and 문의 are all valid inputs.

Swapping the default modifiers for Korean equivalents such as 문의, 연락처, 제휴 and 이메일 gives the expansion pass a much better chance on Korean-language pages.

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 Kakao 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	Channel or page snippet, cleaned of labels and counters
email	Lower-cased email address
emailDomain	The matched domain, e.g. @naver.com
possiblyTruncated	true when Google's snippet ellipsis touched the email — verify before sending
foundAt	ISO 8601 UTC timestamp

Storing query and keyword on every row keeps the output auditable. On a low-yield platform that is genuinely useful: you can see which few phrasings are producing anything and drop the rest.

How to Use the KakaoTalk Email Scraper

1. Open the KakaoTalk Email Scraper on Apify and click Try for free.
2. Enter two or three specific keywords, ideally in Korean.
3. Replace customDomains with @naver.com, @daum.net, @hanmail.net and @kakao.com.
4. Set countryCode to KR, then repeat the run with US.
5. Keep maxEmails modest — Kakao will not fill a large target.
6. Run it, then export the dataset as CSV, JSON or Excel.

Leave maxPagesPerQuery and maxConcurrency at their defaults for a first pass. More concurrency cannot conjure pages Google never indexed.

The KakaoTalk Email Scraper is callable from the Apify API and SDK clients, so scheduling small recurring sweeps is easy.

Use Cases for the KakaoTalk Email Scraper

Use case	How the KakaoTalk Email Scraper helps
Korean SME prospecting	Find shops and studios whose Kakao Channel page lists an enquiry email
Market-entry research	Measure which Korean categories actually run a public Kakao Channel
Open-chat community outreach	Surface open.kakao.com room pages that publish an organiser contact
Beauty and K-commerce sourcing	Reach Korean brands and resellers with a public partnership address
Localisation partner discovery	Identify Korean agencies and studios open to collaboration
Cross-channel enrichment	Match a Kakao Channel to a brand you already track elsewhere
Diaspora marketing	Use a US country code run to find bilingual Korean-market channels
CRM enrichment	Add public Kakao contact emails to records you already hold

Given the low yield, most teams pair this with broader sources. The Instagram Email Scraper covers Korean brands with far more indexed pages, and the YouTube Email Scraper reaches Korean creators who publish a business address on their channel.

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

Why Use This KakaoTalk Email Scraper

Because when a Kakao contact does exist in Google's index, you want it captured, normalised and attributed properly rather than missed.

The KakaoTalk Email Scraper is configured specifically for the platform: three Kakao domains, the pf.kakao.com/{username} profile template and modifiers that mirror how Korean business pages phrase contact lines.

Parsing is structural rather than cosmetic. Because it finds the <h3> and walks outward, a Google redesign degrades results gracefully instead of ending the run with nothing.

Korean-text handling is deliberate too — full-width at signs, zero-width characters and [at] obfuscation are normalised before matching.

Above all, the KakaoTalk Email Scraper tells you the truth about a thin platform instead of overselling it.

Limitations of the KakaoTalk Email Scraper

Read all of these before buying. The first is the most important.

• KakaoTalk exposes very few indexable public profile pages, so result volume is low. No setting changes this. If you need thousands of leads, Kakao is the wrong source.
• Only publicly indexed emails. The KakaoTalk 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 Kakao far less completely than Western networks. Korean platforms are crawled thinly, much Korean discovery happens on Naver rather than Google, and nearly all indexed text is Korean.
• 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 Kakao snippets make ellipsis clipping relatively common.
• 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 KakaoTalk Email Scraper is not affiliated with, endorsed by or connected to Kakao Corp. Use the output in line with PIPA, GDPR and your own outreach policy.

Related Actors

Actor	What it collects
KakaoTalk Email and Phone Number Scraper	Emails and phone numbers from KakaoTalk
KakaoTalk Phone Number Scraper	Public phone numbers from KakaoTalk
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
Kick Email Scraper	Public contact emails from Kick
Lemon8 Email Scraper	Public contact emails from Lemon8
Likee Email Scraper	Public contact emails from Likee
LINE Email Scraper	Public contact emails from LINE
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 KakaoTalk Email Scraper input for Seoul beauty and skincare channels:

{
  "keywords": ["뷰티", "피부관리", "shop"],
  "location": "서울",
  "customDomains": ["@naver.com", "@daum.net", "@hanmail.net", "@gmail.com"],
  "maxEmails": 50,
  "countryCode": "KR",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "business", "inquiry"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}

One dataset item from that run:

{
  "network": "KakaoTalk",
  "keyword": "피부관리",
  "query": "site:pf.kakao.com OR site:kakao.com OR site:open.kakao.com 피부관리 inquiry \"@naver.com\" \"서울\"",
  "title": "서울스킨 피부관리실 | 카카오톡 채널",
  "accountName": "_seoulskin",
  "fullName": "서울스킨 피부관리실",
  "username": "_seoulskin",
  "profileUrl": "https://pf.kakao.com/_seoulskin",
  "url": "https://pf.kakao.com/_seoulskin",
  "description": "서울 강남 피부관리실. 예약 및 제휴 문의 seoulskin.care@naver.com",
  "email": "seoulskin.care@naver.com",
  "emailDomain": "@naver.com",
  "possiblyTruncated": false,
  "foundAt": "2025-03-14T09:41:22Z"
}

Every row the KakaoTalk 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 short run gives you usable data before it completes.

KakaoTalk Email Scraper FAQ

What is the KakaoTalk Email Scraper?

An Apify Actor that extracts publicly indexed contact emails from pf.kakao.com, kakao.com and open.kakao.com search results and returns them as a structured dataset.

Why does the KakaoTalk Email Scraper return so few results?

Because KakaoTalk exposes very few indexable public profile pages. Low volume is the expected outcome on this platform, and no configuration removes that ceiling.

Can it read KakaoTalk chats, contacts or friend lists?

No. The KakaoTalk Email Scraper never opens the app, never authenticates and has no access to any private data.

Does it use Kakao's API?

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

Which email domains work best for Korea?

@naver.com, @daum.net, @hanmail.net, @kakao.com and @nate.com. Adding these instead of the defaults is the biggest single yield improvement available.

Which country code should I use?

Start with KR. Run US as a second pass to catch bilingual and diaspora-facing Kakao Channels.

Do Korean keywords work?

Yes. Keywords are placed into the Google query as written, so Hangul terms like 쇼핑몰 and 문의 behave exactly like English ones.

What does possiblyTruncated mean?

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

Why are some username and profileUrl values empty?

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

Does the KakaoTalk 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 Kakao the practical ceiling is what Google has indexed, which is well below either figure.

Can I run the KakaoTalk Email Scraper on a schedule?

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

What export formats are supported?

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

Is the KakaoTalk Email Scraper affiliated with Kakao?

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

Leave a review

If the KakaoTalk 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.