> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

> Choose a native provider connection, a custom MCP server, or a webhook tool, then review its credentials and agent attachment.

An integration connects a workspace resource to an external service. Choose the connection method before creating tools or attaching the resource to an agent.

## Choose a connection method

| Method | Use it for | Start here |
| - | - | - |
| Native integration | A provider offered by the deployment's integration catalog. | [Cal.com](/agents-platform/configure/integrations/calcom) or [Calendly preview](/agents-platform/configure/integrations/calendly). |
| Custom MCP server | A server you operate or have reviewed and trust. | [MCP server configuration](/agents-platform/configure/integrations/mcp-servers). |
| Webhook tool | A documented HTTP action that you configure and authorize separately. | [Agent tools](/agents-platform/configure/tools/overview). |

<Note>
  The reviewed native catalog contains Cal.com and Calendly. Cal.com enables connection and tool-creation workflows; Calendly is a preview with self-serve connection disabled. The deployed catalog can differ. A listed provider, saved connection, or attached tool does not prove live agent execution.
</Note>

## Review the dashboard catalog

Open [Integrations](https://threetone.in/app/agents/integrations) in the intended workspace. The list combines installed native connections and saved MCP servers. Select **Add integration** to inspect available providers, search by name, or filter by category. Select **Add MCP server** for a custom endpoint.

Before connecting, review the provider, credential method, ownership, and allowed actions. A credential with access to a provider account can grant more access than one task requires. Use a dedicated account or appropriately limited credential where the provider supports it.

## Connect, create tools, and attach

These are separate changes:

1. A provider connection stores the relationship and credential reference.
2. Creating integration tools selects the provider operations the workspace needs.
3. Saving an agent draft preserves the selected tool or server identifiers. Later publication is available only for an eligible configuration; voice and custom-model publication remain gated.

Read each result back. Review changing shared resources separately from the agent's configuration diff. Check [current execution availability](/agents-platform/overview#current-availability) before planning a live demonstration.

## Credentials and environments

Use [auth connections](/agents-platform/configure/authentication/auth-connections) for supported reusable authentication and [workspace secrets](/agents-platform/configure/authentication/secrets) for private stored values. Native provider connections have their own managed credential workflow. Editing an unrelated secret does not automatically rotate a native provider connection.

Use [environment variables](/agents-platform/deploy/environment-variables) when a supported field needs a string, secret reference, or auth-connection reference for an environment. Keep personal API keys server-side.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Can I connect a provider that is absent from the catalog?" id="faq-integration-missing-provider">There is no verified native connection workflow for an absent provider. Review a custom MCP or webhook design where appropriate. Its credential, transport, and execution requirements still need verification.</Accordion>
  <Accordion title="Does Connected mean every action works?" id="faq-integration-connected">No. Verify the stored connection status, provider access, enabled operations, and the intended execution path separately. A label alone is insufficient.</Accordion>
  <Accordion title="Are integration tools added to an agent automatically?" id="faq-integration-agent-attachment">Creating a connection or tool is separate from saving the agent's attachment list. Follow the provider guide, attach the reviewed identifiers, and preserve a server draft. Publish only an eligible configuration on the intended branch.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.