# Fbcci Email Scraper (`email_scraper/fbcci-email-scraper`) Actor

Fbcci Email Scraper extracts publicly available email addresses from Fbcci using targeted keywords, locations, and custom email domains. Build structured contact datasets for B2B lead research, supplier discovery, business research, market analysis, and contact collection.

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

## Pricing

from $1.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

### Fbcci Email Scraper

The **Fbcci Email Scraper** is an Apify Actor designed to find publicly available email addresses associated with relevant results from **fbcci.org** using targeted search keywords and optional location filters.

Instead of manually searching through many search results, you can provide multiple keywords such as `manufacturer`, `exporter`, `supplier`, or other relevant business terms. The Actor searches for matching Fbcci results and extracts email addresses that match the email domains you specify.

Each collected result is returned as structured dataset data containing the search keyword, result title, description, URL, and extracted email address.

The Actor is useful for business research, contact discovery, market research, supplier research, lead research, and other workflows that require structured email data from publicly available search results.

### What Is the Fbcci Email Scraper?

The **Fbcci Email Scraper** automates targeted email discovery from search results related to Fbcci.

You provide one or more keywords and can optionally specify a country, city, or other region. You can also choose which email domains to search for, such as `@gmail.com`, `@yahoo.com`, or `@outlook.com`.

The Actor then processes the configured keyword and email-domain combinations and returns matching email addresses together with contextual information from the relevant search result.

The workflow can be summarized as:

**Keywords + optional location + email domains → relevant Fbcci search results → email extraction → structured dataset**

Results are pushed to the Apify dataset as they are collected, making the output suitable for further review and analysis.

### 🔍 Key Features

| Feature                        | Description                                                     | User Benefit                                                    |
| ------------------------------ | --------------------------------------------------------------- | --------------------------------------------------------------- |
| Keyword-based search           | Search Fbcci results using one or more keywords or queries.     | Target specific industries, professions, businesses, or topics. |
| Location filtering             | Optionally add a country, state, or city.                       | Narrow searches to a geographic area.                           |
| Custom email domains           | Specify one or multiple email-domain suffixes.                  | Focus collection on the types of addresses you need.            |
| Per-combination email target   | Set `maxEmails` for each keyword + domain combination.          | Control the depth of each search combination.                   |
| Exclude words                  | Skip result descriptions containing specified words or phrases. | Reduce unwanted results.                                        |
| Structured dataset output      | Results contain keyword, title, description, URL, and email.    | Make collected data easier to review and process.               |
| Duplicate prevention           | Previously collected email addresses are not added again.       | Reduce duplicate email records.                                 |
| Incremental dataset collection | Results are pushed as they are found.                           | Make collected results available progressively.                 |
| Resume support                 | Progress is retained during the run.                            | Help continue processing after an interruption.                 |

### 📊 What Data Can You Extract?

The Actor returns five primary output fields for each collected email.

- **Keyword** — The keyword or query associated with the search result.
- **Title** — The title of the relevant search result.
- **Description** — The available search-result description containing the matching contact information.
- **URL** — The URL associated with the search result.
- **Email** — The email address matching one of your configured email-domain suffixes.

This combination provides both the extracted contact information and contextual search data that can help you understand where the email was found.

The Actor focuses on email addresses that are publicly available through relevant search results. It should therefore be treated as a targeted contact discovery and research tool rather than a guarantee that every Fbcci profile contains an email address.

### Why Use This Actor?

Manually searching for business contacts can require repeatedly entering different terms, checking results, identifying relevant descriptions, and recording email addresses.

The **Fbcci Email Scraper** turns that repetitive search process into a configurable Actor run.

You can use specific search terms to target particular business categories. For example, instead of searching only for a broad term such as `business`, you can create more focused searches such as:

- `manufacturer`
- `exporter`
- `supplier`
- `garment manufacturer`
- `textile exporter`
- `software company`

Combining several related keywords can provide broader search coverage while keeping the search intent targeted.

### 🚀 Benefits

The Actor provides several practical benefits for structured contact research.

- **Automated collection** — Reduce repetitive manual searching for matching email addresses.
- **Targeted discovery** — Use specific keywords to focus on relevant results.
- **Geographic targeting** — Add a location when research needs to focus on a particular area.
- **Flexible domains** — Search for addresses from selected email providers or domains.
- **Structured results** — Receive consistent fields for easier analysis.
- **Multiple keyword support** — Process several search terms within one run.
- **Filtering control** — Exclude descriptions containing unwanted words or phrases.
- **Duplicate reduction** — The Actor tracks collected email addresses to avoid adding the same address repeatedly.

### 🔍 How to Use the Fbcci Email Scraper

