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

# Findymail Find Phone: Inputs, Cost & CLI Example

> Find someone's phone number from a business profile URL. 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=findymail_find_phone:{"linkedin_url":"{{linkedin_url}}"}' --json
```

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

## Input Schema

| Name                   | Type     | Required | Default | Description                                                                                                                                      |
| ---------------------- | -------- | -------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| `payload.linkedin_url` | `string` | Yes      |         | Person's business profile URL. (can be full URL "[https://linkedin.com/in/johndoe](https://linkedin.com/in/johndoe)" or username only "johndoe") |

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

  ### Input JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "Find someone's phone number from a business profile URL. Uses 10 finder credits if a phone is found. For legal reasons, requests for EU citizens will not return any result.",
    "properties": {
      "linkedin_url": {
        "type": "string",
        "description": "Person's business profile URL. (can be full URL \"https://linkedin.com/in/johndoe\" or username only \"johndoe\")"
      }
    },
    "required": [
      "linkedin_url"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Output Schema

| Name          | Type     | Required | Default | Description                                    |
| ------------- | -------- | -------- | ------- | ---------------------------------------------- |
| `result.data` | `object` | Yes      |         | Provider response payload.                     |
| `result.meta` | `object` | No       |         | Additional response metadata (status, paging). |

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

  ### Output JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "Standard tool result payload.",
    "properties": {
      "data": {
        "description": "Provider response payload.",
        "anyOf": [
          {
            "type": "object",
            "properties": {
              "phone": {
                "type": "string",
                "description": "The phone number in E.164 format (e.g. +1234567890), or null if not found. Only available for US numbers."
              },
              "line_type": {
                "type": "string",
                "description": "The type of phone line (e.g. \"Mobile\", \"Landline\"), or null if not found."
              }
            },
            "additionalProperties": false
          },
          {
            "type": "object",
            "description": "Phone not found",
            "properties": {
              "phone": {
                "type": "string",
                "description": "The phone number in E.164 format (e.g. +1234567890), or null if not found. Only available for US numbers."
              },
              "line_type": {
                "type": "string",
                "description": "The type of phone line (e.g. \"Mobile\", \"Landline\"), or null if not found."
              }
            },
            "additionalProperties": false
          }
        ]
      },
      "meta": {
        "type": "object",
        "description": "Additional response metadata (status, paging).",
        "additionalProperties": true
      }
    },
    "required": [
      "data"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Advanced: Direct CLI

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

```bash theme={null}
deepline tools execute findymail_find_phone --payload '{
  "linkedin_url": "string"
}' --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: `6.86` per pricing unit.
* Billing mode: `post_deduct`.