Adding Million Verifier as Validation Provider in Waterfall
Hi, How do we add Million Verifier as the Validation Provider instead of what is listed in the waterfall? Thanks!
Hi, How do we add Million Verifier as the Validation Provider instead of what is listed in the waterfall? Thanks!
When setting up an email waterfall, you can change the validation provider from the default ZeroBounce to Million Verifier. [1]
To make this change, configure your waterfall settings when adding the email enrichment and select Million Verifier from the available validation provider options.
Did that answer your question?
Million verifier is not listed in the options.
Million Verifier isn't currently available as a validation provider option in our email waterfalls. Only a subset of our integrations can be added to waterfalls right now, but we're working to support all providers soon. [1]
We consolidate 75+ enrichment tools and continuously add new providers. If you need Million Verifier specifically, request human assistance by clicking "Talk to a person" and our team can help find a solution or add the provider. [2]
Did that answer your question?
Talk to a person
I’ll connect you to one of my teammates who can help. Please hold on a moment.
Clay Support is sharing a file with you.
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
Hi Mick - thanks for reaching out!
Unfortunately, Million Verifier is not currently available as a built-in validation provider in Clay's email waterfall. However, if you have an API key, you can use it as a separate column with our HTTP API enrichment. You can validate emails by using a "Find Email" provider, and then utilize the HTTP API column afterwards - rinse & repeat. I recommend referring to their API documentation for handling the requests, but it is definitely doable within Clay!
Let me know if you have anymore questions :)
Hey Michael A. Thank you for responding promptly, We have that HTTP API enrichment, but i wanted to have it added as a column every after enrichment step in the waterfall, Do you have a way to do that? I wanted it to replace the Email Validation i.e. "ZeroBounce" and have it be set up the same way.
Hi Mick! Unfortunately, you cannot integrate the validator within a waterfall because it is a custom configuration, not a built-in Clay integration email validator.
A current workaround is to set up your email waterfall without a validation step and add Million Verifier as a separate column after the waterfall. However, the waterfall will not automatically skip to the next provider if validation fails.
For now, I recommend this option until Clay adds HTTP API validation support to waterfalls. Let me know if I can help with anything else, thanks!
Yea. that's actually the problem we are facing, it doesnt flow through the next step, it has to wait until we found one, and we have to re run steps that haven't run in the event that it is a bad email.
Yeah, I hear your frustration. Thinking at a high level, there is two approaches to this that you can use.
Option 1: Use a Built-in Validator for Now
You can use Clay's current default validator and then optionally run Million Verifier as a secondary check on the final validated emails (you only pay for the provider that finds a valid email).
Option 2: Complex Formula-Based Waterfall
This is technically possible but very manual:
Provider 1 (e.g., LeadMagic)
Million Verifier Validation 1 - validate Provider 1's email
Formula Step: Check if Provider 1 + Validation 1 succeeded
Provider 2 (e.g., Hunter) - conditional run: Only if Formula Step = false
Million Verifier Validation 2 - validate Provider 2's email
Formula Step: Check if Provider 2 + Validation 2 succeeded
Provider 3 (e.g., Prospeo) - conditional run: Only if previous formula = false
Continue this pattern...
Final Merge Formula: Return first email that passed validation
But it is harder to scale / costs more credits.
Those are the options that I can suggest, feel free to let me know how those go!
Yes, we were building option 2 before i messaged here. Just wanted to see if there's a better way to do this, as it would cost more credits.
Yeaa unfortunately there isn't a cheaper workaround. I recommend sticking with option 1 if you're looking to save credits, as Clay's current default validator is very accurate!