Gumroad Email Scraper

Gumroad Email Scraper — Extract Public Contact Emails from Gumroad Creators

The Gumroad Email Scraper finds publicly indexed contact emails belonging to Gumroad creators and digital product sellers, and returns them as clean, structured data.

You give it keywords such as digital products or creator, choose the email domains you care about, and the Gumroad Email Scraper writes a dataset of leads with store names, subdomain handles, product snippets and profile URLs.

Gumroad is the default storefront for indie makers: Notion templates, Lightroom presets, fonts, UI kits, sample packs, ebooks, prompt libraries and one-person courses.

Every seller gets their own store at name.gumroad.com, and those store and product pages are indexed by Google — often with a support or business address in the description.

Important: this Gumroad Email Scraper never logs into Gumroad, never uses the Gumroad API, and never opens gumroad.com directly. Every record comes from publicly indexed Google search results.

It is a Gumroad email extractor for creator outreach, affiliate recruiting and lead generation — not a sales-data tool and not a customer-list scraper.

---

Key Features of the Gumroad Email Scraper

The table below reflects what the Gumroad Email Scraper genuinely does. No invented capabilities, no marketing fiction.

Feature	What it means in practice
Google site: data collection	Queries are restricted to gumroad.com, so only Gumroad store and product pages are parsed
Query expansion	Each keyword × domain pair is searched in several phrasings: base, quoted, intitle:, plus one variant per query modifier
Domain-filtered extraction	Only emails ending in your customDomains list are kept
Global deduplication	One email appears once across every query and every page of the run
Subdomain handle recovery	Because every seller gets name.gumroad.com, the crawler recovers that subdomain as username and builds a canonical profileUrl
Obfuscation-aware parser	Understands name [at] domain [dot] com, name (at) domain, name @ domain.com, domain .com, zero-width characters and the full-width ＠
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	Discards a hit that is only the tail of another email in the same result block
Structural HTML parsing	Locates the <h3> title, then the smallest surrounding block — it does not depend on Google's CSS class names
Whole-page fallback parser	If Google's markup changes, the run degrades to "emails without account metadata" rather than "no emails"
Concurrency	An asyncio worker pool runs several queries in parallel with a shared stop signal on maxEmails
Retry logic and proxy rotation	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 silently counted as empty
Blocked-query requeue	Failed or blocked queries are re-queued once at the end of the run
Resumable state	Progress is stored in the key-value store keyed by a hash of your input, saved on PERSIST_STATE, MIGRATING and ABORTING
Streaming dataset writes	Each lead is pushed to the Apify dataset the moment it is found
Run summary logging	Pages fetched, blocked pages, retries and emails per page are reported at the end

---

How the Gumroad Email Scraper Works: Crawler and Parser Pipeline

The Gumroad Email Scraper pipeline is short and deliberately transparent. There is no browser, no JavaScript rendering, no authentication and no cookies.

1. Read input. The Gumroad Email Scraper loads your keywords, optional location, email domains and limits.

2. Build queries. It composes Google queries with the site: operator, for example site:gumroad.com notion template "@gmail.com" "Berlin".

3. Fetch search result pages. Pagination is handled asynchronously with aiohttp through the Apify GOOGLE_SERP proxy, with retry logic and a fresh proxy session on every attempt.

4. Parse result blocks. For each result the Gumroad Email Scraper finds the <h3> title, walks up to the smallest enclosing block, and reads the title, the breadcrumb host and the snippet.

5. Extract and normalise emails. A domain-filtered regex pulls addresses out of the block text, then normalisation and the junk filter clean them up.

6. Deduplicate and push. Every unique email is written to the dataset immediately, so you can start exporting mid-run.

Base queries run first, so the earliest rows the Gumroad Email Scraper writes are usually the highest-signal ones.

---

What Structured Data Does the Gumroad Email Scraper Extract?

The Gumroad Email Scraper produces one dataset item per unique email, and every item carries the same 14 fields.

Alongside the address you get the account label Google printed, a canonical gumroad.com store link, the subdomain handle, and the product or bio snippet the email came from.

Because Gumroad stores are white-labelled, accountName is usually the seller's own brand — "Pixel Practice", not a platform handle. That is expected metadata here, not a defect.

You also get full provenance: the keyword and the exact Google query that produced the lead, plus a UTC timestamp.

