ActionVonageUpdated September 2026
How do I search recent Vonage messages?
Short answer: You can search messages in Vonage by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Vonage Search Messages action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 |
|---|---|---|---|
Date (YYYY-MM-DD) date | string | Required | – |
Recipient (optional) to | string | Optional | – |
Sample request
{"date": "{{trigger.date}}","to": "{{trigger.to}}"}
Returns
{"count": 1,"items": [{"to": "+1999","body": "Hi","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 Search Messages.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Search Messages.
What does the Search Messages action do in Vonage?
Searches recent sent messages on the connected Vonage account by date range. Useful for reconciliation, audit, or billing exports.
What inputs does Search Messages require?
Required: Date (YYYY-MM-DD). 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 Search Messages support batch operations?
Run Search Messages 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
Other Vonage actions.
Action
Get Message Status
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.
ActionMake 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.
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.