Start Phone Verification: Vonage action

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.

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 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 Start Phone Verification support batch operations?

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