# ContactOut Node

> Looks up people and company data: headcounts, people and company search, contact details, email and phone status, and decision makers.

**URL:** https://caywork.com/learn/docs/node/contactout-node

## Content

The **ContactOut Node** looks up people and company data: headcounts, searches, contact details, work and personal emails, phone numbers, and decision makers. The node is a tool connector: your agent chooses one of 14 actions and supplies the arguments at run time. ContactOut is a direct REST integration, not an MCP connection, and the platform holds the API key, so there is nothing to connect per user.

## Parameters
The agent picks the action and supplies its arguments at run time.

### Required Arguments
| Action | Required arguments |
| --- | --- |
| `people_count` | At least one people-search filter (for example `job_title`, `company`, `location`, `skills`). |
| `people_search` | At least one people-search filter. |
| `people_enrich` | One identifier: `linkedin_url`, `email`, `phone`, `full_name`, or `first_name` plus `last_name`. |
| `linkedin_enrich` | `profile` (LinkedIn profile URL). |
| `email_enrich` | `email`. |
| `contact_info` | `profile` (LinkedIn profile URL). |
| `decision_makers` | One identifier: `linkedin_url`, `domain`, or `name`. |
| `company_search` | At least one company-search filter (for example `name`, `domain`, `industry`, `location`). |
| `company_domain` | `domains` (non-empty list of domains, maximum 30). |
| `email_to_linkedin` | `email`. |
| `email_verify` | `email`. |
| `personal_email_status` | `profile` (LinkedIn profile URL). |
| `work_email_status` | `profile` (LinkedIn profile URL). |
| `phone_status` | `profile` (LinkedIn profile URL). |

### Optional Arguments
| Action | Optional arguments |
| --- | --- |
| `people_count` | Additional people-search filters; narrower filters reduce the count. |
| `people_search` | `page_size` (default 5, clamped to 1–25), `reveal_info` (default false). |
| `people_enrich` | Any further identifiers or people-search filters to disambiguate the match. |
| `linkedin_enrich` | None. |
| `email_enrich` | None. |
| `contact_info` | `include_phone` (default false), `email_type`. |
| `decision_makers` | `reveal_info` (default false). |
| `company_search` | Additional company-search filters; narrower filters reduce the result set. |
| `company_domain` | None; send at most 30 domains per call. |
| `email_to_linkedin` | None. |
| `email_verify` | None. |
| `personal_email_status` | None. |
| `work_email_status` | None. |
| `phone_status` | None. |

## Practical Use Cases
1. **List building**: Start with `people_count` to size a filter, then `people_search` to page through matches.
2. **Contact enrichment**: Enrich a known profile or email with `people_enrich`, `linkedin_enrich`, or `email_enrich`, then fetch work and personal addresses with `contact_info`.
3. **Lead qualification**: Verify a work email with `email_verify` and check its status with `work_email_status` before adding it to a sequence.
4. **Account mapping**: Run `company_search` or `company_domain` to find accounts, then `decision_makers` to find the people worth contacting.
5. **Reverse lookup**: Turn a known email into a LinkedIn profile with `email_to_linkedin`.

## Notes
* Actions that reveal contact details consume ContactOut credits. Size filters with `people_count` before paging through `people_search`.
* `page_size` is clamped to 1–25 whatever the agent sends; keep pages small while testing.
\