Get Message: Twilio action

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 SID messageSid	string	Required	Message SID. e.g. "SM1234567890abcdef"

Sample request

{
  "messageSid": "SM1234567890abcdef"
}

Returns

{
  "to": "+15551234567",
  "sid": "SM1234567890abcdef",
  "body": "Hello from Twilio!",
  "from": "+15559876543",
  "price": "-0.0075",
  "status": "delivered",
  "date_sent": "2024-01-01T00:00:01Z"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Get Message.

What does the Get Message action do in Twilio?

Retrieves details of a sent Twilio message by SID with status (queued, sent, delivered, undelivered, failed), price, and error code. Used to reconcile sends with carrier-reported state.

What inputs does Get Message require?

Required: Message SID. 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 Twilio 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 Twilio's rate limits automatically so you don't have to throttle manually.

More actions