# Company Contacts Finder: Emails, Phones, Socials & DNS (`hirepulse/company-contact-details-finder`) Actor

Find public company emails, phone numbers, LinkedIn and social profiles from website domains. Optionally inspect MX, SPF and DMARC records and email-provider signals. Structured JSON for B2B contact research, lead enrichment, n8n, Make and Apify MCP.

- **URL**: https://apify.com/hirepulse/company-contact-details-finder.md
- **Developed by:** [HirePulse](https://apify.com/hirepulse) (community)
- **Categories:** Lead generation, Agents
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.40 / 1,000 domain with contacts

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
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

## Company Contact Finder: Emails, Phones, Socials & DNS

Find publicly listed business contact information from company websites. Export emails, phone numbers, social links and optional email-infrastructure observations in a company record.

### What you get

- Collect publicly visible email addresses, phone numbers and contact-page links.
- Find supported company social-profile URLs.
- Optionally inspect MX, SPF, DMARC and email-provider signals.

### Quick start

Edit the sample target in Apify Console, or pass an explicit target through the API:

```json
{
  "domains": [
    "linear.app"
  ],
  "include_dns": true,
  "use_paid_upstream": false
}
```

Results are written to the default dataset. Use the overview dataset view to inspect records and export available columns as JSON, CSV or Excel.

### Captured output example

Selected fields from an earlier validation run; these values are not current measurements.

```json
{
  "domain": "linear.app",
  "status": "ok",
  "linkedin": null,
  "twitter": "https://x.com/linear"
}
```

### Sources and coverage

Only publicly accessible information is extracted. DNS/MX records do not verify that an individual mailbox exists or will accept email. Missing or blocked pages are reported without inventing contact details.

The default uses public or platform-native sources with external paid data providers disabled. Apify Actor events and platform usage are separate from external API costs. Unsupported or unavailable fields are reported honestly; this is not a guarantee of complete source coverage.

### Pricing

Published standard event rates (before plan discounts):

| Event | USD per event | Meaning |
|---|---:|---|
| `apify-actor-start` | $5e-05 | Actor Start |
| `domain-with-contacts` | $0.003 | Domain with contacts |

Startup events, when configured, are separate from result events. Result-event charging follows the Actor's eligibility and useful-output rules; public fallback or diagnostic outputs may be uncharged. The live Pricing tab is authoritative. Set a maximum total charge before starting a run.

### API, MCP and workflow integrations

Actor ID: `hirepulse/company-contact-details-finder`. Run this Actor through Apify API or its official client libraries. Connect it to n8n or Make using the Apify integration, or expose it to AI agents through Apify's MCP server. This Actor does not host its own MCP server. API calls must supply the required target; Console prefill is an editable example, not a hidden API target.

### Use cases and data coverage

| Dimension | Coverage |
|---|---|
| Use cases | B2B contact research, lead enrichment and company website research |
| Target sources | Company websites and public DNS |
| Output | Structured JSON records in an Apify dataset |

Store categorization is assigned by Apify. No search position, AI recommendation, completeness or fixed runtime is guaranteed.

### Related HirePulse tools

- [ats-job-pulse](https://apify.com/hirepulse/ats-job-pulse)
- [google-jobs-scraper](https://apify.com/hirepulse/google-jobs-scraper)
- [domain-seo-overview](https://apify.com/hirepulse/domain-seo-overview)

# Actor input Schema

## `domains` (type: `array`):

Required. Company websites, one per item, up to 200 per run. Full URLs and email addresses are fine too (the domain is taken). Example: \["stripe.com", "linear.app"].

## `include_dns` (type: `boolean`):

Add MX records, email provider (Google Workspace, Microsoft 365, ...), SPF and DMARC policy for each domain. Default: true.

## `use_paid_upstream` (type: `boolean`):

Off by default. Supported paid sources also require the owner-controlled HIREPULSE_ALLOW_PAID_UPSTREAM=1 environment setting. Keep false for all quality and smoke checks.

## Actor input object example

```json
{
  "domains": [
    "linear.app"
  ],
  "include_dns": true,
  "use_paid_upstream": false
}
```

# Actor output Schema

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

One record per submitted domain, including lookup status, public contact details and optional email DNS signals.

## `summary` (type: `string`):

Counts of requested and checked domains, results with email, charged results and run limit indicators.

# 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 = {
    "domains": [
        "linear.app"
    ],
    "include_dns": true,
    "use_paid_upstream": false
};

// Run the Actor and wait for it to finish
const run = await client.actor("hirepulse/company-contact-details-finder").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 = {
    "domains": ["linear.app"],
    "include_dns": True,
    "use_paid_upstream": False,
}

# Run the Actor and wait for it to finish
run = client.actor("hirepulse/company-contact-details-finder").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 '{
  "domains": [
    "linear.app"
  ],
  "include_dns": true,
  "use_paid_upstream": false
}' |
apify call hirepulse/company-contact-details-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hirepulse/company-contact-details-finder"
        }
    }
}
```

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/4q7K8so0eToIihZrm/builds/OOfhZPrfhmgl8GqIa/openapi.json