Get Message Status: Vonage 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 ID message_id	string	Required	The Message ID assigned by Vonage. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label.

Sample request

{
  "message_id": "{{trigger.message_id}}"
}

Returns

{
  "messages": [
    {
      "to": "+19999999999",
      "status": "delivered",
      "message-id": "abc"
    }
  ]
}

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

FAQ

Questions about Get Message Status.

What does the Get Message Status action do in Vonage?

Searches for a sent Vonage message by ID and returns its current delivery status and error code (if any). Use to reconcile sends with carrier-reported failures.

What inputs does Get Message Status 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 Vonage 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 Status support batch operations?

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

More actions