Dribbble Email Scraper

Dribbble Email Scraper

Dribbble Email Scraper — extract public UI designer contact emails from Dribbble

The Dribbble Email Scraper collects publicly indexed contact emails belonging to Dribbble designers — UI and UX specialists, product designers, icon and illustration artists, and small design studios advertising availability.

You provide keywords, an optional location and a list of email domains. The Dribbble Email Scraper builds domain-scoped Google queries against dribbble.com, parses the search results and extracts every matching address into a clean dataset.

No login, no Dribbble API, no headless browser, no cookies. This Dribbble email extractor works exclusively from what Google has already published in its public index.

Recruiters, product teams, design marketplaces and agency partners use the Dribbble Email Scraper for fast contact discovery instead of clicking through shots one profile at a time.

---

Features of the Dribbble Email Scraper

Everything listed here is implemented in the Dribbble Email Scraper today, with no roadmap items and no aspirational claims.

Feature	What it means in practice
Google site: search automation	Every query is scoped to dribbble.com, so results stay on-platform
Query expansion	Base, quoted and intitle: variants plus one variant per query modifier
Hiring-tuned modifiers	Defaults include email, contact, inquiries, hire, work with me
Domain-filtered extraction	Only addresses on your customDomains list are collected
Global deduplication	A unique email is written to the dataset once, across every query and page
Obfuscation-aware parser	Reads name [at] domain [dot] com, name (at) domain, name @ domain.com, domain .com
Unicode normalisation	Handles zero-width characters and the full-width ＠ sign
Junk filter	Rejects email@, yourname@, test@, xxx@ and single-character locals
Boundary-correct matching	@gmail.com does not match inside @gmail.company or @gmail.com.br
Soft-wrap repair	Drops a hit that is only the tail of another email in the same block
Concurrency control	An asyncio worker pool runs queries in parallel with a shared stop signal
Retry logic	Up to 3 attempts per page, exponential backoff, fresh proxy session per request
Block detection	CAPTCHA, "unusual traffic" and consent pages are retried, not treated as empty
Resumable state	Progress is stored in the key-value store, keyed by a hash of your input
Structural parsing	Blocks are located from the <h3> title rather than fragile CSS class names
Fallback parser	A Google layout change degrades to "emails without account details"
Streaming dataset writes	Leads land in the dataset immediately and can be exported mid-run

---

How the Dribbble Email Scraper works

The Dribbble Email Scraper is a search-results crawler, not a shot crawler. It never requests dribbble.com directly.

1. Read input. Keywords, location, email domains, page caps and concurrency are parsed and validated.

2. Build queries. Queries are composed with the site: operator, for example: site:dribbble.com ui designer "@gmail.com" hire.

3. Expand queries. With expandQueries on, each keyword × domain pair runs as a base query, a quoted variant, an intitle: variant and one variant per entry in queryModifiers. Base queries go first.

4. Fetch pages. The Dribbble Email Scraper fetches result pages asynchronously with aiohttp through the Apify GOOGLE_SERP proxy, using proxy rotation and pagination up to maxPagesPerQuery.

5. Parse blocks. For each result the parser finds the <h3> title, then the smallest enclosing block, so titles, snippets and site labels stay bound to the right record.

6. Extract and filter. A domain-filtered regex pulls candidate addresses from the block text, normalises them and strips junk, tails and boundary mismatches.

7. Deduplicate and store. The Dribbble Email Scraper deduplicates every new email globally and pushes it straight into the Apify dataset as structured data.

The Dribbble Email Scraper re-queues blocked or failed queries once at the end of the run, and the run summary reports pages fetched, blocked pages, retries and emails per page.

---

What data does the Dribbble Email Scraper extract?

Every row the Dribbble Email Scraper writes is a single email paired with the account metadata Google exposed alongside it.

That means the address, the matched domain, the account label, a parsed display name, a handle and profile URL where Dribbble exposes one, a cleaned bio snippet, and complete provenance.

Provenance drives iteration: keyword and query show which phrasing surfaced a designer, so the next run can drop the terms that returned noise.

---

Input schema

Every Dribbble Email Scraper input field is listed below with the exact name, type and default taken from the Actor input schema.

