- Integrations
- /
- Vonage
- /
- Actions
- /
- Get Message Status
ActionVonageUpdated May 2026
How do I check the delivery status of a Vonage SMS?
Short answer: Drop the "Vonage → Get Message Status" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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.
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
Other Vonage actions.
Action
Make Voice Call
Initiates an outbound voice call using the Vonage Voice API (requires an Application + private key, not just an API key/secret). Call flow is driven by the linked NCCO or answer_url.
ActionSearch Messages
Searches recent sent messages on the connected Vonage account by date range. Useful for reconciliation, audit, or billing exports.
ActionSend SMS
Sends an SMS via Vonage (formerly Nexmo) from your registered sender ID to a destination number. US/Canada destinations require 10DLC registration to avoid filtering.
ActionStart Phone Verification
Starts a Vonage Verify request: sends an OTP via SMS (with optional voice fallback) and returns a request_id you check in a follow-up step. The managed alternative to rolling your own OTP.
Send get message status from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.