Join the Community

Issues with Email Validation and Output Column in Waterfall Process

·

·

There are emails being found in my waterfall that are not being outputted to my output column, even if they were not found to be invalid. In fact, the zerobounce validation does not seem to be running on emails that have been found from some sources. When clicking to "explain" why the run condition was not met to validate, ti says: "Why this condition wasn't met: The condition is false because the emails from sources where validation status is not "valid" do not include the email in "Find Work Email (5)". Specifically, "Validate Findymail" has a status of "abuse" (not "valid"), so it uses the email from "Find Work Email (2)" which is "hawkins@sullivanhill.com", matching "Find Work Email (5)". However, the other validations like "Validate LeadMagic", "Validate Prospeo", and "Validate DropContact" are empty or undefined, so their emails are not included in the list to compare. To make the condition true, ensure that at least one validation (like "Validate LeadMagic" or "Validate Prospeo") has a status other than "valid" and that the corresponding email matches the email in "Find Work Email (5)". Alternatively, provide valid data for the missing validations so their emails can be checked properly." table lnik: https://app.clay.com/workspaces/590277/workbooks/wb_0svwz70wSARsNR8YtgX/tables/t_0swdqwwkS7kiV3R2Tbq/views/gv_0symvqoENtotzE9cjVz

4 comments

Clay
APP
·
·
The waterfall continues running even after finding an email when that email fails validation. Multiple providers run in sequence because each email found was not valid, causing the next provider to run until a valid email is found or all providers are exhausted. Validation columns are hidden by default to keep your table tidy, but they exist behind the scenes. To see why ZeroBounce validation isn't running on certain emails, unhide the validation columns in your Columns Panel to inspect the detailed validation steps. Only validated emails appear in the final output column - emails that fail validation won't be outputted even if they were found by a provider.
Sources: Enrich People (Waterfalls) [Automated Outbound] - Clay University Enrich People (Waterfalls) [Clay 101] - Clay University
Dustin S.
·
·
I expanded the waterfall. The issue is that validation columns are not running after an email was found. It just says run condition not met.
Clay
APP
·
·
The validation columns show "run condition not met" because the waterfall's built-in conditional logic only triggers validation when an email needs to be verified before moving to the next provider. If an email was found but validation isn't running, it's likely because the waterfall logic determined that email doesn't meet the criteria for validation at that step. The standard waterfall triggers providers and validation only when an email hasn't been found or the previous email found was invalid. To troubleshoot this, unhide all validation columns in your Columns Panel to see the complete validation process and understand why certain validation steps aren't executing. This will show you the detailed validation steps and help identify where the conditional logic is preventing validation from running.
Sources: Enrich People (Waterfalls) [CRM Enrichment] - Clay University Enrich People (Waterfalls) [Clay 101] - Clay University
Bo (.
·
·
Sorry for the confusion—there isn't any double charge, let me explain what's happening and how it works behind the scenes: When an email is found, we automatically run a validation step to check its accuracy. These validation columns are hidden by default to keep your table clean, but you can reveal them by selecting "Show All Columns"—this will let you review the email validation status directly. https://downloads.intercomcdn.com/i/o/w28k1kwz/1596443262/ddcd8e77ee2a30dc3d90c6f3d618/f1f8487a-3c6e-4656-9c8b-77dea23a7458?expires=1751330700&signature=3961cdf2442c0676074ec6dd7627070a6b8a991bf22fa0b85ad974bbdbfca7b9&req=dSUuEM16noNZW%2FMW1HO4zcOfiFJ2rZfmsFY7PVjVBrYXiLb0WmwQzIizTMpL%0Ab6w5%0A
Each time you try to find an email, we reach out to our providers. If they return a result, that counts as successful and credits are used. From there we send it to a validation step (the hidden one). Since we can't know in advance what a provider will return, we can't avoid this charge. However, what we do to prevent further credit costs is that once an email has been checked and marked invalid, we won't re-validate the same one. If another finder step runs afterward, it will only validate if it receives a new, different email. This helps avoid duplicate charges wherever possible. If you have any more questions or need further assistance, feel free to ask! 🌟

Issues with Email Validation and Output Column in Waterfall Process | Clay