# Dribbble Email Scraper - Keyword Search & Domain Filter (`parse-point/dribbble-email-scraper-lightning-fast-and-accurate`) Actor

🏀 Dribbble Email Scraper pulls designer and studio emails with keyword and location filters. 🎯 Limit to specific domains, decode hidden addresses and drop duplicates. 💼 Built for design hiring and agency outreach.

- **URL**: https://apify.com/parse-point/dribbble-email-scraper-lightning-fast-and-accurate.md
- **Developed by:** [Parse Point](https://apify.com/parse-point) (community)
- **Categories:** Lead generation, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.99 / 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.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### Dribbble Email Scraper 🔍

**Dribbble Email Scraper** helps marketers, recruiters, and sales pros extract email addresses from Dribbble so you stop manually hunting for contact info. It’s built for `dribbble email extractor` workflows and `extract emails from dribbble` as part of `dribbble lead generation`—so you can scale outreach faster with less effort.

***

### 🌟 Key Features of Dribbble Email Scraper

| Feature | Benefit |
|---|---|
| ✅ **Targeted Keyword Search** | Reach the exact Dribbble audience you need for email scraping and outreach |
| ✅ **Location Filtering** | Geo-target contacts by city, region, or country when you set `location` |
| ✅ **Custom Domain Filter** | Extract only emails matching your allowed domains (e.g., `@gmail.com`, `@yahoo.com`) |
| ✅ **Bulk Export (JSON / CSV)** | Use the Apify dataset to export results into your CRM or email tool |
| ✅ **Proxy-Ready** | Helps scraping run more smoothly with built-in proxy support |
| ✅ **Real-Time Saving** | Results are saved incrementally to reduce risk of data loss on long runs |

This is a practical `dribbble contact extraction` tool for anyone building `designer email leads` and accelerating `lead generation automation`.

***

### 📥 Input — Dribbble Email Scraper Parameters

```json
{
  "keywords": ["manager", "founder"],
  "location": "",
  "customDomains": ["@gmail.com", "@yahoo.com"],
  "maxEmails": 20
}
```

| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| `keywords` | Array | ✅ Yes | — | Search terms to find relevant Dribbble profiles for email extraction |
| `location` | String | No | `""` | City or region to filter the results and focus your dribbble email finder efforts |
| `customDomains` | Array | No | `[]` | Allowed email domains to filter extracted emails (for example `@gmail.com`) |
| `maxEmails` | Integer | No | `20` | Maximum number of emails to collect per run (helps control scraping time and cost) |

Use `website scraping` style targeting by combining job titles/roles in `keywords` with domain filters for more relevant `contact information harvesting`.

***

### 📤 Output — What Dribbble Email Scraper Returns

The actor saves each result as a JSON record in your Apify dataset.

```json
[
  {
    "keyword": "manager",
    "title": "Product Design Manager",
    "description": "Design leadership • Systems thinking • Email: mia.ross@gmail.com",
    "url": "https://dribbble.com/miarossdesign",
    "email": "mia.ross@gmail.com"
  },
  {
    "keyword": "founder",
    "title": "Creative Founder",
    "description": "Brand & UX studio • Portfolio • Reach out at harper@studio-nova.co",
    "url": "https://dribbble.com/studionovauk",
    "email": "harper@studio-nova.co"
  }
]
```

| Field | Type | Description |
|---|---|---|
| `keyword` | String | The search term that surfaced this result during Dribbble contact discovery |
| `title` | String | Dribbble profile name or business title associated with the contact |
| `description` | String | Profile bio or summary text scraped from Dribbble |
| `url` | String | Direct link to the Dribbble profile for quick verification |
| `email` | String | Extracted email address associated with the profile (filtered by your domains) |

This output is ideal for `email validation` workflows and `data mining` lead lists for `nft marketing leads` or broader `designer email leads`.

***

### 💻 How to Use Dribbble Email Scraper — Step-by-Step

1. **Open the Actor** — Find **Dribbble Email Scraper** on [Apify Store](https://apify.com/store).
2. **Enter Keywords** — Add job titles, roles, or business-focused terms relevant to your `dribbble scraper` goals.
3. **Set Location** *(optional)* — Narrow results to a specific city or region for more precise `social media lead generation`.
4. **Filter by Domain** *(optional)* — Choose domains in `customDomains` to target specific email types.
5. **Set Max Emails** — Cap the total extracted emails to manage runtime and scraping cost.
6. **Run the Actor** — Start the run and monitor progress in live logs.
7. **Export Results** — Download from the Apify dataset tab as JSON/CSV for use in your CRM.

***

### 💡 Best Use Cases for Dribbble Email Scraper

- 🎯 **B2B Lead Generation** — Build a focused **Dribbble Email List** for outreach and partnerships
- 📣 **Email Marketing** — Expand your campaign segments with fresh Dribbble contacts
- 🤝 **Recruitment** — Reach designers and creative leaders with direct `contact information harvesting`
- 🔬 **Market Research** — Identify active industry voices for targeted `website scraping` insights
- 🧠 **CRM Enrichment** — Improve lead records with `dribbble contact extraction` results

***

### Disclaimer

This actor only accesses **publicly available data** on Dribbble. It does not scrape private profiles, authenticated content, or password-protected pages. You’re responsible for ensuring your use complies with Dribbble’s Terms of Service and applicable privacy and anti-spam laws (including GDPR/CCPA where relevant). Use it for legitimate purposes such as research and compliant outreach. For data-removal requests, contact 📧 <hello.parsepoint@gmail.com>.

***

### 🆘 Support & Feedback

Have a question or found an issue with the **Dribbble Email Scraper**? We’re here to help.

- 🐞 **Bug Reports:** Open a ticket in the repository's Issues section
- ✨ **Custom Solutions & Feature Requests:** Reach out to our team
- 📧 **Email:** <hello.parsepoint@gmail.com>

Your feedback helps us improve `email scraping` quality for `dribbble scraper` users.

### Run Memory

**Skip keywords already scraped in a previous run** - the actor keeps a
persistent record of every keyword it finishes, in a named key-value store that
survives between runs. Turn this on and a repeat run silently drops the keywords
it has already covered, so a scheduled job over a fixed list only pays for new
ground.

A keyword is identified by the keyword *plus* the set of email domains it was
searched against, so re-running `fitness` against a new domain list is correctly
treated as new work rather than a duplicate.

**Reset keyword history** - wipe that record before the run starts, so
everything counts as new again.

**Max emails per keyword** - cap how many results any single keyword may
produce before the actor moves on to the next one. Stops one broad term from
consuming the entire run budget. `0` means no per-keyword limit.

These sit alongside the existing address-level deduplication: *Skip previous
runs* prevents re-pushing an individual mailbox, while *Skip duplicate keywords*
prevents re-running the search at all.

# Actor input Schema

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

A list of keywords or queries to search for.

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

Location to filter search results.

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

List of custom email domains

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

Maximum number of emails to collect. The scraper will stop once this limit is reached. Setting a higher limit allows for more potential results but doesn't guarantee reaching that number. This helps save costs by controlling scraping time.

## `decodeProtectedEmails` (type: `boolean`):

Read addresses the page hides behind Cloudflare protection or HTML entities. These are invisible to a plain text scan.

## `decodeWrittenEmails` (type: `boolean`):

Read addresses written to defeat scrapers, such as 'name \[at] example \[dot] com'.

## `decodeEncodedEmails` (type: `boolean`):

Read addresses stored base64-encoded in the page markup.

## `mergeAliasDuplicates` (type: `boolean`):

Collapse different spellings that reach the same inbox (e.g. j.o.h.n+news@gmail.com and john@gmail.com) into a single result, so you are not billed twice for one lead.

## `skipPreviousRuns` (type: `boolean`):

Do not return leads that an earlier run of this Actor already returned. Skipped leads are never charged.

## `duplicateHandling` (type: `string`):

What to do when several spellings reach the same inbox: merge them into one result, keep them apart but flag them, or keep everything as found.

## `skipDuplicateKeywords` (type: `boolean`):

Remember every keyword this actor completes and skip it next time. Ideal for a scheduled run over a fixed keyword list - you only pay for ground you have not covered. A keyword searched against a different set of email domains counts as new work, not a duplicate.

## `resetKeywordHistory` (type: `boolean`):

Clear the remembered keywords before this run starts, so everything is treated as new again. Use after changing your target list.

## `maxEmailsPerKeyword` (type: `integer`):

Stop collecting for a keyword once it has produced this many results, then move on to the next one. Keeps one broad term from consuming the whole run. Leave at 0 for no per-keyword limit.

## Actor input object example

```json
{
  "keywords": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "decodeProtectedEmails": true,
  "decodeWrittenEmails": true,
  "decodeEncodedEmails": true,
  "mergeAliasDuplicates": true,
  "skipPreviousRuns": false,
  "duplicateHandling": "merge",
  "skipDuplicateKeywords": false,
  "resetKeywordHistory": false,
  "maxEmailsPerKeyword": 0
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

# 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": [
        "manager",
        "founder"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("parse-point/dribbble-email-scraper-lightning-fast-and-accurate").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": [
        "manager",
        "founder",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("parse-point/dribbble-email-scraper-lightning-fast-and-accurate").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": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ]
}' |
apify call parse-point/dribbble-email-scraper-lightning-fast-and-accurate --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,parse-point/dribbble-email-scraper-lightning-fast-and-accurate"
        }
    }
}

```

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/xZN0rUheMSpeYw4f2/builds/fteulpIu0GPTOGbNq/openapi.json