Connect your AI provider keys
Add, replace or remove the OpenAI, Anthropic, Azure Speech and Azure Translation keys your AI features run on.
- Plan
- Depends on your plan · Which plan do I need?
- Who can use this
- Account owner, Manager
Add, replace or remove the OpenAI, Anthropic, Azure Speech and Azure Translation keys your AI features run on.
The AI features in your workspace run on your own AI provider accounts. You add an API key for each provider you want to use. The provider bills you directly for what you use. There is no shared key, so a feature that needs a key does not work until you add one.
Sidebar → AI → Configuration → Integrations. The page is titled Integrations and lists your AI provider credentials with a "connected" counter.
You see the AI menu only if your role has the chatbot management permission. The AI pages need the ai_agent plan feature. Without it, the menu items show a lock and open an upgrade page.
ai_agent).sk-). You find it on the provider's site under API keys.sk-ant-), created in the Anthropic console under API keys.eastus, centralindia or westeurope. The region is shown on the resource's Overview page in the Azure portal.| Provider card | What it powers |
|---|---|
| OpenAI | Knowledge base (adding documents, search, AI answers), translating messages in the inbox, and voice-to-text in chatbots |
| Anthropic (Claude) | Knowledge-base answers and document processing, only when you pick a Claude model in the knowledge base's AI models. Embeddings still use OpenAI. |
| Azure Speech | Azure speech-to-text and text-to-speech blocks in chatbots |
| Azure Translation | The Azure translate block in chatbots |
| Pinecone | Older (legacy) knowledge sources only. New knowledge bases do not need it. |
Each provider has a card that shows Connected or Not connected, and the top of the list shows how many are connected.
For Azure, fill in the Subscription Key and the Region instead.
When the check passes, you see "<Provider> connected" and the card shows Connected.
The old key is never shown back to you.
The new key is tested first. If the test fails, nothing changes and the old key stays in use.
The dialog names what the key is used for and warns that everything that uses it stops working until you connect a key again, including AI agents, bots and knowledge bases that rely on it.
You see "<provider> key removed" with a list under Stops working now. The card changes to Not connected.
There is no undo. To use the features again, connect a key again. Only workspace managers can remove a key.
The Integrations page has no Test button. A key is tested only when you connect or update it.
ai_agent). Check it under Billing → Current Plan.Key changes are made only from an external AI client (for example a desktop AI app connected to your workspace), by a manager. The in-panel Copilot does not offer these tools.
Do it with Copilot
Do it with Copilot
These prompts work only from an external AI app connected to your workspace, not in the panel's Copilot.
Do it with Copilot
Do it with Copilot
Removing a key always needs a person's approval in the panel, and it cannot be undone.
Never paste a secret key into a chat you share with other people.
| What you see | Why | What to do |
|---|---|---|
| "API key is required" / "Subscription key and region are required" | A field is empty | Fill in every field, including the full key when you edit |
| "<Provider> rejected this key (invalid key). Nothing was saved; the previous key (if any) is still in use." (for Azure: "invalid key or wrong region") | The provider refused the key | Copy the key again from the provider. For Azure, check that the region matches the resource. |
| "<Provider> region not found — check the region name." | The region name is wrong | Use the region name from the Azure portal, in lower case with no spaces (for example centralindia) |
| "<Provider> says this key is out of quota or rate-limited, so it was not saved. Add credit / wait, then try again." | The provider account has no credit, or is busy | Add credit or wait, then try again |
| "Could not reach <Provider> to check this key, so it was not saved." | The provider did not answer | Try again in a few minutes |
| "Credentials for … is already exist." | A key for this provider is already saved | Use Edit on the card instead of Connect |
| "OpenAI API key not configured. Connect OpenAI in Integrations first." (in the knowledge base: "OpenAI key needed" with an Add key button) | A feature needs OpenAI and no key is saved | Connect OpenAI |
| "Anthropic API key not configured. Connect Anthropic in Integrations first, or pick an OpenAI model." | The knowledge base uses a Claude model and no Anthropic key is saved | Connect Anthropic (Claude), or pick an OpenAI model in the knowledge base's AI models |
| "<provider> key is still in use" | A legacy (older) data source still uses this key | Migrate or delete it under Legacy Sources, then remove the key again |
| "Too many key changes" | Keys can be changed 5 times per hour | Wait, then try again |
| "You can't remove this key" | Only workspace managers can remove AI provider keys | Ask a manager |
| "Stored OpenAI credentials could not be read. Please reconnect OpenAI in Integrations." | The saved key could not be used | Click Edit on OpenAI and save the key again |