> ## 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: Post Inbox Sms

> Send SMS Message. Lemlist Post Inbox Sms reference includes SDK V2 and CLI requests, input constraints, response fields, and Deepline cost.

Send SMS Message.

<Info>
  Tool ID: `lemlist_post_inbox_sms`
</Info>

## Run this action

Use the TypeScript SDK for a single call. Put `ctx.tools.execute(...)` inside a Play when the call should be durable, scheduled, or run across a CSV.

```ts theme={null}
import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'lemlist_post_inbox_sms',
  {
    "sendUserId": "send_user_123",
    "from": "example",
    "message": "Example message"
  },
);

console.log(result.toolResponse.raw);
```

### CLI

```bash theme={null}
deepline tools execute lemlist_post_inbox_sms --input '{
  "sendUserId": "send_user_123",
  "from": "example",
  "message": "Example message"
}' --json
```

## Example response

The SDK exposes this shape at `result.toolResponse.raw`. Values below are representative.

```json theme={null}
{
  "data": {
    "ok": true,
    "contactId": "contact_123"
  }
}
```

Use `deepline tools get lemlist_post_inbox_sms --json` for the latest machine-readable contract.

## Input reference

Sends an SMS to a contact through the lemlist inbox. The message is sent to the contact's phone number (`phone` field, or the first entry of `phones`). Sending consumes SMS credits, one per message segment.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `payload.sendUserId` | `string` | Yes | — | Sender user ID. Must belong to the team owning the API key. |
| `payload.from` | `string` | Yes | — | Sender phone number, in E.164 format. Must be a phone number provisioned on your team; an unknown, pending or deleted number fails with `Failed to send SMS`. |
| `payload.contactId` | `string` | No | — | Contact ID. Provide either contactId or leadId (not both required). Returned in the response. |
| `payload.leadId` | `string` | No | — | Lead ID. Provide either contactId or leadId; when only leadId is sent, its contact is resolved and returned as contactId in the response. |
| `payload.message` | `string` | Yes | — | SMS body. lemlist variables such as \{\{firstName}} are resolved against the contact before sending, and the resolved message must not be empty. |

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

  ### Input JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "Sends an SMS to a contact through the lemlist inbox. The message is sent to the contact's phone number (`phone` field, or the first entry of `phones`). Sending consumes SMS credits, one per message segment.",
    "properties": {
      "sendUserId": {
        "type": "string",
        "description": "Sender user ID. Must belong to the team owning the API key."
      },
      "from": {
        "type": "string",
        "description": "Sender phone number, in E.164 format. Must be a phone number provisioned on your team; an unknown, pending or deleted number fails with `Failed to send SMS`."
      },
      "contactId": {
        "type": "string",
        "description": "Contact ID. Provide either contactId or leadId (not both required). Returned in the response."
      },
      "leadId": {
        "type": "string",
        "description": "Lead ID. Provide either contactId or leadId; when only leadId is sent, its contact is resolved and returned as contactId in the response."
      },
      "message": {
        "type": "string",
        "description": "SMS body. lemlist variables such as {{firstName}} are resolved against the contact before sending, and the resolved message must not be empty."
      }
    },
    "required": [
      "sendUserId",
      "from",
      "message"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Output reference

Standard tool result payload.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `result.data` | `object` | Yes | — | Provider response payload. |
| `result.data.ok` | `boolean` | No | — | True when the SMS was sent. |
| `result.data.contactId` | `string` | No | — | The contact the SMS was sent to (resolved from leadId when only a lead was provided). |
| `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": "object",
        "description": "Provider response payload.",
        "properties": {
          "ok": {
            "type": "boolean",
            "description": "True when the SMS was sent."
          },
          "contactId": {
            "type": "string",
            "description": "The contact the SMS was sent to (resolved from leadId when only a lead was provided)."
          }
        },
        "additionalProperties": false
      },
      "meta": {
        "type": "object",
        "description": "Additional response metadata (status, paging).",
        "additionalProperties": true
      }
    },
    "required": [
      "data"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Deepline cost

* Pricing model: `fixed` (per call).
* Estimated Deepline credits: `0` per pricing unit.
* Provider-native pricing may still exist outside Deepline credit billing.

## Related documentation

* [Lemlist provider guide](/docs/providers/lemlist/guide)
* [SDK V2 quickstart](/docs/sdk-v2/quickstart)
* [SDK reference](/docs/sdk-v2/sdk-reference)
* [Run tools across a CSV](/docs/sdk-v2/batch-csv)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.