How to search messages in Vonage

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.

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 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 Search Messages support batch operations?

Yes. Run Search Messages inside a Loop node to process arrays. TinyCommand handles Vonage's rate limits automatically so you don't have to throttle manually.

More actions