# Employee Emails and Phones at a Company by Domain

**Use case:** 

The contacts tier of the company employees search: directors, VPs and C-level at one company, found by its website domain, each with an email on record and any phone and social links. Must have email delivers and charges only employees who have an address; the rest are counted free in one note row. Replace gong.io with your target and widen the roles if needed.

## Input

```json
{
  "companies": [
    "gong.io"
  ],
  "roles": [
    "director",
    "vp",
    "cxo"
  ],
  "profileDetail": "contacts",
  "mustHave": [
    "email"
  ],
  "compact": false,
  "titleContains": [],
  "titleExcludes": [],
  "excludeLowSignal": false,
  "maxRows": 100
}
```

## Output

```json
{
  "_status": {
    "label": "Status",
    "format": "string"
  },
  "_input": {
    "label": "Input",
    "format": "object"
  },
  "fullName": {
    "label": "Name",
    "format": "string"
  },
  "title": {
    "label": "Title",
    "format": "string"
  },
  "seniority": {
    "label": "Seniority",
    "format": "text"
  },
  "headline": {
    "label": "Headline",
    "format": "string"
  },
  "locality": {
    "label": "City",
    "format": "string"
  },
  "countryCode": {
    "label": "Country",
    "format": "string"
  },
  "hasPersonalEmail": {
    "label": "Personal email",
    "format": "boolean"
  },
  "hasWorkEmail": {
    "label": "Work email",
    "format": "boolean"
  },
  "lowSignal": {
    "label": "Low signal",
    "format": "boolean"
  },
  "profileUrl": {
    "label": "Profile",
    "format": "string"
  },
  "email": {
    "label": "Best email",
    "format": "string"
  },
  "emailType": {
    "label": "Email type",
    "format": "string"
  },
  "phone": {
    "label": "Phone",
    "format": "string"
  },
  "_detail": {
    "label": "Detail tier",
    "format": "string"
  },
  "_note": {
    "label": "Note",
    "format": "string"
  },
  "_error": {
    "label": "Details",
    "format": "string"
  }
}
```

## How it works

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

The LinkedIn Company Employees Scraper — Emails, Phones, by Domain Actor is ready to run with the inputs already set for "Employee Emails and Phones at a Company by Domain". [Sign up or log in](https://console.apify.com/create-task-from-example/KGJwhLG9RxkVaHeeR) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Employee Emails and Phones at a Company by Domain" task

The LinkedIn Company Employees Scraper — Emails, Phones, by Domain Actor will start running based on the input automatically. You can also change all the input fields, like companies, seniority roles (optional), and more, to match your specific use case.

### 3. Receive the "Employee Emails and Phones at a Company by Domain" 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 status, input, 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 "Employee Emails and Phones at a Company by Domain" task via API](https://apify.com/b2bsearch/company-employees.md).

## FAQ

### What contacts does the employee emails task return?

The employee emails task returns each employee's emails on record, personal and work, with phone numbers and X, GitHub or Facebook links where present, plus title, seniority, city and LinkedIn URL.

### Are employees without an email charged?

Must have is set to email in the employee emails task, so employees without an address are skipped for free and counted in one note row. The price per 1,000 delivered is on the Actor's Pricing tab.

### How do I keep only current work addresses?

Set Must have to work email at the current employer in the employee emails task. Addresses at a past employer then do not qualify, which keeps bounces down for outbound.

### Can I run the employee emails task on many accounts at once?

Put one domain per line in Companies. The employee emails task works through them in order until Max rows is reached, up to 10,000 people per run on the contacts tier.

## About this Actor

This example demonstrates how to use [LinkedIn Company Employees Scraper — Emails, Phones, by Domain](https://apify.com/b2bsearch/company-employees.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/b2bsearch/company-employees.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/b2bsearch/company-employees.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`).
