- Integrations
- /
- Vonage
Vonage
Vonage SMS, voice, and phone verification
Vonage (formerly Nexmo) is the communications API platform — SMS, voice, verify (phone-number OTP), video, conversation — competing with Twilio in the global CPaaS market. Tiny Command exposes five actions, no triggers (Vonage delivers inbound SMS, message-status changes, and inbound-call events via webhooks configured per-application in the Vonage dashboard; point them at a Tiny Command webhook trigger URL): Send SMS (single recipient, with international number routing handled by Vonage), Make Voice Call (initiates an outbound call with an NCCO action list — talk, stream, connect, etc.), Start Phone Verification (Vonage's Verify API for OTP-style number ownership confirmation), Get Message Status (poll a sent message's delivery state), Search Messages (historical message lookup with filters). The connection uses a Vonage API key + secret from the dashboard, plus the Application ID for voice-related actions (Vonage's voice and verify products use a separate JWT-signed application context, with the private key stored on the connection).
Do anything Vonage can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| 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. |
| Make 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. |
| Search Messages | Searches recent sent messages on the connected Vonage account by date range. Useful for reconciliation, audit, or billing exports. |
| Send 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. |
| Start 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. |
Pre-built Vonage workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Vonage once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Vonage field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Vonage integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Vonage to Tiny Command?
What Vonage triggers does Tiny Command support?
What Vonage actions can I run from a workflow?
Is the Vonage integration real-time?
Do I need to write code to use Vonage with Tiny Command?
How much does the Vonage integration cost?
More communication apps people connect.
Same category as Vonage, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Vonage.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.