That provenance is what makes a creator contact list maintainable. It shows which product keyword actually reaches your niche so you can drop the ones that do not.

Nothing outside these 14 fields is collected. The Gumroad Email Scraper does not touch sales figures, customer lists, prices or anything behind a login.

---

Gumroad Email Scraper Input Schema

Every field below is taken verbatim from the Gumroad Email Scraper input schema.

Field	Type	Default	Description
keywords	array (required)	["digital products", "creator"]	Search terms describing the Gumroad accounts you want (niche, job title, industry)
location	string	""	Optional location phrase added to every query
customDomains	array	["@gmail.com", "@yahoo.com"]	Only emails on these domains are collected; the leading @ is 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…)
expandQueries	boolean	true	Search each keyword × domain pair with several phrasings
queryModifiers	array	["email", "contact", "business inquiries", "collab", "booking", "dm"]	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

JSON input example

{
  "keywords": ["notion template", "lightroom presets", "figma ui kit"],
  "location": "Berlin",
  "customDomains": ["@gmail.com", "@yahoo.com"],
  "maxEmails": 300,
  "countryCode": "DE",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "business inquiries", "collab", "booking", "dm"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}

Why query expansion matters for contact discovery

Google returns roughly 300 results for any single query, which is a hard ceiling on a one-shot search.

With expandQueries on, notion template × @gmail.com becomes a base query, a quoted query, an intitle: query and one query per modifier — business inquiries, collab, booking and the rest.

Because deduplication is global, expansion can only add leads to the Gumroad Email Scraper dataset. Leave it enabled unless you are running a deliberately tiny test.

---

Gumroad Email Scraper Output Schema

Every dataset item produced by the Gumroad Email Scraper contains all 14 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 — on Gumroad usually the store or brand name
fullName	Display name parsed from a profile-style title; empty for product-page titles that carry no name
username	URL-safe handle when Gumroad exposes one — the gumroad.com subdomain; 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 product 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

JSON output example

{
  "network": "Gumroad",
  "keyword": "notion template",
  "query": "site:gumroad.com notion template \"@gmail.com\" \"Berlin\"",
  "title": "Second Brain OS — Pixel Practice",
  "accountName": "Pixel Practice",
  "fullName": "Pixel Practice",
  "username": "pixelpractice",
  "profileUrl": "https://pixelpractice.gumroad.com/",
  "url": "https://pixelpractice.gumroad.com/l/second-brain-os",
  "description": "A Notion system for freelancers, built in Berlin. Support and business inquiries: pixelpractice.studio@gmail.com",
  "email": "pixelpractice.studio@gmail.com",
  "emailDomain": "@gmail.com",
  "possiblyTruncated": false,
  "foundAt": "2026-08-31T09:42:17Z"
}

Export the Gumroad Email Scraper dataset as JSON, CSV, XLSX or HTML, or pull it through the Apify API into your CRM.

---

How to Use the Gumroad Email Scraper

Step 1 — open the Actor. Launch the Gumroad Email Scraper on the Apify platform.

Step 2 — enter keywords. Use product language, not category language. procreate brush pack and ai prompt pack beat digital download every time.

Step 3 — pick your email domains. Start with @gmail.com and @yahoo.com, then add @proton.me, @icloud.com or @outlook.com — indie makers are a privacy-minded crowd.

Step 4 — set maxEmails and run. Leave query expansion on so the automation works around Google's per-query result cap.

Step 5 — export. Download the data, or schedule a weekly Gumroad Email Scraper run so newly launched stores get picked up automatically.

If you want the same workflow on a support-page platform, the Ko-fi Email Scraper reaches many of the same independent creators.

---

Use Cases for the Gumroad Email Scraper

Use case	How the Gumroad Email Scraper helps
Affiliate recruiting	Find sellers whose audience matches your product and pitch a revenue share
Marketplace seller acquisition	Invite proven digital product sellers onto your own storefront
SaaS lead generation	Reach creators for tools covering payments, tax, email, analytics or licensing
Bundle and cross-promotion deals	Assemble a creator contact list for a themed bundle launch
Newsletter sponsorship	Indie makers with products are natural sponsors and sponsees
Agency prospecting	Offer landing-page, ads or launch copy services to people already selling
Product research	Read description snippets to map what a niche is actually shipping
Talent sourcing	Template and UI-kit sellers are often freelancers available for contract work
Press and roundup research	Build a source list for "best Notion templates" style coverage
CRM enrichment	Match store names and subdomain profile URLs to accounts you already track

