# Carrd Email Scraper (`neuro-scraper/carrd-email-scraper`) Actor

Carrd Email Scraper SD - Carrd Email Scraper is a lead generation tool that extracts leads with public contact emails, account names and profile URLs from Carrd results by keyword, location and email domain - Carrd email extractor.

- **URL**: https://apify.com/neuro-scraper/carrd-email-scraper.md
- **Developed by:** [Neuro Scraper](https://apify.com/neuro-scraper) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.49 / 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.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

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

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### Carrd Email Scraper - extract public freelancer and portfolio emails from Carrd sites

The **Carrd Email Scraper** collects publicly indexed contact emails from Carrd one-page sites: freelance portfolios, designer resumes, indie-hacker landing pages, musician press kits, coach bios and small-business micro-sites.

You supply keywords, an optional location and a list of email domains. The Carrd Email Scraper builds domain-scoped Google queries against `carrd.co`, parses each result block and writes every matching address into a structured dataset.

There is no login, no Carrd API, no headless browser and no cookies. This Carrd email extractor reads only what Google has already indexed publicly.

Carrd is a strong source because a one-page site exists to be contacted. Most parsed rows carry a site identity and a usable profile URL, and because every free Carrd site gets its own subdomain the Actor recovers `jane` from `jane.carrd.co` as the `username`.

Agencies, recruiters, no-code tool vendors, hiring managers and partnership teams use the Carrd Email Scraper for contact discovery at a scale manual browsing cannot match.

***

### Features of the Carrd Email Scraper

Everything below is implemented in the Carrd Email Scraper today. No roadmap items, no aspirational claims.

| Feature | What it means in practice |
|---|---|
| Google `site:` search automation | Every query is scoped to `carrd.co`, so results stay on-platform |
| Subdomain handle recovery | The site subdomain becomes `username`, rebuilt into a `carrd.co` profile URL |
| Query expansion | Base, quoted and `intitle:` variants plus one variant per query modifier |
| Freelance-tuned modifiers | Defaults are `email`, `contact`, `inquiries`, `hire`, `work with me` |
| Domain-filtered extraction | Only emails on your `customDomains` list are kept |
| Global deduplication | Each unique address reaches the dataset exactly once across all queries and pages |
| Obfuscation-aware parser | Understands `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, `domain .com` |
| Unicode normalisation | Handles zero-width characters and the full-width at sign |
| 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 |
| Concurrency control | An `asyncio` worker pool runs queries in parallel with a shared stop signal on `maxEmails` |
| 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, never scored as empty |
| Re-queue pass | Blocked or failed queries are retried once more at the end of the run |
| Resumable state | Progress persists in the key-value store, keyed by a hash of your input |
| Structural parsing | Result blocks are located via the `<h3>` title, not by Google's CSS class names |
| Fallback parser | A Google markup change degrades to "emails without account details", not "no emails" |
| Streaming dataset writes | Leads appear in the dataset immediately, so exports can begin mid-run |

***

### How the Carrd Email Scraper works

The Carrd Email Scraper is a search-results crawler. It never opens a carrd.co site and never submits a contact form.

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

**2. Build queries.** Queries use the `site:` operator, for example:
`site:carrd.co freelance designer "@gmail.com" "Lisbon"`.

**3. Expand queries.** With `expandQueries` on, each keyword and domain pair is issued as a base query, a quoted variant, an `intitle:` variant and one variant per entry in `queryModifiers`. Base queries always run first.

**4. Fetch pages.** The Carrd Email Scraper fetches result pages asynchronously with `aiohttp` through the Apify GOOGLE_SERP proxy, paginating up to `maxPagesPerQuery`.

**5. Parse result blocks.** The parser locates the `<h3>` title, then the smallest surrounding block, so titles, snippets and site labels stay attached to the correct record.

**6. Extract and normalise.** A domain-filtered regex pulls candidates from the block text, normalises them, and removes junk, tails and boundary mismatches.

**7. Deduplicate and store.** Every new address is deduplicated globally and pushed straight into the Apify dataset as structured data.

The Carrd Email Scraper run summary logs pages fetched, blocked pages, retries and emails per page, so you can judge a keyword set on evidence.

***

### What data does the Carrd Email Scraper extract?

Each row is one email paired with the site metadata Google exposed alongside it.

You get the address, the matched domain, the site or account label, a parsed name, the subdomain handle and profile URL, a cleaned description snippet and full provenance.

Provenance is the underrated part. The `keyword` and `query` fields tell you which phrasing surfaced this site, which is exactly what you tune on the next lead generation run.

Because every Carrd site sits on its own subdomain, the Carrd Email Scraper resolves `username` and rebuilds `profileUrl` as `https://<handle>.carrd.co/` on the large majority of parsed results.

***

### Input schema for the Carrd Email Scraper

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

| Field | Type | Default | Description |
|---|---|---|---|
| `keywords` | array (required) | `["freelancer", "portfolio"]` | Search terms describing the Carrd sites 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 and 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

```json
{
  "keywords": ["freelance designer", "video editor", "copywriter"],
  "location": "London",
  "customDomains": ["@gmail.com", "@outlook.com"],
  "maxEmails": 300,
  "countryCode": "GB",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "inquiries", "hire", "work with me"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

***

### Output schema of the Carrd Email Scraper

Every dataset item the Carrd Email Scraper produces carries 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 (subdomain handle or site name) |
| `fullName` | Display name parsed from a profile-style title; empty for generic page titles |
| `username` | URL-safe handle when Carrd exposes one, taken from the subdomain; otherwise `null` |
| `profileUrl` | Canonical site URL when a handle is known; otherwise empty |
| `url` | Direct Carrd link when exposed, else the profile URL |
| `description` | Page or bio 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

```json
{
  "network": "Carrd",
  "keyword": "freelance designer",
  "query": "site:carrd.co freelance designer \"@gmail.com\" work with me",
  "title": "Jane Okafor - Freelance Brand Designer",
  "accountName": "janeokafor",
  "fullName": "Jane Okafor",
  "username": "janeokafor",
  "profileUrl": "https://janeokafor.carrd.co/",
  "url": "https://janeokafor.carrd.co/",
  "description": "Brand identity and packaging design for small food brands. Currently taking projects. Work with me: jane.okafor.design@gmail.com",
  "email": "jane.okafor.design@gmail.com",
  "emailDomain": "@gmail.com",
  "possiblyTruncated": false,
  "foundAt": "2026-08-31T12:04:55.610Z"
}
```

The Carrd 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 Carrd Email Scraper

**Step 1 - use job-title language.** Carrd titles read like `Jane Okafor - Freelance Brand Designer`. Keywords such as `freelance designer`, `UX writer`, `video editor`, `photographer` or `music producer` match how people actually title a one-page site.

**Step 2 - pick email domains that fit independents.** `@gmail.com` covers most solo freelancers. Add `@outlook.com` or `@proton.me` when you want broader coverage.

**Step 3 - start small.** Run the Carrd Email Scraper with `maxEmails` at 20 to 50 to confirm the keyword set matches the seniority and niche you want.

**Step 4 - keep the freelance-tuned modifiers.** `hire`, `work with me` and `inquiries` are literally the section headings people put on a Carrd portfolio.

**Step 5 - use `location` more freely here than elsewhere.** Freelancers often state a city on a portfolio page, so location filtering is more productive on Carrd than on most platforms.

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

***

### Use cases for the Carrd Email Scraper

| Use case | Who runs it | Typical keywords |
|---|---|---|
| Freelance talent sourcing | Agencies, studios and hiring managers | `freelance designer`, `video editor`, `copywriter` |
| Recruiting and candidate pipelines | Recruiters and in-house sourcers | `portfolio`, `product designer`, `front end developer` |
| No-code and SaaS prospecting | Founders selling tools to indie makers | `indie hacker`, `no code`, `landing page` |
| Creative services partnerships | Print shops, studios, production houses | `photographer`, `illustrator`, `animator` |
| Musician and artist booking | Promoters and venue bookers | `music producer`, `dj`, `band epk` |
| Local small-business outreach | Local marketers and web agencies | `personal trainer`, `bakery`, `salon` |
| Coaching and consulting partnerships | Course platforms and lead-gen agencies | `career coach`, `consultant`, `nutritionist` |
| Portfolio and market research | Analysts studying the no-code web | any niche keyword, varied by `location` |

Carrd sits at the point where somebody has decided to be findable but has not yet built a full website, so the Carrd Email Scraper surfaces a lot of early-stage independents.

Creators who chose a link hub instead of a one-page site are better covered by the [Linktree Email Scraper](https://apify.com/leads-scraper/linktree-email-scraper), and creators who monetise directly show up in the [Ko-fi Email Scraper](https://apify.com/neuro-scraper/ko-fi-email-scraper) or the [Gumroad Email Scraper](https://apify.com/leads-scraper/gumroad-email-scraper).

***

### Why choose this Carrd Email Scraper

Manually collecting freelancer contacts means searching, opening a site, hunting for the contact block, copying an address and repeating. The Carrd Email Scraper automates that loop and returns a deduplicated dataset.

Every row is auditable. The `query` and `keyword` fields show exactly how a lead was found, so weak keyword sets are easy to prune.

The extraction layer is deliberately conservative. Junk filtering, boundary-correct domain matching and soft-wrap repair mean far fewer garbage rows to clean downstream.

Long Carrd Email Scraper runs survive interruption. State persists in the key-value store and saves fire on Apify's `PERSIST_STATE`, `MIGRATING` and `ABORTING` events.

***

### Worked example: a freelance video-editor bench

Your agency needs 200 freelance video editors it can brief on short notice.

Set `keywords` to `["video editor", "motion designer", "after effects"]`, `customDomains` to `["@gmail.com"]`, `location` to `"United Kingdom"`, `countryCode` to `"GB"` and `maxEmails` to `200`.

The Carrd Email Scraper issues base, quoted and `intitle:` variants plus one query per modifier, paginating each independently and streaming leads as they are found.

Export the Carrd Email Scraper dataset to CSV, remove `possiblyTruncated` rows, sort by `keyword` to see which discipline yielded best, then import the rest into your talent database.

***

### Limitations you should know before running

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

**Only publicly indexed emails.** The Carrd Email Scraper returns addresses that already appear in Google's index. Sites that hide contact behind a form only, with no visible address, will not surface.

**Google's per-query ceiling.** A single query caps out at roughly 300 results. Query expansion exists to work around that ceiling, which is why it defaults to on.

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

**Apify GOOGLE_SERP proxy required.** The Carrd Email Scraper cannot run without Apify proxy credentials that include the GOOGLE_SERP group.

**Free-plan cap.** Running the Carrd Email Scraper on a free Apify plan limits results to 100 emails per run. Paid plans are uncapped.

**Handle availability.** `username` and `profileUrl` are populated only when Google's result exposes a Carrd subdomain. Carrd performs well here, but some rows will still carry `accountName` and `fullName` with an empty `username` and `profileUrl`, which is a Google limitation, not a bug.

**No guaranteed volume.** Carrd Email Scraper yield varies with keywords, domains and location. No result count is promised.

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

***

### Related Actors

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

| Actor | What it collects |
|---|---|
| [Carrd Email and Phone Number Scraper](https://apify.com/neuro-scraper/carrd-email-and-phone-number-scraper) | Emails and phone numbers from Carrd |
| [Carrd Phone Number Scraper](https://apify.com/neuro-scraper/carrd-phone-number-scraper) | Public phone numbers from Carrd |
| [Academia.edu Email Scraper](https://apify.com/neuro-scraper/academia-edu-email-scraper) | Public contact emails from Academia.edu |
| [Buy Me a Coffee Email Scraper](https://apify.com/neuro-scraper/buy-me-a-coffee-email-scraper) | Public contact emails from Buy Me a Coffee |
| [Domestika Email Scraper](https://apify.com/neuro-scraper/domestika-email-scraper) | Public contact emails from Domestika |
| [edX Email Scraper](https://apify.com/leads-scraper/edx-email-scraper) | Public contact emails from edX |
| [Gumroad Email Scraper](https://apify.com/leads-scraper/gumroad-email-scraper) | Public contact emails from Gumroad |
| [Kaggle Email Scraper](https://apify.com/neuro-scraper/kaggle-email-scraper) | Public contact emails from Kaggle |
| [Kajabi Email Scraper](https://apify.com/neuro-scraper/kajabi-email-scraper) | Public contact emails from Kajabi |
| [Ko-fi Email Scraper](https://apify.com/neuro-scraper/ko-fi-email-scraper) | Public contact emails from Ko-fi |
| [Linktree Email Scraper](https://apify.com/leads-scraper/linktree-email-scraper) | Public contact emails from Linktree |
| [MasterClass Email Scraper](https://apify.com/neuro-scraper/masterclass-email-scraper) | Public contact emails from MasterClass |
| [Meetup Email Scraper](https://apify.com/leads-scraper/meetup-email-scraper) | Public contact emails from Meetup |
| [Pluralsight Email Scraper](https://apify.com/leads-scraper/pluralsight-email-scraper) | Public contact emails from Pluralsight |
| [Preply Email Scraper](https://apify.com/neuro-scraper/preply-email-scraper) | Public contact emails from Preply |
| [ResearchGate Email Scraper](https://apify.com/neuro-scraper/researchgate-email-scraper) | Public contact emails from ResearchGate |
| [Skillshare Email Scraper](https://apify.com/neuro-scraper/skillshare-email-scraper) | Public contact emails from Skillshare |
| [Teachable Email Scraper](https://apify.com/neuro-scraper/teachable-email-scraper) | Public contact emails from Teachable |
| [Udemy Email Scraper](https://apify.com/leads-scraper/udemy-email-scraper) | Public contact emails from Udemy |
| [Academia.edu Email and Phone Number Scraper](https://apify.com/neuro-scraper/academia-edu-email-and-phone-number-scraper) | Emails and phone numbers from Academia.edu |
| [Buy Me a Coffee Email and Phone Number Scraper](https://apify.com/neuro-scraper/buy-me-a-coffee-email-and-phone-number-scraper) | Emails and phone numbers from Buy Me a Coffee |
| [Domestika Email and Phone Number Scraper](https://apify.com/neuro-scraper/domestika-email-and-phone-number-scraper) | Emails and phone numbers from Domestika |
| [edX Email and Phone Number Scraper](https://apify.com/neuro-scraper/edx-email-and-phone-number-scraper) | Emails and phone numbers from edX |
| [Gumroad Email and Phone Number Scraper](https://apify.com/leads-scraper/gumroad-email-and-phone-number-scraper) | Emails and phone numbers from Gumroad |
| [Kaggle Email and Phone Number Scraper](https://apify.com/neuro-scraper/kaggle-email-and-phone-number-scraper) | Emails and phone numbers from Kaggle |
| [Kajabi Email and Phone Number Scraper](https://apify.com/neuro-scraper/kajabi-email-and-phone-number-scraper) | Emails and phone numbers from Kajabi |
| [Ko-fi Email and Phone Number Scraper](https://apify.com/neuro-scraper/ko-fi-email-and-phone-number-scraper) | Emails and phone numbers from Ko-fi |
| [Linktree Email and Phone Number Scraper](https://apify.com/leads-scraper/linktree-email-and-phone-number-scraper) | Emails and phone numbers from Linktree |
| [MasterClass Email and Phone Number Scraper](https://apify.com/neuro-scraper/masterclass-email-and-phone-number-scraper) | Emails and phone numbers from MasterClass |
| [Meetup Email and Phone Number Scraper](https://apify.com/neuro-scraper/meetup-email-and-phone-number-scraper) | Emails and phone numbers from Meetup |
| [Pluralsight Email and Phone Number Scraper](https://apify.com/neuro-scraper/pluralsight-email-and-phone-number-scraper) | Emails and phone numbers from Pluralsight |
| [Preply Email and Phone Number Scraper](https://apify.com/neuro-scraper/preply-email-and-phone-number-scraper) | Emails and phone numbers from Preply |
| [ResearchGate Email and Phone Number Scraper](https://apify.com/neuro-scraper/researchgate-email-and-phone-number-scraper) | Emails and phone numbers from ResearchGate |
| [Skillshare Email and Phone Number Scraper](https://apify.com/neuro-scraper/skillshare-email-and-phone-number-scraper) | Emails and phone numbers from Skillshare |
| [Teachable Email and Phone Number Scraper](https://apify.com/neuro-scraper/teachable-email-and-phone-number-scraper) | Emails and phone numbers from Teachable |
| [Academia.edu Phone Number Scraper](https://apify.com/neuro-scraper/academia-edu-phone-number-scraper) | Public phone numbers from Academia.edu |
| [Buy Me a Coffee Phone Number Scraper](https://apify.com/neuro-scraper/buy-me-a-coffee-phone-number-scraper) | Public phone numbers from Buy Me a Coffee |
| [Domestika Phone Number Scraper](https://apify.com/neuro-scraper/domestika-phone-number-scraper) | Public phone numbers from Domestika |
| [edX Phone Number Scraper](https://apify.com/neuro-scraper/edx-phone-number-scraper) | Public phone numbers from edX |
| [Gumroad Phone Number Scraper](https://apify.com/leads-scraper/gumroad-phone-number-scraper) | Public phone numbers from Gumroad |
| [Kaggle Phone Number Scraper](https://apify.com/neuro-scraper/kaggle-phone-number-scraper) | Public phone numbers from Kaggle |
| [Kajabi Phone Number Scraper](https://apify.com/neuro-scraper/kajabi-phone-number-scraper) | Public phone numbers from Kajabi |

### FAQ about the Carrd Email Scraper

#### What is the Carrd Email Scraper?

It is an Apify Actor that extracts publicly indexed contact emails from Carrd one-page sites by running domain-scoped Google searches and parsing the resulting search-result blocks.

#### Does the Carrd Email Scraper open the actual Carrd site?

No. It never loads a carrd.co page, never runs JavaScript and never submits a contact form. It reads Google's indexed titles, snippets and site labels only.

#### How does it get the username?

Each Carrd site lives on its own subdomain, so the Carrd Email Scraper takes `jane` from `jane.carrd.co` as the `username` and rebuilds `profileUrl` from it.

#### Does it find sites on custom domains?

No. Queries are scoped to `carrd.co`, so a Carrd site published on its owner's own domain is outside the search scope.

#### Why is `username` empty on some rows?

Google does not always print the subdomain in the result. Those rows still carry `accountName` and `fullName`, but `username` is `null` and `profileUrl` is empty.

#### What does `possiblyTruncated: true` mean?

Google's snippet ellipsis touched the address, so it may be cut off. Verify those rows before contacting anyone.

#### How many emails will one run of the Carrd Email Scraper return?

`maxEmails` accepts 1 to 10000, but free Apify plans are capped at 100 emails per run and paid plans are uncapped. Real volume depends on keywords, domains and location.

#### Is a proxy required?

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

#### Should I leave `expandQueries` on?

Almost always. Google returns roughly 300 results per query, and expansion multiplies your reachable surface through base, quoted, `intitle:` and modifier variants.

#### Is `location` worth using on Carrd?

More than on most platforms. Freelancers frequently state a city on a portfolio page, so a location phrase narrows the Carrd Email Scraper output without destroying recall.

#### What happens if my run is interrupted or migrated?

State persists 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 everyone in the dataset immediately?

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

***

### Leave a review

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

# Actor input Schema

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

Search terms describing the Carrd accounts you want (niche, job title, industry).

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

Optional location phrase added to every query (e.g. "New York").

## `customDomains` (type: `array`):

Only emails ending with one of these domains are collected. With or without the leading @. Each domain is searched separately, so more domains means more results but a longer run - remove some for a faster, narrower search, or add your own (e.g. @company.com).

## `maxEmails` (type: `integer`):

Stop once this many unique emails have been collected.

## `countryCode` (type: `string`):

Two-letter country code for the search proxy (e.g. US, GB, DE). Empty for any.

## `expandQueries` (type: `boolean`):

Search each keyword x domain pair with several phrasings. Recommended - Google caps a single query at ~300 results.

## `queryModifiers` (type: `array`):

Extra words combined with each keyword when Expand queries is on. Tuned for Carrd.

## `maxPagesPerQuery` (type: `integer`):

Google rarely returns more than ~30 pages for one query.

## `maxConcurrency` (type: `integer`):

How many queries run in parallel.

## Actor input object example

```json
{
  "keywords": [
    "freelancer",
    "portfolio"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "inquiries",
    "hire",
    "work with me"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

## `results` (type: `string`):

Records produced by Carrd Email Scraper, stored in the run's default dataset.

# 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": [
        "freelancer",
        "portfolio"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "inquiries",
        "hire",
        "work with me"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("neuro-scraper/carrd-email-scraper").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": [
        "freelancer",
        "portfolio",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "inquiries",
        "hire",
        "work with me",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("neuro-scraper/carrd-email-scraper").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": [
    "freelancer",
    "portfolio"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "inquiries",
    "hire",
    "work with me"
  ]
}' |
apify call neuro-scraper/carrd-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,neuro-scraper/carrd-email-scraper"
        }
    }
}
```

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/xgpUoi2WGGTsfu5qS/builds/WerGnZgHsRTNgWo4k/openapi.json