# Scrape Emails From JS Sites With Browser Fallback

**Use case:** 

For modern JavaScript-rendered sites where a static crawl finds nothing: the browser fallback retries with a real browser to catch dynamically rendered contact and team pages. Raise pages per domain for thorough coverage.

## Input

```json
{
  "domains": [
    "https://vercel.com",
    "https://supabase.com"
  ],
  "names": [],
  "verifyEmails": true,
  "usePlaywrightFallback": true,
  "maxPagesPerDomain": 8,
  "includeContext": true,
  "fromAddress": "verify@example.com",
  "maxConcurrency": 5
}
```

## Output

```json
{
  "domain": {
    "label": "Domain"
  },
  "email": {
    "label": "Email"
  },
  "name": {
    "label": "Name"
  },
  "source": {
    "label": "Source"
  },
  "isRoleBased": {
    "label": "Role-based"
  },
  "confidence": {
    "label": "Confidence"
  },
  "smtp": {
    "label": "SMTP"
  },
  "mxFound": {
    "label": "MX"
  },
  "pattern": {
    "label": "Pattern"
  },
  "sourceUrl": {
    "label": "Found on",
    "format": "link"
  },
  "context": {
    "label": "Context"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The Email Finder Actor is ready to run with the inputs already set for "Scrape Emails From JS Sites With Browser Fallback". [Sign up or log in](https://console.apify.com/create-task-from-example/oLbtAYpsXPlz0DNpx) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Scrape Emails From JS Sites With Browser Fallback" task

The Email Finder Actor will start running based on the input automatically. You can also change all the input fields, like domains or urls, names to find (optional), and more, to match your specific use case.

### 3. Receive the "Scrape Emails From JS Sites With Browser Fallback" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as domain, email, name, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Scrape Emails From JS Sites With Browser Fallback" task via API](https://apify.com/fuze/email-finder-scraper.md).

## About this Actor

This example demonstrates how to use [Email Finder](https://apify.com/fuze/email-finder-scraper.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/fuze/email-finder-scraper.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

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 full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/fuze/email-finder-scraper.md

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`).