Lemlist: Post Inbox Sms

Send an SMS to a contact from the Lemlist inbox.

Tool ID: lemlist_post_inbox_sms

Run this action

Use the TypeScript SDK for one call. Use ctx.tools.execute(...) inside a Play for durable calls, scheduled calls, or CSV processing.

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

deepline tools execute lemlist_post_inbox_sms --input '{
  "sendUserId": "send_user_123",
  "from": "example",
  "message": "Example message"
}' --json

Example response

The SDK returns this shape at result.toolResponse.raw. The example values illustrate the response.

{
  "data": {
    "ok": true,
    "contactId": "contact_123"
  }
}

Use deepline describe 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.

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

Deepline cost

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

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation