Choose a connection method
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.
Review the dashboard catalog
Open 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:- A provider connection stores the relationship and credential reference.
- Creating integration tools selects the provider operations the workspace needs.
- 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.
Credentials and environments
Use auth connections for supported reusable authentication and workspace 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 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
Can I connect a provider that is absent from the catalog?
Can I connect a provider that is absent from the catalog?
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.
Does Connected mean every action works?
Does Connected mean every action works?
No. Verify the stored connection status, provider access, enabled operations, and the intended execution path separately. A label alone is insufficient.
Are integration tools added to an agent automatically?
Are integration tools added to an agent automatically?
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.