A typical run requires only a few configuration steps.

1. Enter one or more relevant keywords in the `keywords` field.
2. Optionally enter a country, state, city, or other geographic term in `location`.
3. Add the email domains you want to target in `customDomains`.
4. Set `maxEmails` according to the amount of data you want to target for each keyword + domain combination.
5. Optionally configure `excludeWords` to remove unwanted result descriptions.
6. Start the Actor.
7. Review the structured results in the Apify dataset.

For a first run, it is useful to start with a small number of keywords and a modest email target. You can then refine the search terms based on the quality and quantity of the returned results.

### 📥 Input

The Actor accepts a JSON object containing search keywords and optional filtering and collection settings.

The `keywords` field is required. The remaining fields provide additional control over geographic targeting, email-domain selection, collection depth, and result filtering.

### Input Fields

| Field           | Type             | Required | Default                        | Description                                                                                  |
| --------------- | ---------------- | -------- | ------------------------------ | -------------------------------------------------------------------------------------------- |
| `keywords`      | Array of strings | Yes      | `["manufacturer", "exporter"]` | Keywords or queries used to find relevant Fbcci results.                                     |
| `location`      | String           | No       | `""`                           | Optional country, state, or city used to narrow the search.                                  |
| `customDomains` | Array of strings | No       | `["@gmail.com"]`               | Email-domain suffixes to search for.                                                         |
| `maxEmails`     | Integer          | No       | `5`                            | Target number of emails for each keyword + domain combination. Minimum `1`, maximum `10000`. |
| `excludeWords`  | Array of strings | No       | `[]`                           | Words or phrases that cause a matching result description to be skipped.                     |

#### Keywords

`keywords` accepts multiple search terms. More specific terms can help target a particular type of business or contact.

For example:

- `manufacturer`
- `exporter`
- `supplier`
- `garment manufacturer`

The Actor processes the configured keywords as separate searches.

#### Location

`location` is optional. Leave it empty when you do not need geographic filtering.

Examples include:

- `Bangladesh`
- `Dhaka`
- `Chattogram`

A location can help focus search results around a particular geographic area.

#### Custom Email Domains

`customDomains` accepts email-domain suffixes such as:

- `@gmail.com`
- `@yahoo.com`
- `@outlook.com`
- `@hotmail.com`

You can also specify other domain suffixes when appropriate.

#### Max Emails

`maxEmails` controls the target for each **keyword + domain combination**, rather than acting as one shared target across every configured combination.

For example, with three keywords, two email domains, and `maxEmails` set to `20`, the Actor works through the six keyword/domain combinations with a target of up to 20 emails for each combination, subject to available results and duplicate filtering.

The configured value must be between `1` and `10000`.

On free-tier runs, the Actor applies a maximum configured collection limit of 100 emails for a combination when the requested value exceeds that free-tier ceiling.

#### Exclude Words

`excludeWords` lets you skip search results whose descriptions contain unwanted terms.

Single words are matched case-insensitively as whole words. Multi-word phrases are matched case-insensitively as phrases.

For example:

- `crypto`
- `onlyfans`
- `unrelated service`

If a result description matches an exclusion term, that result is skipped rather than having an email extracted from it.

### Input Example

```json
{
  "keywords": [
    "manufacturer",
    "exporter",
    "supplier"
  ],
  "location": "Bangladesh",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com",
    "@outlook.com"
  ],
  "maxEmails": 10,
  "excludeWords": [
    "crypto",
    "onlyfans"
  ]
}
```

### 📤 Output

The Actor stores collected results in the **Fbcci Emails Dataset**.

Each dataset item contains the keyword that produced the result, contextual search information, the result URL, and the matching email address.

The output is designed to provide enough context to identify the source of each contact rather than returning an email address alone.

Email addresses are deduplicated during collection, so the same email address is not intentionally added repeatedly when encountered in multiple results.

### Output Fields

| Field         | Description                                                     |
| ------------- | --------------------------------------------------------------- |
| `keyword`     | The keyword used for the search that produced the result.       |
| `title`       | Title of the relevant search result.                            |
| `description` | Search-result description associated with the result.           |
| `url`         | URL of the relevant search result.                              |
| `email`       | Extracted email address matching the configured domain pattern. |

### Output Example

```json
{
  "keyword": "manufacturer",
  "title": "Example Manufacturer",
  "description": "Example business description with contact@example.com",
  "url": "https://fbcci.org/example-profile",
  "email": "contact@example.com"
}
```

The values above are illustrative examples of the output structure. Actual titles, descriptions, URLs, and email addresses depend on the available search results.

### Use Cases

The **Fbcci Email Scraper** can support several research and data-collection workflows.

