Clay S. I'm having issues with the ZoomInfo connection for a work email waterfall - right now it is saying 'Missing Attribution Path' - below are the screenshots and here is the table url: https://app.clay.com/workspaces/635731/workbooks/wb_0sybw20CsyqgeGYnv4k/tables/t_0syqi1t6FXbX9Zgwzwq/views/gv_0syqi1uPYvJXU2kJggT
For work email waterfalls, the primary input required is the Company Domain, and ideally Personal Social Profile URLs should also be included. If these aren't available, you can use fallback combinations like Full Name + Company Name or Full Name + Personal Email. The Company Domain should be entered as a clickable/searchable link and you should avoid using fields labeled as 'Email Domain'. Additionally, providing the full name of the individual is critical for successful email enrichment. Which specific input columns are you currently using for your ZoomInfo connection in the work email waterfall?
Hey Jordan - Happy to help, which column is causing an issue? I can see the Zoominfo column is currently working as expected
It is the 'Work Email' in the waterfall that I can't get to work
I created a ZoomInfo column to make sure that I could see the connection, but it is not pulling the work email through
Hey Jordan - I can see the waterfall is currently not working because you have the run condition set to "FALSE" which means the column will never run
Correct, I wanted to get the zoominfo connection working and the red diamond - pictured above - is saying it is "Missing Attribution Path" once that is fixed I was going to update the run formula
Hey Jordan - The issue is caused because the waterfall output section is not mapped. That being said, I've noticed the output options are not automatically populating here.

I've escalated this to our engineering team as a bug to help look into it. We'll follow up here as soon as we know more!
Of course!
Good news! Happy to report that we heard back from the team and this issue should be fixed. Try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if the problem has been resolved on your end, or if you still have trouble. Thank you for your patience as we worked on it.
Still getting the same error