Field	Type	Default	Description
keywords	array (required)	["designer", "ui designer"]	Search terms describing the Dribbble accounts you want (niche, job title, industry)
location	string	""	Optional location phrase added to every query, e.g. "New York"
customDomains	array	["@gmail.com", "@yahoo.com"]	Only emails ending with one of these domains are collected; leading @ optional
maxEmails	integer 1–10000	20	Stop once this many unique emails have been collected
countryCode	string	""	Two-letter country code for the search proxy (US, GB, DE…). Empty for any
expandQueries	boolean	true	Search each keyword × domain pair with several phrasings
queryModifiers	array	["email", "contact", "inquiries", "hire", "work with me"]	Extra words combined with each keyword when expansion is on
maxPagesPerQuery	integer 1–50	30	Page cap per query
maxConcurrency	integer 1–20	5	How many queries run in parallel

Input example for the Dribbble Email Scraper

{
  "keywords": ["product designer", "webflow designer", "icon designer"],
  "location": "Toronto",
  "customDomains": ["@gmail.com", "@icloud.com"],
  "maxEmails": 150,
  "countryCode": "CA",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "inquiries", "hire", "work with me"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}

---

Output schema

Every item produced by the Dribbble Email Scraper contains all fourteen fields below.

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 shot captions
username	URL-safe handle when Dribbble exposes one; otherwise null
profileUrl	Canonical account URL when a handle is known; otherwise empty
url	Direct Dribbble link when exposed, else the profile URL
description	Bio or shot snippet, cleaned of labels and engagement counters
email	Lower-cased email address
emailDomain	The matched domain, e.g. @gmail.com
possiblyTruncated	true when Google's snippet ellipsis touched the email — verify before sending
foundAt	ISO 8601 UTC timestamp

Output example

{
  "network": "Dribbble",
  "keyword": "product designer",
  "query": "site:dribbble.com product designer \"@gmail.com\" hire",
  "title": "Marcus Reyes - Product Designer | Dribbble",
  "accountName": "marcusreyes",
  "fullName": "Marcus Reyes",
  "username": "marcusreyes",
  "profileUrl": "https://dribbble.com/marcusreyes",
  "url": "https://dribbble.com/marcusreyes",
  "description": "Product designer in Toronto. SaaS dashboards, design systems, mobile. Available for freelance - marcus.reyes.ux@gmail.com",
  "email": "marcus.reyes.ux@gmail.com",
  "emailDomain": "@gmail.com",
  "possiblyTruncated": false,
  "foundAt": "2026-08-31T11:38:05.462Z"
}

The Dribbble Email Scraper dataset exports as JSON, CSV, Excel or XML from the Apify console, or streams through the Apify API into your CRM, ATS or outreach tool.

---

How to use the Dribbble Email Scraper

Step 1 — use role and stack language. Dribbble bios say design systems, SaaS dashboards, Webflow, mobile app designer. Those beat the generic word designer.

Step 2 — keep the hiring modifiers. hire, work with me and inquiries match the exact phrasing designers use to signal availability.

Step 3 — start with a small maxEmails. Confirm seniority and relevance at 20–50 rows before committing to a large run.

Step 4 — set countryCode when the role is location-bound. Combine it with a location phrase for in-office or timezone-sensitive hiring.

Step 5 — widen customDomains carefully. Studio-owned domains appear less often in snippets than personal @gmail.com addresses.

Step 6 - clean before you send. Filter out rows where possiblyTruncated is true, then put the remaining Dribbble Email Scraper results through your normal email-verification step before any outreach.

---

Use cases for the Dribbble Email Scraper

Use case	Who runs it	Typical keywords
Freelance UI designer sourcing	Startups and product teams	ui designer, mobile app designer, design systems
Agency talent bench	Design agencies covering overflow	freelance designer, webflow designer, landing page designer
Design recruiting pipelines	In-house and agency recruiters	product designer, ux designer, interaction designer
Design-tool go-to-market	SaaS founders selling to designers	figma, prototyping, design systems
Icon and illustration licensing	Marketplaces and asset publishers	icon designer, illustration, 3d icons
No-code build partnerships	Webflow / Framer studios	webflow designer, framer designer, no code
Regional talent mapping	Employer-brand and ops teams	any keyword + location
Competitive talent research	Analysts tracking design labour supply	ui designer per country

Dribbble skews toward interaction and interface work advertised for hire, so the Dribbble Email Scraper is strongest for freelance sourcing and contract staffing.

If you also need long-form portfolio and case-study talent, run the Behance Email Scraper alongside it. For illustration-heavy and commission-based artists, the DeviantArt Email Scraper reaches a different pool, and the LinkedIn Email Scraper covers in-house design leadership.

---

Why use this Dribbble Email Scraper

Manual contact discovery on Dribbble is a grind: open a shot, click the designer, read the bio, hunt for an address, repeat. The Dribbble Email Scraper turns that loop into one run and one dataset.

Results are traceable. Every row carries the exact query behind it, so you can measure which niche terms produce hires rather than guessing.

