Hey team, I am trying to enrich the company using apollo within clay but getting a runtime error. Can you please check why this might may be.
Based on common issues with Apollo.io integration, your runtime error might be related to API key permissions. Here are the potential causes and solutions: 1. Your API key may be invalid or unauthorized for the enrich endpoint 2. The API key might lack necessary permissions 3. There could be endpoint restrictions on your API keyTo resolve this: ** Verify that your API key has proper access to the enrich endpoint ** Double-check that your API key is active and correctly entered * If the permissions appear correct but you're still having issues, you may need to contact Apollo.io's support team to verify your endpoint accessFor detailed guidance on configuring your API key with the correct permissions, you can check Apollo.io's documentation on API key creation and management. 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!
Hi Uzair, thanks for reaching out. Taking a look at this now!
It looks like the API key you're using for your apollo integration is invalid, I suggest following this guide from apollo to create a new api key, which you can then try to re-link in Clay: https://knowledge.apollo.io/hc/en-us/articles/4415734629773-Create-API-Keys
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.
same issue here
Same issue here
same issue as well!
I just checked and a cell that worked with Apollo two days ago now has runtime error
Same issue here!
Same here! Apollo must have updated something that broke the integration