Third Party Services
Third Party Services (shown in the app as Connected Services) are named accounts for external providers. Each connection stores credentials and a set of enabled capabilities. Agents, channels, knowledge bases, and service tools pick that connection by id — they do not store their own API keys.
This is not APIs (imported OpenAPI operations), MCP Integrations (outbound MCP clients), or Chat Integrations (Web / In App chat surfaces).
Providers
See Providers for the full list (OpenAI, Claude, Google, Twilio, Exotel, Pinecone, and more). Each provider page covers how to create keys or grant access on that vendor’s site.
When to use
- Attach your own provider keys, or use a platform-managed connection already available in the workspace
- Unlock channel types that depend on a connected messaging or voice account
- Expose provider actions as agent and workflow service tools
Connect a service
Open Integrations → Third Party Services and choose Connect Service.
- Pick a provider from the catalog. You can search by name or tags. Open that provider’s docs page for where to create the key or grant access.
- Enter a Name and save. The record starts Disconnected.
- Open the connection and choose Connect Now. Complete the provider form — API key, account fields, or OAuth sign-in.
Studio can add a named disconnected entry. You still finish Connect in this UI; Studio does not complete OAuth or paste credentials for you.
Manage the connection
The list shows Connected or Disconnected. Filter by name, status, and provider.
On a Connected detail page:
| Action | What it does |
|---|---|
| Re-Connect | Rotate keys or re-grant OAuth |
| Test | Validates the account and shows success or error |
| Disconnect | Stops using the account (confirm in the dialog) |
A disconnected connection stays in the list but is not usable until you connect again.
Enable capabilities
Each provider advertises features such as LLM, embeddings, STT/TTS, realtime voice, vector store, messaging, or OAuth apps. Only enabled capabilities are available when you pick this connection elsewhere.
On the detail page, after the service is connected:
- Toggle capabilities on or off.
- Use Test on an enabled capability to check that feature.
| Rule | Meaning |
|---|---|
| At least one enabled | You cannot turn off the last remaining capability |
| Must be connected | Disconnected connections cannot toggle capabilities |
| Extra OAuth scopes | Enabling a capability that needs new permissions may require Re-Connect |
Use platform-managed connections
Some connections are platform-managed (billed / admin-managed). They appear in the workspace for LLM and similar use without you attaching a key.
Host extras such as web search, code interpreter, and image generation cannot be enabled on those connections. Use your own connected account when you need those features.
Limits
- Disconnected services are ignored by agents, channels, and tools.
- A capability must be enabled on the connection before you can select it (for example LLM, STT, or a service tool).
- Studio cannot finish OAuth or credentials — connect in the UI after the record exists.
Where connected services are used
| Place | How |
|---|---|
| Agents | LLM / realtime LLM, STT/TTS, @ Service mentions, Services tools |
| Channels | Available channel types and routing service |
| Knowledge bases | Your own vector store (“Your own” provider) |
| Workflows, widgets, MCP Servers | Blocks that bind a serviceId |
| WhatsApp templates | Require a messaging-capable connected service with WhatsApp enabled |