Twilio Verify
Identity & SecurityAdd phone and email verification to any flow with Twilio Verify. Agents start one-time passcode challenges over SMS, voice call, email, or WhatsApp and check the codes users submit, with Twilio generating, delivering, and validating every passcode.
What This Integration Enables
Most automation platforms treat identity as someone else's problem: if a request arrives, it must be legitimate. FlowRunner's position is the opposite, and Twilio Verify is one of the sharpest tools for it. When a workflow reaches a step where it matters that a specific human is on the other end, activating an account, changing a payout destination, releasing a sensitive document, an agent can challenge that human with a one-time passcode over SMS, voice call, email, or WhatsApp. Twilio generates, delivers, and validates the code, so no code is ever stored or handled in your flow, and the agent proceeds only on an approved check. - Verify phone numbers and emails during signup before an account goes live - Add step-up verification to the riskiest steps of any workflow, not just logins - Confirm a recipient owns a number before enrolling them in transactional messaging - Choose the channel per recipient: SMS, voice call, email, or WhatsApp - Escalate verification failures to [human-in-the-loop](/concepts/human-in-the-loop) review, where fraud and friction get told apart
Without FlowRunner
With FlowRunner
Use Case Scenarios
Signups that are real before they are active
A new contact lands in [HubSpot](/integrations/hubspot). The agent calls Start Verification over SMS, and the signup flow collects the code and confirms it with Check Verification. On approved, the account activates and a welcome message goes out through [SendGrid](/integrations/sendgrid). Numbers that fail verification never enter the messaging audience, which keeps delivery rates honest and keeps the CRM from filling with contacts who cannot be reached.
Step-up verification inside the approval itself
FlowRunner's human-in-the-loop gates pause a workflow for a person's decision. For the highest-stakes gates, a vendor bank-detail change, a bulk refund release, the approval itself gets verified: when the approver responds, the agent fires Start Verification to their registered phone and requires the code back through Check Verification before treating the approval as genuine. The workflow no longer trusts that whoever answered the message is the person authorized to answer it. That distinction is exactly what an auditor asks about.
Proving number ownership before the first text
Before an SMS notification program enrolls anyone, the agent verifies each opted-in number: Start Verification, code entry on the confirmation page, Check Verification. Only approved numbers flow into the messaging platform's audience. Typos, recycled numbers, and someone else's phone get caught at the door instead of generating carrier complaints later, and the verification record itself, logged to [Google Sheets](/integrations/google-sheets) or the CRM, becomes the consent evidence.
Human-in-Loop Highlight
The dangerous moment on this connector is not the send; it is the interpretation of a failure. A verification that expires after its ten minutes or burns through its maximum attempts leaves Check Verification returning errors, and an agent facing that has two tempting wrong moves: retry Start Verification in a loop, which is a real per-attempt spend and, because only one verification per recipient can be active at a time, can wedge a legitimate customer out of verifying at all; or quietly proceed without an approved status, which defeats the entire point of challenging identity. FlowRunner agents do neither. An exhausted verification becomes a case in front of a person, with the channel, attempt history from Get Verification, and account context attached. The human decides: help a stranded customer through another path, or lock the door on someone probing it.
Agent Capabilities
5 actionsVerifications
3- Start Verification Starts a phone or email verification by sending a one-time passcode to the recipient over the chosen channel: SMS, voice call, email, or WhatsApp. Twilio generates and delivers the code, so the flow never handles it. Returns a pending verification and a SID. Only one active verification per recipient at a time.
- Check Verification Checks the passcode a user entered against an active verification. Returns approved when correct, pending when not. Verifications are consumed on approval and removed after expiration, typically ten minutes, or maximum attempts, after which further checks return an error.
- Get Verification Fetches the current state of a verification by SID, including status and channel. Consumed verifications return a 404 shortly after approval, expiry, or exhaustion, so state checks belong inside the active window.
Services
2- List Services Lists the Verify Services in the Twilio account. Each service is a container of settings, code length, delivery channels, friendly name, identified by a SID starting with VA. The discovery step for configuring this integration.
- Get Service Fetches a single Verify Service's configuration: friendly name, generated code length, and enabled channels. Defaults to the service SID configured on the integration.
Frequently Asked Questions
What can FlowRunner do with Twilio Verify?
FlowRunner agents can run Start Verification, Check Verification, and Get Verification in Twilio Verify, plus 2 more actions.
Does connecting Twilio Verify to FlowRunner require OAuth?
No. Twilio Verify connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can Twilio Verify trigger a FlowRunner workflow automatically?
Twilio Verify doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Twilio Verify
$100 in credits. No card required. Connect in minutes.