Tks @Darren_Murphy. Appreciated.
Also there’s a typo in that regex. One of the “[” is missing. I’ll leave it a practice exercise for you to locate it…
2 Likes
In all seriousness though, I hadn’t envisaged using a Regex within a GDE column, but rather as an attribute against a text input field in a form. In the same way that one can currently specify that a text field is required and that it also has length restrictions, one could also specify that it must match a “Regex” mask. In that way I imagine that the matching process would only be executed at the point of checking field constraints prior to submission, so not running “willy nilly out of hand” within the internal DB, if that makes any sense. It would allow so much power in terms of validated data capture in Glide.
The hell is this haha.
1 Like
heh… it’s a regular expression for matching (a subset of) all possible URL’s 
I thought that would have been obvious? 
2 Likes
2 years and still no support for native phone number validation?
Anyway, I managed to get a workaround using regex FWIW: Data entry mask on phone or email component? - #3 by kiptoo
I’ve also struggled with phone number validation in Glide. Regex works, but it’s brittle and doesn’t cover every format (international codes, dashes, brackets, etc.).
A simpler option I’ve used is to let users type the number however they like, and then run it through Zapier + numverify right after form submission:
- Numverify validates the number and checks if it’s real.
- It strips out extra characters (spaces, brackets, dots, “+”) automatically.
- Zapier saves the clean, consistent version back into Glide.
That way your users don’t have to learn a strict input format, and your data stays clean.
Here’s the integration if you’d like to try it: