How to Write a Case-Insensitive Regex for Clay's Scrape Website Enrichment?

How do you write regex to be case-insensitive for Clay’s Scrape Website enrichment? For example, I’d like to write a regex that captures both “Business” and “business”. I tried /business/i using the case insensitive i flag; it does not work (no returned matches). However, when I try Business or business, it works.

26 comments

Matthew Q.
·
·
Can you try [Bb]usiness
Joe R.
·
·
Sorry, I should’ve clarified that I’m looking for more general guidelines on what flavour of regex works and doesn’t work in Clay. Based on your suggestion, it sounds like the case-insensitive i flag does not work. What are other rules I should be aware of? Do you have any documentation on Clay’s regex rules that I can refer to when writing regex? Thanks for your help!
Joe R.
·
·
Just bumping this again
Matthew Q.
·
·
Hey Joe R. - sorry was out sick yesterday
Matthew Q.
·
·
Just spoke to dev about this
Matthew Q.
·
·
They’re actually going to fix the Regex functions so its what’d youd typically expect
Joe R.
·
·
Hey no worries, sorry for pinging you on a Saturday while you’re still recovering
Matthew Q.
·
·
as opposed to having little one off rules
Matthew Q.
·
·
and all good! Catching up on everything rn anyways
:thumbsup_all:1
Joe R.
·
·
OK - any way I can get a list of one-off rules or is this fix going to be implemented really soon?
Matthew Q.
·
·
Someone is going to try fixing that today
Joe R.
·
·
oh wow, ok. I’ll wait then; would appreciate it if you could keep me posted
Matthew Q.
·
·
Yep will do!
:thumbsup_all:1
Joe R.
·
·
thanks a lot!
Joe R.
·
·
Hey Matthew Q.! Wanted to follow up to see if the regex revamp has been completed
Matthew Q.
·
·
hey this is fixed now!
Matthew Q.
·
·
also its case insensitive now by default
Joe R.
·
·
Nice! ill give it a try
Joe R.
·
·
Hey Matthew Q. - I see that the case insensitive filter is on by default now, thanks. But I’m running into other issues, which I’ve explained in a Loom here.
1.
Scraper pulling a regex match when I can’t find the string in the source text
2.
I still don’t know how to write regex in a way that Clay will understand. How do I write “TSA” and force Clay to only look for TSA as a stand-alone term and in all capitals?
Would really appreciate your help
Joe R.
·
·
Hey Arturo O. - would you be able to help here by any chance?
Clay Team
APP
·
·
Hey Joe! Sure, I'll take a look
🙏1
Matthew Q.
·
·
Hey Joe, sorry for the delay here - got lost in my messages. First off just added 1k credits for the lag here
Matthew Q.
·
·
Looked into this a bit more - the regex does look often, couldn’t quite discern what’s going on. For the time being, I added our free integration that get’s keywords from a body of text. This is looking to be more accurate
Matthew Q.
·
·
Will ned dev to check out this ticket further though to adjust the scrape website integration
Clay Team
APP
·
·
Yep, was checking this too. I was going to test out with formulas, using ai to generate a proper code to search for... not sure if it takes that as input though
👍1
Joe R.
·
·
Matthew Q. hey you mentioned the bug was due to the scraper pulling CSS properties / values and that it was resolved. But seeing the same issue recur in the same table (showing “ocean” as a regex match for the first row). Could you please help look into this