.png){kind=logo}
Email Validation Logic for Catchall and Invalid Emails
!{{Valid Email - Apollo}}?.result || ["invalid", "catchall"].includes({{Valid Email - Apollo}}?.result.toLowerCase())
If you're experiencing issues with Apollo email validation, here are the steps to resolve them: 1. Check your API key permissions: • Verify that your API key has access to the enrich endpoint • Confirm that the API key is active and correct 2. If you're getting a 403 Forbidden response, this typically means: • Your API key might be invalid • You have insufficient permissions • There are endpoint restrictions on your API key 3. If the permissions appear correct but you're still having issues, you'll need to contact Apollo.io's support team for clarification about your API key's endpoint access. Source: Apollo.io integration overview | Documentation | Clay University
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Dan E.··i'm on a plane so might be a little slow to get back 🙂
Bruno R.··Can you clarify where you're seeing this issue? If you could share the table you're seeing this instance I'd be happy to investigate this for you.
- Dan E.··
'Agency People'
- Bruno R.··
I'm not sure I see the error here - the apollo integration seems to be running as expected.
- Dan E.··
yes, that seems to be working, but i'm not seeing the Waterfall verified emails in the 'Workplace email' column
- Dan E.··
see row 8 as an example
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.
