Short answer: Drop the "Telnyx → Send SMS" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
From (E.164) from | string | Required | — |
To (E.164) to | string | Required | — |
Text text | string | Required | — |
Messaging Profile ID messaging_profile_id | string | Optional | — |
{"from": "{{trigger.from}}","to": "{{trigger.to}}","text": "{{trigger.text}}","messaging_profile_id": "{{trigger.messaging_profile_id}}"}
{"data": {"id": "msg_abc","to": [{"status": "queued","phone_number": "+19999999999"}],"from": {"phone_number": "+18888888888"},"text": "Hi"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.