ActionTelnyxUpdated May 2026

How do I check the delivery status of a Telnyx SMS?

Short answer: Drop the "Telnyx → Get Message" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 3 Telnyx actions

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.

Google Sheets → Telnyx

2 Google Sheets triggers

HubSpot → Telnyx

18 HubSpot triggers

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Message support batch operations?

Yes. Run Get Message inside a Loop node to process arrays. Tiny Command handles Telnyx's rate limits automatically so you don't have to throttle manually.

More actions