ActionVonageUpdated September 2026

How do I send an OTP to verify a phone number with Vonage?

Short answer: You can start phone verification in Vonage by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Vonage Start Phone Verification action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Start Phone Verification in Vonage — start free All 5 Vonage actions

Start Phone Verification 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
Phone Number number	phone	Required	Phone Number. e.g. "+14155552671"
Brand Name brand	string	Required	Shown to the user: 'Your MyApp verification code is...'
Code Length code_length	options	Optional	Code Length. Options: 4 digits, 6 digits

Sample request

{
  "number": "+14155552671",
  "brand": "MyApp",
  "code_length": "{{trigger.code_length}}"
}

Returns

{
  "status": "0",
  "request_id": "verify-abc123"
}

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

Triggered by

Apps that pair well as the trigger for Start Phone Verification.

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 Start Phone Verification.

What does the Start Phone Verification action do in Vonage?

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.

What inputs does Start Phone Verification require?

Required: Phone Number, Brand Name. 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 Start Phone Verification support batch operations?

Run Start Phone Verification 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