Troubleshooting Email Retrieval with Apollo and Clay Integration

Hey guys, I'm trying to use Apollo to find emails in my Clay table and only to run rest of the waterfall if Clay doesn't work: https://app.clay.com/workspaces/286951/workbooks/wb_fyR3vgGNBAEN/tables/t_kfM3v4QJ46Na/views/gv_gKAJbq8QCSey I put a check on the waterfall to only run if Apollo doesn't find it since I'm using my API key. But the email is not populating in the Work Email 2 column

8 comments

Bruno R.
·
·
Hi Reyhan, thanks for reaching out. It looks like you ran out of Neverbounce credits for your personal API key here: https://downloads.intercomcdn.com/i/o/w28k1kwz/1247695108/e2abab97214f61bc93f8928502c7/CleanShot+2024-11-11+at+12_04_00%402x.png?expires=1731346200&signature=837bb27b5c07479033a985c95ea156741e35c8b9e57ac2920cb3a57dbd430bd4&req=dSIjEc93mIBfUfMW1HO4zSsrr3cSV8yfYCO68J6CCQkWWvUtzT74LwWLX%2BSx%0Am1wz%0A The emails are not being validated in the waterfall, which is why they are not appearing in the merge column. This issue is due to unmet run conditions. I recommend topping up your NeverBounce credits and re-running the setup to resolve this problem.
1
Reyhan K.
·
·
Why does my Table have 3 of these Neverbounce columns all of a sudden? Bruno R.
Bruno R.
·
·
The columns were already present; they were just hidden from view. These are validation columns you set up in your waterfall to determine whether the emails returned by the providers are valid. If the validation provider fails to run, it causes the waterfall to break, which is what happened in this case. Let me know if you need help resolving this!
1
Reyhan K.
·
·
I want to add a waterfall with the same 3 sources and 1 validation step, why is the validation step showing 3 times? I'll try to redo it
Tanvi R.
·
·
Hey Reyhan, the logic of the work email waterfall is automatically set up to run an email validation check in between each data provider. This is because the waterfall will continue to run if an email found is not valid. Essentially with the work email waterfall, you can either validate every email found or not validate any of the emails at all. If you would like to only run a validation column once, you can add the validation column as a separate column after the waterfall to find emails has been run. Please note that the best way to optimize for better data quality is by running the work email waterfall with validation after every provider - which is the way we have set this up. Totally up to you, but wanted to let you know why we do things this way :) Here's an explanation of the work email waterfall: https://www.loom.com/share/e79acd92841a4706b1710c4ce1bddaa4 Let me know if you have any other questions! 😊
Channeled
APP
·
·
Hey there - just wanted to check in here to see if you needed anything else! Feel free to reply back here if you do.
Reyhan K.
·
·
Im good you can close it
Channeled
APP
·
·
Hi Reyhan K.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: