--- title: Twilio Verify Sender node description: Initiates a Twilio Verify request to send a one-time passcode to the user's device as an additional authentication factor. component: auth-node-ref version: latest page_id: auth-node-ref:cloud:twilio-verify-sender canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/cloud/twilio-verify-sender.html keywords: ["Nodes & Trees", "Journeys", "Authentication", "Twilio"] page_aliases: ["auth-node-twilio-verify-sender.adoc"] section_ids: examples: Examples outcomes: Outcomes configuration: Configuration --- # Twilio Verify Sender node Initiates a [Twilio Verify](https://www.twilio.com/verify) request to send a one-time passcode to the user's device as an additional authentication factor. If you do not enable the Request Identifier property, make sure the shared node state has a `userIdentifier` field set with a valid phone number or an email ID when the flow reaches this node. Follow this node with the [Twilio Verify Collector Decision node](twilio-verify-collector-decision.html) in the authentication flow. ## Examples For examples in context, read the [Twilio examples](twilio-verify-collector-decision.html#twilio-examples). ## Outcomes * `True`: OTP sent successfully. * `Error`: Exception occurred, and the error message is stored in the shared store. ## Configuration | Property | Usage | | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Account SID | The unique string to identify the account found in the Twilio account dashboard. | | Authentication Token | The authentication token found in the Twilio account dashboard. You can use ESVs to set credentials appropriately for each environment in a multi-environment setup. Learn more in [ESVs](https://docs.pingidentity.com/pingoneaic/tenants/esvs.html). | | Service SID | The unique string to identify the service in the Twilio account dashboard. | | Channel | The delivery channel for sending the one-time passcode:- `SMS` (default) Phone numbers must contain the country code and can optionally contain special characters. The node removes all special characters before making the Twilio Verify request. Valid identifiers include `+15553231234` or `1(555)323-1234`. Invalid identifiers include `(555) 323-1234` as the country code is missing. - `Call` The same rules apply for phone numbers. - `Email` To use this channel, first integrate the Twilio Verify with SendGrid services, as described in [Send Email Verifications with Verify and Twilio SendGrid](https://www.twilio.com/docs/verify/email). - `WHATSAPP` The same rules apply for phone numbers. | | Request Identifier | Whether to prompt the user for their identifier.Optionally, this node can prompt the user for their identifier. By default, the authentication flow shared node state must contain a `userIdentifier` field that holds a valid phone number or email address.Default: disabled | | Identifier Shared State | The shared state variable to search for the user identifier. |