ActionVonageUpdated September 2026

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

Short answer: You can get message status in Vonage by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Vonage Get Message Status 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.

Get Message Status in Vonage — start free All 5 Vonage actions

Get Message Status in Vonage — start free

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.

Triggered by

Apps that pair well as the trigger for Get Message Status.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Vonage

2 Google Sheets triggers

HubSpot → Vonage

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Vonage 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 Status support batch operations?

Run Get Message Status 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 Vonage's rate limits.

More actions