Can someone help me? My org signed up with Clay not too long ago. We have worked with one rep for two teaching sessions. But in setting up our table enrichment template for us, he had a typo in the final emails and now we have have over 3000 in our CRM with an added /fina (sometimes multiple /fina/fina/fina) ahead of the email address. This is a big problem. I emailed this rep, he said he fixed it, and was kind of snippy about it. But it is still not fixed and I don't know how to get rid of this /fina on the emails. He is also not responding to my emails. I can rerun eh column again, but I don't want to waste credits when I already had reliabl data in a majority of this column before running any enrichments. I also tried creating a new enrichment column to remove the /fina, but it didn't seem to work. Please help!
You can use Clay's data cleaning tools to fix those email addresses without using any credits. These tools are completely credit-free since they operate by parsing existing data rather than reaching out to external providers. To remove the "/fina" prefixes: 1. Navigate to the "Add enrichment" panel 2. Select the "Normalize" option in the left sub-navigation 3. Look for text normalization tools in the pre-built options 4. Choose your email column as the input 5. Run the action across your rows This should help standardize your email formats without losing your reliable data.
text normalization or normalize email is not an option in my account.
You can use Clay's AI formula to clean those email addresses. Since the normalization tools aren't available in your account, create a new column with an AI formula that removes the "/fina" prefix from your emails. For example, use a formula that instructs the AI to "Remove all instances of '/fina' from this email address" with your email column as the input. This approach uses Clay's data parsing capabilities without consuming enrichment credits, as it's manipulating existing data rather than fetching new information.
I also tried using AI formulation to remove the /fina and it did not work. Any "normalized email" still had /fina on it
Hey there Kristine thanks for reaching out, I replied in the other thread, so I’ll close this one.
