> ## 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 Bulk Create Leads Using Csv: Inputs, Cost & CLI

> Create multiple leads in a single request using a CSV. 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=emailbison_bulk_create_leads_using_csv:{"name":"{{name}}","csv":"{{csv}}","columnsToMap":"{{columnsToMap}}"}' --json
```

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

## Input Schema

| Name                             | Type                         | Required | Default | Description                                                                                                                                                                                                                                                                                                                                                        |
| -------------------------------- | ---------------------------- | -------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `payload.name`                   | `string`                     | Yes      |         | The name of the contact list                                                                                                                                                                                                                                                                                                                                       |
| `payload.csv`                    | `string`                     | Yes      |         | The CSV file containing the contacts.                                                                                                                                                                                                                                                                                                                              |
| `payload.existing_lead_behavior` | `"put" \| "patch" \| "skip"` | No       |         | The behavior to apply when a lead already exists. If "put", replace all the lead's fields, including custom variables, with the fields from this request. Fields not passed are cleared. If "patch", only update a field if it's passed. Fields and custom variables not passed are kept. If "skip", do not process the lead. Will default to "put" if not passed. |
| `payload.columnsToMap`           | `array`                      | Yes      |         | The array with the header fields from the csv.                                                                                                                                                                                                                                                                                                                     |

### Allowed values

| Field                            | Allowed values         |
| -------------------------------- | ---------------------- |
| `payload.existing_lead_behavior` | `put`, `patch`, `skip` |

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

  ### Input JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "Create multiple leads in a single request using a CSV",
    "properties": {
      "name": {
        "type": "string",
        "description": "The name of the contact list"
      },
      "csv": {
        "type": "string",
        "description": "The CSV file containing the contacts.",
        "format": "binary"
      },
      "existing_lead_behavior": {
        "type": "string",
        "description": "The behavior to apply when a lead already exists. If \"put\", replace all the lead's fields, including custom variables, with the fields from this request. Fields not passed are cleared. If \"patch\", only update a field if it's passed. Fields and custom variables not passed are kept. If \"skip\", do not process the lead. Will default to \"put\" if not passed.",
        "enum": [
          "put",
          "patch",
          "skip"
        ]
      },
      "columnsToMap": {
        "type": "array",
        "description": "The array with the header fields from the csv.",
        "items": {
          "type": [
            "object",
            "null"
          ],
          "properties": {
            "first_name": {
              "type": "string",
              "description": "The first name header field of the csv."
            },
            "last_name": {
              "type": "string",
              "description": "optional The last name header field of the csv."
            },
            "email": {
              "type": "string",
              "description": "The email address header field of the csv."
            },
            "title": {
              "type": "string",
              "description": "The title header field of the csv."
            },
            "company": {
              "type": "string",
              "description": "The company name header field of the csv."
            },
            "custom_variable": {
              "type": "string",
              "description": "The header field from your CSV to match this variable"
            }
          },
          "required": [
            "first_name",
            "email"
          ],
          "additionalProperties": false
        }
      }
    },
    "required": [
      "name",
      "csv",
      "columnsToMap"
    ],
    "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_bulk_create_leads_using_csv --payload '{
  "name": "string",
  "csv": "string",
  "columnsToMap": "array"
}' --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`.