ActionTelnyxUpdated September 2026
How do I check the delivery status of a Telnyx SMS?
Short answer: You can get message in Telnyx by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Telnyx Get Message action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Message ID message_id | string | Required | – |
Sample request
{"message_id": "{{trigger.message_id}}"}
Returns
{"data": {"id": "msg_abc","to": [{"status": "delivered"}]}}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Get Message.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Get Message.
What does the Get Message action do in Telnyx?
Retrieves a Telnyx message by ID, including its current delivery status (queued, sent, delivered, failed) and error codes if any. Used to follow up on a send and reconcile failures.
What inputs does Get Message require?
Required: Message ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Telnyx returns an error?
The run history shows the failed step with its input and the error message Telnyx returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Get Message support batch operations?
Run Get Message inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Telnyx's rate limits.
More actions
Other Telnyx actions.
Action
Make Outbound Call
Initiates an outbound voice call on the Telnyx Call Control API. Requires a Call Control App and a connection-id; the actual call flow is driven by webhook events.
ActionSend SMS
Sends a text message from a Telnyx number (or messaging profile) to a destination number. US/Canada destinations require 10DLC registration to avoid carrier filtering.