> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Apollo Enrich Person: Inputs, Cost & CLI Example
> Legacy alias for resolving one person via Apollo ID/email/name matching. Includes inputs, outputs, costs, and Deepline CLI examples for GTM automation.
## Run in Enrichment Spreadsheet
Use this function as a column step in `deepline enrich`.
```bash theme={null}
deepline enrich --input leads.csv --output leads.enriched.csv --with 'result=apollo_enrich_person:{}' --json
```
Map payload values to spreadsheet columns with `{{column_name}}` placeholders.
## Input Schema
| Name | Type | Required | Default | Description |
| -------------------------------- | --------- | -------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `payload.name` | `string` | No | | Person's full name. |
| `payload.email` | `string` | No | | Person's email address. |
| `payload.hashed_email` | `string` | No | | Person's MD5-hashed email address. |
| `payload.first_name` | `string` | No | | Person's first name. |
| `payload.last_name` | `string` | No | | Person's last name. |
| `payload.linkedin_url` | `string` | No | | Person's LinkedIn profile URL. |
| `payload.domain` | `string` | No | | Company domain (e.g., 'apollo.io'). |
| `payload.organization_name` | `string` | No | | Employer/company name. |
| `payload.id` | `string` | No | | Apollo person ID from a prior lookup. `apollo_people_match` requires another identifier with `id`; use `apollo_bulk_people_enrichment` with `details: [{ id }]` for id-only lookup. |
| `payload.reveal_personal_emails` | `boolean` | No | `true` | When true, attempt personal email reveal (credit-consuming). WARNING: Apollo primarily returns work emails even with this flag (\~70% work, \~30% personal). Do NOT use Apollo for personal email discovery - use Fullenrich or BetterContact instead. |
Show raw input schema
### Input JSON Schema
```json theme={null}
{
"type": "object",
"description": "Apollo people match input. Supports id-assisted matching, but id-only lookup belongs in apollo_bulk_people_enrichment. `reveal_personal_emails` defaults to true.",
"properties": {
"name": {
"type": "string",
"description": "Person's full name."
},
"email": {
"type": "string",
"description": "Person's email address."
},
"hashed_email": {
"type": "string",
"description": "Person's MD5-hashed email address."
},
"first_name": {
"type": "string",
"description": "Person's first name."
},
"last_name": {
"type": "string",
"description": "Person's last name."
},
"linkedin_url": {
"type": "string",
"description": "Person's LinkedIn profile URL."
},
"domain": {
"type": "string",
"description": "Company domain (e.g., 'apollo.io')."
},
"organization_name": {
"type": "string",
"description": "Employer/company name."
},
"id": {
"type": "string",
"description": "Apollo person ID from a prior lookup. `apollo_people_match` requires another identifier with `id`; use `apollo_bulk_people_enrichment` with `details: [{ id }]` for id-only lookup."
},
"reveal_personal_emails": {
"type": "boolean",
"description": "When true, attempt personal email reveal (credit-consuming). WARNING: Apollo primarily returns work emails even with this flag (~70% work, ~30% personal). Do NOT use Apollo for personal email discovery - use Fullenrich or BetterContact instead.",
"default": true
}
},
"additionalProperties": false
}
```
## Output Schema
| Name | Type | Required | Default | Description |
| ------------- | -------- | -------- | ------- | ------------------------------------------------------------- |
| `result.data` | `object` | Yes | | Apollo people match payload with a top-level `person` object. |
| `result.meta` | `record` | No | | Additional response metadata (status, paging). |
Show raw output schema
### Output JSON Schema
```json theme={null}
{
"type": "object",
"description": "Legacy alias for Apollo people match result.",
"properties": {
"data": {
"type": [
"object",
"null"
],
"description": "Apollo people match payload with a top-level `person` object.",
"properties": {
"person": {
"type": "object",
"properties": {
"id": {
"type": "string"
},
"first_name": {
"type": "string"
},
"last_name": {
"type": "string"
},
"name": {
"type": "string"
},
"email": {
"type": "string"
},
"email_status": {
"type": "string"
},
"linkedin_url": {
"type": "string"
},
"title": {
"type": "string"
},
"organization": {
"type": "object",
"properties": {
"id": {
"type": "string"
},
"name": {
"type": "string"
},
"primary_domain": {
"type": "string"
}
},
"additionalProperties": false
},
"organization_id": {
"type": "string"
}
},
"additionalProperties": false
}
},
"required": [
"person"
],
"additionalProperties": false
},
"meta": {
"type": "object",
"description": "Additional response metadata (status, paging).",
"additionalProperties": {}
}
},
"required": [
"data"
],
"additionalProperties": false
}
```
## Advanced: Direct CLI
Use direct execution for single payload debugging.
```bash theme={null}
deepline tools execute apollo_enrich_person --payload '{}' --json
```
### CLI flags
| Flag | Description |
| --------------------------- | --------------------------------------------------- |
| `--json` | Print machine-readable output. |
| `--wait` | Wait for terminal provider status when supported. |
| `--debug` | Enable wait mode with additional status/log output. |
| `--wait-timeout SECONDS` | Max seconds to wait in wait mode. |
| `--poll-interval SECONDS` | Polling interval in seconds during wait mode. |
| `--timeout SECONDS` | Request timeout in seconds. |
| `--connect-timeout SECONDS` | Connection timeout in seconds. |
## Cost
* Pricing model: `per_result` (per result).
* Estimated Deepline credits: `0.17` per pricing unit.
* Billing mode: `post_deduct`.