Instantly Integration Issue: API Key and Table Duplication Problems

Ericson D. · 2024-09-05 13:02:17.225655+00

Hi! Looks like the Instantly integration is not working atm. I tried to re-add the API key and duplicate the table but still doesn't work. Here's a video: Clay table:

Instantly Integration Issue: API Key and Table Duplication Problems | Clay

10 comments

· Sorted by Oldest

Channeled
APP
·
·
👋 Hey there! Our support team has got your message - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in this thread so that we can help you as quickly as possible!
Tanvi R.
·
·
Hi Ericson, thanks for reaching out. It looks like we've got a bug on our hands - I've escalated this over to our engineering team and we'll let you know as soon as we know more!
Tanvi R.
·
·
Hey Ericson, I took a closer look and see the issue is actually coming from 2 different errors related to your API keys. 1. Your OpenAI API key in Claygent maxed its rate limit creating stale data 2. Your Instantly Key encountered and authorization error. To resolve this, you should: 1. Upgrade your OpenAI key to a higher tier or contact their support team if believe there are issues with your usage tier 2. Check if your Instantly API key is invalid or expired and has the correct access level. Here's a more detailed explanation: https://www.loom.com/share/e0e21bf93fbe4533b84c076a6e3e53c8?sid=3723b4ec-db08-477c-b40d-f683e21df9d4
Ericson D.
·
·
Hi Tanvi R., I'm actually in tier 4 so this shouldn't be an issue
Ericson D.
·
·
and API key appears to be valid
Ericson D.
·
·
seems like the issue is on your end
Bo (.
·
·
Yes, the API is valid, but it the rate limit has been reached. For the “instantly” issue, it’s also due to stale data. A quick solution is to turn the table off and then back on. Here's how to turn your table off, stop ongoing runs, also run a specific number of rows (bonus setting up row limits/filters) - https://www.loom.com/share/131e2c371a184748a87dc870304955b0 This should prompt the “Cleaned Job Title Response” column to re-run, using up-to-date data. Here’s an example of how stale or outdated data can cause issues: Loom video. 😊
Ericson D.
·
·
Thanks:) It's all good now
Channeled
APP
·
·
We haven't heard back from you in a bit, so we're going to go ahead and close things out here - feel free to let us know if you still need something!
Channeled
APP
·
·
Hi Ericson D.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

Channeled
APP
·
·
👋 Hey there! Our support team has got your message - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in this thread so that we can help you as quickly as possible!
Tanvi R.
·
·
Hi Ericson, thanks for reaching out. It looks like we've got a bug on our hands - I've escalated this over to our engineering team and we'll let you know as soon as we know more!
Tanvi R.
·
·
Hey Ericson, I took a closer look and see the issue is actually coming from 2 different errors related to your API keys. 1. Your OpenAI API key in Claygent maxed its rate limit creating stale data 2. Your Instantly Key encountered and authorization error. To resolve this, you should: 1. Upgrade your OpenAI key to a higher tier or contact their support team if believe there are issues with your usage tier 2. Check if your Instantly API key is invalid or expired and has the correct access level. Here's a more detailed explanation: https://www.loom.com/share/e0e21bf93fbe4533b84c076a6e3e53c8?sid=3723b4ec-db08-477c-b40d-f683e21df9d4
Ericson D.
·
·
Hi Tanvi R., I'm actually in tier 4 so this shouldn't be an issue
Ericson D.
·
·
and API key appears to be valid
Ericson D.
·
·
seems like the issue is on your end
Bo (.
·
·
Yes, the API is valid, but it the rate limit has been reached. For the “instantly” issue, it’s also due to stale data. A quick solution is to turn the table off and then back on. Here's how to turn your table off, stop ongoing runs, also run a specific number of rows (bonus setting up row limits/filters) - https://www.loom.com/share/131e2c371a184748a87dc870304955b0 This should prompt the “Cleaned Job Title Response” column to re-run, using up-to-date data. Here’s an example of how stale or outdated data can cause issues: Loom video. 😊
Ericson D.
·
·
Thanks:) It's all good now
Channeled
APP
·
·
We haven't heard back from you in a bit, so we're going to go ahead and close things out here - feel free to let us know if you still need something!
Channeled
APP
·
·
Hi Ericson D.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: