ormuz
Home/Integrations/Twilio SMS/Nodes/Verify phone OTP (Twilio)
Twilio SMSUser actionStable

Verify phone OTP (Twilio)

Sends and verifies an SMS code with Twilio Verify to prove control of a phone number.

Vue d’ensemble

Sends and verifies an SMS code with Twilio Verify to prove control of a phone number.

Exemple

Before a sensitive action, ask the participant to validate the code received on their mobile phone.

Parameters 11

extension_config_idRequisref(extension_config:twilio)
Communication-provider configuration used by this operation.
titleOptionnelstring
Title displayed in the approval or verification experience.
descriptionOptionnelstring
Supporting text displayed during the user action.
toRequisphone
Message recipient(s): address, number, or contact(s) depending on the node.
verify_service_sidOptionnelstring
Optional Twilio Verify service used for the OTP journey.
mask_phone_in_journeyRequisboolean
Whether the phone number must be partially masked in the hosted experience.
resend_delay_secondsRequisinteger
Minimum delay between two code resends.
max_attemptsRequisinteger
Maximum number of allowed code attempts.
max_resendsRequisinteger
Maximum number of allowed code resends.
allow_replay_from_hereOptionnelboolean
Allow replay from this step utilisé pour cette opération de communication.
replay_boundaryOptionnelboolean
Replay point of no return utilisé pour cette opération de communication.

Outputs 5

verifiedboolean
Whether the OTP code was successfully validated.
phone_numberphone
Verified phone number.
verification_sidstring
Twilio Verify identifier for the OTP journey.
statusstring
Current normalized state of the mailing, approval, or verification.
verified_atdatetime
Date and time when verification succeeded.

Behavior

The user action sends the code, enforces attempt and resend limits, and resumes the process only after validation or completion of the journey.

Limits and responsibilities

  • Verification proves control of the number at the time of the journey, not the person's civil identity.
  • Attempt and resend limits are product safeguards and must not be bypassed through process loops.
  • Masking the number on screen reduces visual exposure but does not change its data classification.