> ## 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.

# Crustdata Enrich Contact: Inputs, Cost & CLI Example

> Enriching one person from an email or profile identifier. Includes inputs, outputs, pricing notes, Deepline CLI examples, and GTM automation guidance.

## Run in Enrichment Spreadsheet

<Info>
  Use this function as a column step in `deepline enrich`.
</Info>

```bash theme={null}
deepline enrich --input leads.csv --output leads.enriched.csv --with 'result=crustdata_enrich_contact:{"email":"jane.doe@example.com"}' --json
```

<Tip>
  Map payload values to spreadsheet columns with `{{column_name}}` placeholders.
</Tip>

## Input Schema

| Name                           | Type     | Required | Default | Description                                                                                                             |
| ------------------------------ | -------- | -------- | ------- | ----------------------------------------------------------------------------------------------------------------------- |
| `payload.email`                | `string` | No       |         | Business/work email address to enrich. Personal webmail domains such as gmail.com are rejected before execution.        |
| `payload.linkedin_url`         | `string` | No       |         | LinkedIn profile URL to enrich.                                                                                         |
| `payload.linkedin_profile_url` | `string` | No       |         | Alias for linkedin\_url. Accepted for compatibility with LinkedIn profile URL fields returned by provider/search tools. |

<details>
  <summary>Show raw input schema</summary>

  ### Input JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "Lookup a person by email or LinkedIn URL.",
    "properties": {
      "email": {
        "type": "string",
        "description": "Business/work email address to enrich. Personal webmail domains such as gmail.com are rejected before execution.",
        "minLength": 1
      },
      "linkedin_url": {
        "type": "string",
        "description": "LinkedIn profile URL to enrich.",
        "minLength": 1
      },
      "linkedin_profile_url": {
        "type": "string",
        "description": "Alias for linkedin_url. Accepted for compatibility with LinkedIn profile URL fields returned by provider/search tools.",
        "minLength": 1
      }
    },
    "additionalProperties": false
  }
  ```
</details>

## Output Schema

| Name            | Type     | Required | Default | Description |
| --------------- | -------- | -------- | ------- | ----------- |
| `result.status` | `string` | Yes      |         |             |
| `result.result` | `array`  | Yes      |         |             |

<details>
  <summary>Show raw output schema</summary>

  ### Output JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "properties": {
      "status": {
        "type": "string"
      },
      "result": {
        "type": "array",
        "items": {
          "type": "object",
          "properties": {
            "name": {
              "type": "string"
            },
            "title": {
              "type": "string"
            },
            "headline": {
              "type": "string"
            },
            "email": {
              "type": "null"
            },
            "linkedin_profile_url": {
              "type": "string"
            },
            "linkedin_flagship_url": {
              "type": "string"
            },
            "location": {
              "type": "string"
            }
          },
          "required": [
            "name",
            "title",
            "headline",
            "email",
            "linkedin_profile_url",
            "linkedin_flagship_url",
            "location"
          ],
          "additionalProperties": true
        }
      }
    },
    "required": [
      "status",
      "result"
    ],
    "additionalProperties": true
  }
  ```
</details>

## Advanced: Direct CLI

<Info>
  Use direct execution for single payload debugging.
</Info>

```bash theme={null}
deepline tools execute crustdata_enrich_contact --payload '{
  "email": "jane.doe@example.com"
}' --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.4` per pricing unit.
* Billing mode: `post_deduct`.