Send SMS: Vonage action · Tiny Command

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
To Phone to	phone	Required	To Phone. e.g. "+14155552671"
From from	string	Required	Sender ID or phone number
Message text	string	Required	Message

Sample request

{
  "to": "+14155552671",
  "from": "Vonage or +14155551234",
  "text": "{{trigger.text}}"
}

Returns

{
  "messages": [
    {
      "to": "14155552671",
      "status": "0",
      "message-id": "msg123",
      "message-price": "0.05",
      "remaining-balance": "15.50"
    }
  ],
  "message-count": "1"
}

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

FAQ

Questions about Send SMS.

What does the Send SMS action do in Vonage?

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.

What inputs does Send SMS require?

Required: To Phone, From, Message. 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 Send SMS support batch operations?

Yes. Run Send SMS 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