Gumroad's seller base is overwhelmingly one-person businesses, and one-person businesses answer their own email — which is why creator outreach converts here.

In every one of these scenarios the Gumroad Email Scraper does the tedious part — reading thousands of search results — and leaves the judgement to you.

---

Why Choose This Gumroad Email Scraper

It is honest about its source. The Gumroad Email Scraper reads Google's public index. Nothing more, nothing hidden.

It returns usable profile URLs. Gumroad's one-subdomain-per-seller model exposes a handle in the URL, so most rows carry a working profileUrl you can open and verify.

It is resilient. Structural parsing plus a whole-page fallback means a Google layout change degrades output quality instead of breaking the crawler.

It is resumable. Migrations and aborts do not cost you a run; state is keyed by a hash of your input.

It is precise. Domain filtering, boundary-correct matching, obfuscation handling and the junk filter keep noise out of your dataset.

It is part of a family. The same engine powers dozens of sibling Actors, including the Kajabi Email Scraper for coaches with full course businesses and the Skillshare Email Scraper for the artists behind many Gumroad brush packs.

---

Limitations of the Gumroad Email Scraper

These are real constraints. Read them before you set expectations.

• Only publicly indexed emails. If an address is not visible in Google's index, the Gumroad Email Scraper cannot find it. Private data is never accessed.
• Google's ~300-result cap. A single query returns roughly 300 results at most. Query expansion exists precisely to work around this, so keep expandQueries on.
• possiblyTruncated. When Google's snippet ellipsis touches an address, this flag is set to true. Verify those rows before sending anything.
• Apify GOOGLE_SERP proxy required. The Gumroad Email Scraper cannot run without Apify proxy credentials.
• Free-plan cap. Free Apify plans are limited to 100 emails per run. Paid plans are uncapped.
• username and profileUrl availability. These are only populated when Google's result exposes a handle. Gumroad's subdomain model means most rows have one, but stores served on a custom domain, or results that surface only a bare product title, will leave username empty and profileUrl blank. That is a Google limitation, not a bug.
• Brand names, not handles. Because Gumroad stores are white-label, accountName is the seller's own brand rather than a platform username.
• No guaranteed volume. Results vary with keywords, domains and location.

Nothing here is affiliated with, endorsed by or officially supported by Gumroad.

---

Related Actors

Actor	What it collects
Gumroad Email and Phone Number Scraper	Emails and phone numbers from Gumroad
Gumroad Phone Number Scraper	Public phone numbers from Gumroad
Academia.edu Email Scraper	Public contact emails from Academia.edu
Buy Me a Coffee Email Scraper	Public contact emails from Buy Me a Coffee
Carrd Email Scraper	Public contact emails from Carrd
Domestika Email Scraper	Public contact emails from Domestika
edX Email Scraper	Public contact emails from edX
Kaggle Email Scraper	Public contact emails from Kaggle
Kajabi Email Scraper	Public contact emails from Kajabi
Ko-fi Email Scraper	Public contact emails from Ko-fi
Linktree Email Scraper	Public contact emails from Linktree
MasterClass Email Scraper	Public contact emails from MasterClass
Meetup Email Scraper	Public contact emails from Meetup
Pluralsight Email Scraper	Public contact emails from Pluralsight
Preply Email Scraper	Public contact emails from Preply
ResearchGate Email Scraper	Public contact emails from ResearchGate
Skillshare Email Scraper	Public contact emails from Skillshare
Teachable Email Scraper	Public contact emails from Teachable
Udemy Email Scraper	Public contact emails from Udemy
Academia.edu Email and Phone Number Scraper	Emails and phone numbers from Academia.edu
Buy Me a Coffee Email and Phone Number Scraper	Emails and phone numbers from Buy Me a Coffee
Carrd Email and Phone Number Scraper	Emails and phone numbers from Carrd
Domestika Email and Phone Number Scraper	Emails and phone numbers from Domestika
edX Email and Phone Number Scraper	Emails and phone numbers from edX
Kaggle Email and Phone Number Scraper	Emails and phone numbers from Kaggle
Kajabi Email and Phone Number Scraper	Emails and phone numbers from Kajabi
Ko-fi Email and Phone Number Scraper	Emails and phone numbers from Ko-fi
Linktree Email and Phone Number Scraper	Emails and phone numbers from Linktree
MasterClass Email and Phone Number Scraper	Emails and phone numbers from MasterClass
Meetup Email and Phone Number Scraper	Emails and phone numbers from Meetup
Pluralsight Email and Phone Number Scraper	Emails and phone numbers from Pluralsight
Preply Email and Phone Number Scraper	Emails and phone numbers from Preply
ResearchGate Email and Phone Number Scraper	Emails and phone numbers from ResearchGate
Skillshare Email and Phone Number Scraper	Emails and phone numbers from Skillshare
Teachable Email and Phone Number Scraper	Emails and phone numbers from Teachable
Academia.edu Phone Number Scraper	Public phone numbers from Academia.edu
Buy Me a Coffee Phone Number Scraper	Public phone numbers from Buy Me a Coffee
Carrd Phone Number Scraper	Public phone numbers from Carrd
Domestika Phone Number Scraper	Public phone numbers from Domestika
edX Phone Number Scraper	Public phone numbers from edX
Kaggle Phone Number Scraper	Public phone numbers from Kaggle
Kajabi Phone Number Scraper	Public phone numbers from Kajabi

