One of my AI columns isn't running and returns "Invalid Input". I thought it was because of my rate limits for my Open AI API key (see below), but even if I change it to any of the models using Clay credits, I still get the same invalid input error. The only input I have to this column is the website domain and it looks to be done properly (see below) and all have values so I'm not sure why I'm still getting this error.
Hey Doug, It seems to be fixed now, right? Typically when you see "Invalid Input," you could click on the row to see the specific reason. Very sorry for the delay.
Ah got it - the link you sent was pointing to the Decision Makers table, very sorry for the confusion. I just checked in the "Company Table" and saw the column - it was indeed due to the OpenAI limits. As you can see, as soon as we select Clay credits and save, the error disappears. For your OpenAI limit - the reason is that your key needs to be upgraded to a higher tier to function properly. Unfortunately, we can’t bypass that limit—it’s something OpenAI handles directly. Here’s what you need for using your API key with the integrations: Claygent (online research): To search the web and gather information, you’ll need at least 450,000 Tokens Per Minute (TPM). ChatGPT (text generation): If you’re just generating text with existing data in Clay, you only need 30,000 TPM. That said, Clay credits will work for these tasks, so upgrading your OpenAI tier might not be necessary depending on your needs. You can check your current tier, as well as your usage and limits, in the OpenAI dashboard under: • Usage • Limits • Usage Tiers We’ve seen users successfully add a pre-paid tier amount to their OpenAI account and resolve the issue. However, since this is outside our control, we recommend troubleshooting directly with OpenAI’s team. Let me know if you need any further assistance! 😊
Hey - I tried in the GIF and it was working for rows with domains but I do see there is still some that say "Invalid Inputs". It seems they were from the previous run and weren't triggered again. When we change the setup, we need to re-run rows to get the new data updated. You can see in this GIF here I re-trigger them and it goes away! :)
.png){kind=logo}
