Library / Security & Compliance
Security & Compliance
Verify phone numbers by SMS OTP and log verified numbers to Google Sheets
Webhook-driven flow that sends a 6-digit SMS code to a phone number, verifies it once within five minutes, and logs confirmed numbers to a Google Sheet.
What it does
## Verify phone numbers with a one-time SMS code (OTP) ### How it works Two webhooks give your sign-up or checkout form a phone verification step, with no code to host: 1. Request a code (POST /sms-otp/send with { "phone": "..." }) checks the number and sends a 6-digit code by SMS with the generate_otp tool of the SMS Vert Pro MCP server. The code is valid for 5 minutes. 2. Check a code (POST /sms-otp/verify with { "phone": "...", "code": "123456" }) checks it with verify_otp. A code works only once. 3. Each verified number is added to a Google Sheet with the date, and the form gets a clear JSON answer: 200, 400 (invalid number), 401 (wrong or expired code), 429 (a code was already sent a moment ago). ### Setup steps 1. Create a Google Sheet with the columns phone and verified_at, and connect your Google account in Log verified number. 2. Create a Bearer Auth credential with your SMS Vert Pro API V2 token (log in at smsvertpro.com, then open https://www.smsvertpro.com/api/doc-v2.php) and select it in the two MCP Client nodes. 3. In OTP settings, set your sender name (11 characters max), your sheet URL, your default country code (numbers starting with 0 are converted) and the country codes you accept. 4. Activate the workflow and call the two production webhook URLs from your form. ### Customization Replace the Google Sheet with your CRM or database, or add a step that unlocks the user account once the number is verified.
The steps
- Request a code
- Check a code
- OTP settings
- Read request
- Valid request?
- Respond: invalid request
- Send or check?
- Send code by SMS
- Code sent?
- Respond: code sent
- Respond: code not sent
- Check code
- Code valid?
- Log verified number
16 steps in total.
Similar automations