Send iMessage/SMS logo

Catalog action Messaging sms

Send a message via iMessage or SMS. Attempts iMessage delivery first (blue bubbles, read receipts) and falls back to SMS. Supports media attachments and iMessage send style effects. Ideal for: user notifications, alerts, OTP delivery, customer outreach, workflow status updates.

At a Glance

FieldValue
Action IDsms-send-message
CategoryMessaging
Connectorsms
Requires gasNo
Funds movementNone declared
Tagsmessaging, sms, imessage, notification, write

Payload Schema

FieldTypeRequiredDescription
contentstringYesMessage text to send. iMessage supports long messages; SMS fallback is limited to 1600 characters.
mediaUrlstringNoURL of a media file to attach (image, video, etc.). Must be publicly accessible.
sendStylestringNoiMessage send style effect. Only applies when delivered via iMessage, ignored for SMS.
statusCallbackUrlstringNoWebhook URL to receive message status updates (QUEUED, SENT, DELIVERED, ERROR).

Result Schema

FieldTypeRequiredDescription
messageHandlestringYesMessage identifier for tracking
statusstringYesMessage delivery status (QUEUED, SENT, DELIVERED)
messageTypestringNoDelivery channel used: 'iMessage' or 'SMS'

Examples

json
{ "type": "sms-send-message", "payload": { "content": "example-content" }, "children": [], "connector": { "type": "sms", "id": "conn_sms" }}

Payload fields can use workflow expressions such as {{$trigger.body.amount}}, {{$nodes.fetch.result.price}}, and {{$props.asset}} when the value should come from a trigger, prior node, or reusable workflow prop.