The parser is designed for durability. Structural block detection plus a whole-page fallback means Google redesigns degrade output quality instead of breaking the crawler.

Long Dribbble Email Scraper runs also survive interruption: state persists in the key-value store, and saves fire on Apify PERSIST_STATE, MIGRATING and ABORTING events.

---

Limitations you should know before running

The Dribbble Email Scraper is deliberately transparent about its boundaries. Read these before planning a large data collection run.

Only publicly indexed emails. The Dribbble Email Scraper finds addresses already visible in Google's index. Designers who route contact solely through Dribbble's hiring form will not appear.

Google's per-query ceiling. A single query returns roughly 300 results at most, which is exactly why query expansion is enabled by default.

possiblyTruncated. When Google's snippet ellipsis clips an email, this field is true and the address may be incomplete. Verify before sending.

Apify GOOGLE_SERP proxy required. The Dribbble Email Scraper cannot run without Apify proxy credentials covering the GOOGLE_SERP group.

Free-plan cap. Running the Dribbble Email Scraper on a free Apify plan means results are capped at 100 emails per run; paid plans are uncapped.

Handle availability. username and profileUrl only populate when Google's result exposes a Dribbble handle. Some rows carry accountName and fullName with an empty username and profileUrl. That is a Google limitation, not a bug.

No guaranteed volume. Output depends on keywords, domains and location; no yield is promised.

The Dribbble Email Scraper is not affiliated with, endorsed by or officially supported by Dribbble.

---

Related Actors

Every Actor below runs the same engine as the Dribbble Email Scraper, with identical input fields and an identical output schema; only the target platform differs.

Actor	What it collects
Dribbble Email and Phone Number Scraper	Emails and phone numbers from Dribbble
Dribbble Phone Number Scraper	Public phone numbers from Dribbble
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
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
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

Worked example: staffing a design-systems project

You need 100 contract designers with design-systems experience in North America.

Set keywords to ["design systems", "ui designer", "product designer"], countryCode to "US", customDomains to ["@gmail.com"] and maxEmails to 100, leaving expansion on.

The Dribbble Email Scraper runs base, quoted and intitle: variants plus one query per modifier, paginating each and pushing deduplicated leads into the dataset as they arrive.

Export the Dribbble Email Scraper dataset to CSV, discard possiblyTruncated rows, review the description snippets for seniority signals, and shortlist from there.

---

FAQ

What is the Dribbble Email Scraper?

An Apify Actor that extracts publicly indexed contact emails for Dribbble designers by running domain-scoped Google searches and parsing the search results.

Does the Dribbble Email Scraper log into Dribbble?

No. The Dribbble Email Scraper never logs in, never calls the Dribbble API and never opens a browser, so there are no cookies and no authentication anywhere in the pipeline.

Where do the emails come from?

The Dribbble Email Scraper reads publicly indexed titles, snippets and site labels, typically bios where the account owner published a contact address themselves.

Can it find emails hidden behind Dribbble's contact form?

No. If an address is not publicly visible in Google's index, the Dribbble Email Scraper will not return it.

Why do some rows have no username?

Google does not always print a handle. Those rows still include accountName and fullName, but username is null and profileUrl is empty.

What does possiblyTruncated: true mean?

Google's snippet ellipsis touched the email, so it may be cut off. Verify before sending.

How many emails can I get per run?

The Dribbble Email Scraper accepts a maxEmails value between 1 and 10000, but free Apify plans are capped at 100 emails per run and paid plans are uncapped. Real volume depends on your keywords, domains and location.

Do I need proxies?

Yes. The Dribbble Email Scraper requires the Apify GOOGLE_SERP proxy and will not run without Apify proxy credentials.

Should query expansion stay on?

Generally yes — Google caps a single query near 300 results, and the base, quoted, intitle: and modifier variants multiply coverage.

Can I target designers in one country?

Yes. Set countryCode for the search proxy and add a location phrase to bias snippets toward that region.

Is the run resumable?

The Dribbble Email Scraper persists state in the key-value store keyed by a hash of your input, with throttled saves plus saves on PERSIST_STATE, MIGRATING and ABORTING, so an interrupted run resumes instead of restarting.

Can I email the list straight away?

Treat the Dribbble Email Scraper output as raw lead data. Deduplication is automatic, but verification, consent and compliance with GDPR, CAN-SPAM and Dribbble terms of service remain your responsibility.

---

Leave a review

If the Dribbble 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 about the Dribbble Email Scraper, bug reports or a custom build? Email neurodata.apify@gmail.com.