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

# Emailbison Update Lead: Inputs, Cost & CLI Example

> Update the details of a specific lead Fields passed in the request will be updated. Fields and custom variables not passed will be cleared.

## 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=emailbison_update_lead:{"lead_id":"{{lead_id}}","first_name":"{{first_name}}","email":"{{email}}"}' --json
```

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

## Input Schema

| Name                       | Type     | Required | Default | Description                                                        |
| -------------------------- | -------- | -------- | ------- | ------------------------------------------------------------------ |
| `payload.lead_id`          | `string` | Yes      |         | Optional parameter. int\|string The ID or email of the lead        |
| `payload.first_name`       | `string` | Yes      |         | The first name of the contact.                                     |
| `payload.last_name`        | `string` | No       |         | optional The last name of the contact.                             |
| `payload.email`            | `string` | Yes      |         | The email address of the contact. Must be in a valid email format. |
| `payload.title`            | `string` | No       |         | The title of the contact.                                          |
| `payload.company`          | `string` | No       |         | The company name of the contact.                                   |
| `payload.notes`            | `string` | No       |         | Additional notes about the contact.                                |
| `payload.custom_variables` | `array`  | No       |         | Array of custom variable objects                                   |

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

  ### Input JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "Update the details of a specific lead Fields passed in the request will be updated. Fields and custom variables not passed will be cleared.",
    "properties": {
      "lead_id": {
        "type": "string",
        "description": "Optional parameter. int|string The ID or email of the lead"
      },
      "first_name": {
        "type": "string",
        "description": "The first name of the contact."
      },
      "last_name": {
        "type": [
          "string",
          "null"
        ],
        "description": "optional The last name of the contact."
      },
      "email": {
        "type": "string",
        "description": "The email address of the contact. Must be in a valid email format."
      },
      "title": {
        "type": [
          "string",
          "null"
        ],
        "description": "The title of the contact."
      },
      "company": {
        "type": [
          "string",
          "null"
        ],
        "description": "The company name of the contact."
      },
      "notes": {
        "type": "string",
        "description": "Additional notes about the contact."
      },
      "custom_variables": {
        "type": "array",
        "description": "Array of custom variable objects",
        "items": {
          "type": [
            "object",
            "null"
          ],
          "properties": {
            "name": {
              "description": "name of the custom variable field"
            },
            "value": {
              "description": "value of the custom variable",
              "anyOf": [
                {
                  "type": "null"
                }
              ]
            }
          },
          "additionalProperties": false
        }
      }
    },
    "required": [
      "lead_id",
      "first_name",
      "email"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Output Schema

| Name          | Type     | Required | Default | Description                                    |
| ------------- | -------- | -------- | ------- | ---------------------------------------------- |
| `result.data` | `string` | 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": {
        "type": "string",
        "description": "Provider response payload."
      },
      "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 emailbison_update_lead --payload '{
  "lead_id": "string",
  "first_name": "string",
  "email": "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: `fixed` (per call).
* Estimated Deepline credits: `0` per pricing unit.
* Provider-native pricing may still exist outside Deepline credit billing.
* Billing mode: `no_bill`.