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

# Lemlist Inbox Operations: Inputs, Cost & CLI Example

> Sending an email via Lemlist inbox. 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=lemlist_send_email:{"send_user_id":"{{send_user_id}}","send_user_email":"{{send_user_email}}","send_user_mailbox_id":"{{send_user_mailbox_id}}","contact_id":"{{contact_id}}","lead_id":"{{lead_id}}","subject":"{{subject}}","message":"{{message}}"}' --json
```

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

## Input Schema

| Name                           | Type     | Required | Default | Description                                  |
| ------------------------------ | -------- | -------- | ------- | -------------------------------------------- |
| `payload.send_user_id`         | `string` | Yes      |         | Sender user ID                               |
| `payload.send_user_email`      | `string` | Yes      |         | Sender email address (must be a valid email) |
| `payload.send_user_mailbox_id` | `string` | Yes      |         | Sender mailbox ID                            |
| `payload.contact_id`           | `string` | Yes      |         | Recipient contact ID                         |
| `payload.lead_id`              | `string` | Yes      |         | Lead ID                                      |
| `payload.subject`              | `string` | Yes      |         | Email subject                                |
| `payload.message`              | `string` | Yes      |         | Email body (HTML)                            |
| `payload.cc`                   | `array`  | No       |         | CC recipients (valid email addresses)        |

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

  ### Input JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "Send an email via Lemlist inbox.",
    "properties": {
      "send_user_id": {
        "type": "string",
        "description": "Sender user ID",
        "minLength": 1
      },
      "send_user_email": {
        "type": "string",
        "description": "Sender email address (must be a valid email)",
        "minLength": 1,
        "format": "email"
      },
      "send_user_mailbox_id": {
        "type": "string",
        "description": "Sender mailbox ID",
        "minLength": 1
      },
      "contact_id": {
        "type": "string",
        "description": "Recipient contact ID",
        "minLength": 1
      },
      "lead_id": {
        "type": "string",
        "description": "Lead ID",
        "minLength": 1
      },
      "subject": {
        "type": "string",
        "description": "Email subject",
        "minLength": 1,
        "allowsTemplatePlaceholders": true
      },
      "message": {
        "type": "string",
        "description": "Email body (HTML)",
        "minLength": 1,
        "allowsTemplatePlaceholders": true
      },
      "cc": {
        "type": "array",
        "description": "CC recipients (valid email addresses)",
        "items": {
          "type": "string",
          "description": "CC recipient email address",
          "format": "email"
        }
      }
    },
    "required": [
      "send_user_id",
      "send_user_email",
      "send_user_mailbox_id",
      "contact_id",
      "lead_id",
      "subject",
      "message"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Output Schema

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

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

  ### Output JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "properties": {
      "status": {
        "type": "string"
      },
      "result": {
        "type": "object",
        "properties": {
          "data": {
            "type": "object",
            "properties": {
              "success": {
                "type": "boolean"
              },
              "messageId": {
                "type": "string"
              }
            },
            "required": [
              "success",
              "messageId"
            ],
            "additionalProperties": true
          }
        },
        "required": [
          "data"
        ],
        "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 lemlist_send_email --payload '{
  "send_user_id": "string",
  "send_user_email": "string",
  "send_user_mailbox_id": "string",
  "contact_id": "string",
  "lead_id": "string",
  "subject": "string",
  "message": "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`.