Hi Team, i want to connect with the Groq API (https://console.groq.com/docs/api-reference#chat-create) to have it be the default AI when using "Use AI" feature in tables (See screenshot) Could anyone help me set this up? The question might rather be, how to connect other APIs beyond those generated by OpenAI or Anthropic (e.g. Groq APIs which will still use such models in the backend, but is hosted by Groq)
Currently, our "Use AI" feature supports three specific AI models: GPT, Claude, and Gemini. You can connect your own API keys for these models by selecting the desired model from the dropdown, clicking on the Account dropdown, and clicking "+ Add account." For other APIs like Groq that aren't directly supported in "Use AI," you can use our HTTP API feature to connect to any tool you have API access to. This allows you to integrate external APIs through custom API configurations. However, this would be separate from the "Use AI" feature's model selection dropdown, which is currently limited to GPT, Claude, and Gemini.
Hi Ricardo, thanks for reaching out to support! Currently, Groq isn't supported as a native integration. Clay's "Use AI" feature works with: ** OpenAI (GPT models) ** Anthropic (Claude) ** Google Gemini ** Clay's own models What you can do: 1. Use your own API keys for the supported providers above - just go to Settings → Connections → Add Connection. This uses your API credits instead of Clay credits, which can be more cost-effective. 2. Potential workaround: If you're on a Pro/Explorer plan, you could use Clay's HTTP API feature to make custom calls to Groq's API, though this would require some technical setup. My recommendation: For now, I'd suggest using one of the supported providers with your own API key to reduce costs. The Clay team has shown interest in expanding AI model options based on user feedback, so submitting a feature request for Groq integration could help prioritize it. Would you like help setting up your own API key with one of the current providers, or would you prefer to explore the HTTP API workaround?