- **Business lead research** — Find publicly available business contact information associated with targeted terms.
- **Supplier research** — Search for manufacturers, exporters, suppliers, and related business categories.
- **Market research** — Build structured datasets around specific business or industry keywords.
- **B2B research** — Identify publicly available email contacts connected with relevant business searches.
- **Geographic research** — Combine business keywords with a country or city.
- **Industry research** — Search terms related to a particular sector and collect matching contact records.
- **Dataset creation** — Build structured contact datasets for later analysis.
- **Business intelligence** — Combine contact information with titles, descriptions, and URLs for research.
- **Contact discovery** — Identify publicly available email addresses associated with relevant search results.
- **Research automation** — Repeat structured searches without manually reviewing every search result.

### Advantages

The Actor is particularly useful when your research requires multiple combinations of search terms and email domains.

Its configurable input makes it possible to change the search strategy without changing the Actor itself. You can target broad business categories, narrow searches with location terms, select specific email domains, and exclude descriptions that are not relevant to your research.

The structured dataset also keeps the email address connected to its keyword, title, description, and URL, which provides useful context for subsequent review.

### Limitations

The Actor can only return email addresses that are available in the relevant search results and match the configured email-domain patterns.

A search target is not a guarantee that the requested number of emails will be found. Results can be lower when:

- A keyword is too narrow.
- The selected email domain is uncommon in the relevant results.
- A location filter significantly narrows the search.
- Relevant pages do not expose an email address in their available search-result description.
- Matching email addresses have already been collected.
- Search results do not contain additional relevant information.

The Actor should therefore be viewed as a targeted discovery tool rather than a guarantee of complete coverage of all contacts on Fbcci.

### Pros and Cons

| Pros                                    | Cons                                                    |
| --------------------------------------- | ------------------------------------------------------- |
| Supports multiple search keywords       | Results depend on publicly available search information |
| Optional geographic targeting           | Narrow searches may return fewer contacts               |
| Custom email-domain selection           | Not every relevant result contains an email address     |
| Exclude-word filtering                  | Requested email targets are not guaranteed              |
| Structured dataset output               | Duplicate email addresses are filtered                  |
| Per keyword + domain collection targets | Free-tier collection restrictions may apply             |
| Incremental dataset collection          | Search coverage depends on available results            |

### Comparison With Alternative Approaches

| Capability                | Fbcci Email Scraper         | Manual Search                            |
| ------------------------- | --------------------------- | ---------------------------------------- |
| Multiple keyword searches | Supported                   | Usually repeated manually                |
| Email-domain targeting    | Supported                   | Requires manual search configuration     |
| Location targeting        | Supported                   | Requires manual query construction       |
| Exclude-word filtering    | Supported                   | Usually manual                           |
| Structured output         | Dataset fields provided     | Manual formatting may be required        |
| Duplicate prevention      | Supported during collection | Must usually be handled manually         |
| Repeatable configuration  | Supported                   | Requires repeating the workflow manually |

This comparison describes workflow differences rather than claiming that the Actor is universally better than manual research.

### Best Practices

For better research workflows, consider the following practices:

- Use several specific keywords instead of relying on one broad term.
- Combine related business terms such as `manufacturer`, `exporter`, and `supplier` when appropriate.
- Use a location only when geographic targeting is important.
- Add multiple relevant email domains when broader email coverage is needed.
- Start with a smaller `maxEmails` value to evaluate the quality of results.
- Use `excludeWords` when certain categories of results should be removed.
- Review titles, descriptions, and URLs before using collected contact information.
- Validate important contacts before using them in business workflows.
- Increase the Apify run timeout when performing wider searches, as the configured Actor description specifies a default run timeout of 3600 seconds.

### Troubleshooting

**Empty Results:** Try broader or more specific keywords, remove an overly restrictive location, or add additional email domains.

**Too Few Emails:** A keyword may have limited relevant results. Try related terms such as `supplier`, `manufacturer`, `exporter`, or a more specific industry term.

**Location Produces Few Results:** Remove the location filter or use a broader geographic term.

**Missing Email Addresses:** A relevant result does not necessarily expose an email address in the available search description. This is expected for some results.

**Unexpected Results:** Review the keyword and location combination. Very broad keywords can produce less targeted results.

**Excluded Results:** Check `excludeWords` if expected results are missing. A matching exclusion term causes the complete result description to be skipped.

**Long Runs:** Wide searches involving many keywords and email domains may require additional run time. Consider starting with a smaller test configuration before expanding the run.

### Frequently Asked Questions

**What does the Fbcci Email Scraper do?**

