Hey Team, I was working on this table last day and I was using Zenrows, Open AI API Key. Now I checked they automatically moved to clay account. Can you please check? Also there are a lot of "retried but failed" and "error"
By default, our system automatically selects the Clay-managed key for API services. This is why you're seeing your Zenrows and OpenAI operations using Clay's account instead of your own API keys.If you'd like to use your own API keys instead, you can add them through two methods:1. Go to your profile picture > Settings > Connections 2. Or when setting up an enrichment, click on "Add Account" in the enrichment panelRegarding the "retried but failed" and "error" messages, I'll need more specific information about these errors to help troubleshoot them effectively. Could you please share:** Screenshots of the errors ** When these errors occur * Which specific operations are failing Sources: Use AI - Clay University Guide: Ways to Save Clay Credits - Clay University
Is that what you were looking for?
I have already connected these API keys, but can't see while doing enrichments
To use your own API keys during enrichments, you need to specifically select them when setting up the enrichment. When you're in the enrichment panel, look for the "Add Account" option to switch from the default Clay-managed key to your own connected API key.Important note: This feature is only available if you're on a paid plan (Starter, Explorer, or Pro). If you're on a free plan, you won't be able to use your own API keys.If you're still having trouble seeing your connected API keys or if you need further assistance, you can request human support by clicking on "Talk to a person". Sources: Guide: Ways to Save Clay Credits - Clay University Enrow - 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 Faheem, thanks for reaching out. Taking a look a this now!
Do you mind sending the link to the table so we can take a look? https://downloads.intercomcdn.com/i/o/1171717996/ac7729f84b426e1d0358af02/image.png?expires=1732221000&signature=754c06b364eba247004d6da93bbd38618af1ef9bb20bb85647e5c6668e8da76c&req=dSEgF85%2FmohWX%2FMW1HO4zYTywSn%2BBJYW2BKsam%2FhVPv1Bg%3D%3D%0A
t_8VsDhe6x3VB3
I don't see any table with this table ID, in your workspace, could you kindly share the entire URL? Thanks for your patience!
Thanks! Do you know what API key usage tier is associated with your Zenrows personal API? This might be the issue. I’d recommend either requesting a higher limit or using our Clay shared API instead. By spending Clay credits, we can leverage higher limits and avoid running into these restrictions.
Got it, for Zerobounce, and Open Ai I also added their API keys, but I can't see them while doing enrichment. Then I added again API key for Zerobounce, still not showing
It seems both the GPT and Zerobounce columns are running on your personal API keys. Could you provide some context on where you're seeing the Clay-shared API key being used?
Can you please let me know if I can work on different workspaces at the same time? I think this is reason, because I'm seeing the Api key for another workspace
Yes, you should be able to work on separate workspaces simultaneously. If you perform a hard refresh, do you still see the discrepancy? If the issue persists, could you kindly perform a hard refresh for me? On a Mac, for Chrome or Firefox, press Cmd + Shift + R. For Safari, press Cmd + Option + R. On a PC, for Chrome, Firefox, or Microsoft Edge, press Ctrl + F5. Additionally, if possible, could you record a Loom video to provide more context? It would help me better understand and resolve the issue.
Hey there - just wanted to check in here to see if you needed anything else! Feel free to reply back here if you do.
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!
.png&w=3840&q=75){kind=logo}