Gumroad Email Scraper Example Run

A productivity SaaS wants affiliates who already sell to the same audience.

They run the Gumroad Email Scraper with keywords: ["notion template", "obsidian vault", "productivity planner"], customDomains: ["@gmail.com", "@proton.me"] and maxEmails: 250.

Query expansion turns three keywords into more than twenty phrasings; the automation paginates through Google while the dataset fills with store names, subdomains and addresses.

They sort by possiblyTruncated, drop the flagged rows, open a sample of gumroad.com profile URLs to gauge catalogue quality, then export a CSV. Total setup time: under five minutes.

---

Gumroad Email Scraper FAQ

Does the Gumroad Email Scraper log into Gumroad?

No. It never logs in, never uses the Gumroad API and never opens gumroad.com. All data comes from publicly indexed Google search results.

Where do the emails actually come from?

From Google result titles, breadcrumb labels and snippets for pages on gumroad.com — typically store bios and product descriptions where the seller published a support address.

Is this a Gumroad email extractor or a full product scraper?

It is a Gumroad email extractor. It returns the 14 fields listed above and nothing else — no prices, no sales counts, no ratings, no customer data.

Will I get a working profile URL?

Usually yes. Gumroad gives each seller a name.gumroad.com subdomain, and the parser recovers that subdomain as username, then builds profileUrl from it.

Why is accountName a store name instead of a handle?

Because Gumroad stores are white-labelled. Google prints the seller's own brand, so accountName reads like "Pixel Practice" rather than a username.

Do I need an Apify proxy?

Yes. The Gumroad Email Scraper requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials.

How many emails can it collect per run?

Free Apify plans are capped at 100 emails per run. Paid plans are uncapped, bounded only by your maxEmails value and what Google has indexed.

What does possiblyTruncated: true mean?

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

Should I leave query expansion enabled?

Yes. Google caps a single query at roughly 300 results, and query expansion is how the Gumroad Email Scraper reaches past that ceiling.

Which keywords work best on Gumroad?

Product nouns. figma ui kit, sample pack, resume template and procreate brushes outperform abstract terms like digital products.

Can I filter to a specific email domain?

Yes — customDomains accepts any list, with or without the leading @. Boundary-correct matching prevents false hits like @gmail.company.

Does it deduplicate?

Yes, globally. An email appears once per run no matter how many queries or pages surfaced it.

What happens if a run is interrupted?

Progress is saved in the key-value store, keyed by a hash of your input, and flushed on PERSIST_STATE, MIGRATING and ABORTING. Restarting resumes rather than starting over.

Is this affiliated with Gumroad?

No. The Gumroad Email Scraper is an independent tool and is not affiliated with, endorsed by or officially supported by Gumroad.

How should I use the results responsibly?

Follow GDPR, CAN-SPAM and any other law that applies to you. Publicly visible does not mean consent to bulk marketing — keep outreach relevant and honour opt-outs.

---

Leave a review

If the Gumroad 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, bug reports or a custom build request? Email neurodata.apify@gmail.com and include your run ID so the Gumroad Email Scraper logs can be checked quickly.