The Fbcci Email Scraper searches for relevant Fbcci results using your keywords and extracts matching publicly available email addresses from the available search-result descriptions.

**What keywords can I use?**

You can use business, industry, professional, geographic, or other relevant search terms. Examples include `manufacturer`, `exporter`, `supplier`, and `software company`.

**Can I use multiple keywords?**

Yes. The `keywords` input is an array, so you can provide multiple search terms in one Actor run.

**Can I search a specific country or city?**

Yes. Use the optional `location` field to add a country, state, or city to the search.

**Can I choose which email domains are collected?**

Yes. The `customDomains` field lets you specify email-domain suffixes such as `@gmail.com`, `@yahoo.com`, and `@outlook.com`.

**What does `maxEmails` control?**

`maxEmails` sets the collection target for each keyword + email-domain combination. The requested amount is not a guarantee that that many emails will be available.

**What happens if I use exclude words?**

When a result description contains an excluded word or phrase, the result is skipped and no email is extracted from that description.

**Does the Actor return only email addresses?**

No. Each output record also includes the keyword, title, description, and URL associated with the result.

**Are duplicate emails returned?**

The Actor tracks collected email addresses and avoids intentionally adding the same email address again.

**Can the Actor return fewer emails than requested?**

Yes. The requested target depends on the available relevant search results, matching email addresses, filters, and duplicate prevention. A target is not a guarantee.

**Is the Actor suitable for automated research workflows?**

Yes. Its structured inputs and dataset output make it suitable for repeatable data-collection and research workflows within Apify.

### NLP Keywords

- Fbcci email scraper
- Fbcci email extraction
- Fbcci contact data
- Fbcci business contacts
- Fbcci lead research
- Fbcci email finder
- Fbcci contact discovery
- Fbcci data extraction
- Fbcci business research
- Fbcci supplier research
- Fbcci manufacturer search
- Fbcci exporter search
- Fbcci public contact information
- Fbcci email collection
- Fbcci structured data
- Fbcci business leads
- Fbcci search results
- Fbcci contact dataset
- Fbcci market research
- Fbcci B2B research

### Related Keywords

- Fbcci email scraper
- scrape Fbcci emails
- Fbcci contact scraper
- Fbcci lead scraper
- Fbcci email extractor
- Fbcci business email finder
- Fbcci supplier email search
- Fbcci manufacturer email search
- Fbcci exporter email search
- Fbcci business contact finder
- Fbcci B2B email scraper
- Fbcci company contact search
- Fbcci public email finder
- Fbcci business lead extraction
- Fbcci contact data extraction
- Fbcci email collection tool
- Fbcci business directory research
- Fbcci supplier research tool
- Fbcci exporter contact research
- Fbcci business email extraction

### Final Overview

The **Fbcci Email Scraper** provides a structured way to discover publicly available email addresses associated with relevant Fbcci search results.

By combining targeted keywords, optional geographic filtering, custom email domains, email targets, and exclusion terms, you can create focused searches for business research and contact discovery.

The returned dataset includes `keyword`, `title`, `description`, `url`, and `email`, giving you both the extracted contact and useful context about the result.

For the best workflow, start with focused keywords, test a small configuration, review the returned data, and then expand your keywords, domains, or geographic targeting when broader coverage is required.

*Contact me:* <Alphascraper69@gmail.com>

# Actor input Schema

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

A list of keywords or queries to search for.

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

Optional country, state or city used to narrow the search. Leave it empty to search without a geographic filter.

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

List of custom email domains

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

How many addresses each search keyword + domain suffix combination may collect before the finder moves on to the next one. This is a per-combination target, not a run-wide total: with 3 keyword and 2 Domains and a limit of 20, the run works through all 6 combinations and aims for up to 20 addresses in each, so up to 120 overall. Lower values finish sooner and cost less; higher values dig deeper but never guarantee a fuller result, since the run can only find what is publicly listed.

## `excludeWords` (type: `array`):

Words or phrases you do not want to see.

## Actor input object example

```json
{
  "keywords": [
    "manufacturer",
    "exporter"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com"
  ],
  "maxEmails": 5,
  "excludeWords": []
}
```

# 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": [
        "manufacturer",
        "exporter"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com"
    ],
    "excludeWords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("email_scraper/fbcci-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": [
        "manufacturer",
        "exporter",
    ],
    "location": "",
    "customDomains": ["@gmail.com"],
    "excludeWords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("email_scraper/fbcci-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": [
    "manufacturer",
    "exporter"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com"
  ],
  "excludeWords": []
}' |
apify call email_scraper/fbcci-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,email_scraper/fbcci-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/GpDnUk84uD4Bfltuq/builds/fRs6itdTK2iCXcgOa/openapi.json