Skip to main content
Give Cassidy access to the right external information and actions while keeping permissions and credentials under control.

​
What you’ll learn

  • When to use a Knowledge Base integration, Connector, or Workflow
  • How synced content gives Cassidy searchable company context with citations
  • How Connectors let Agents read and update live information in business apps
  • How personal and shared connections affect whose external account and permissions Cassidy uses
  • How to connect unsupported systems with Custom Connectors, webhooks, or API requests
  • How to protect credentials with secret storage and narrowly scoped access

​
Put it into practice

1

Choose the right connection method

Use a Knowledge Base integration for searchable company content, a Connector for live reads and writes in an Agent conversation, or a Workflow for a repeatable process with defined Triggers and Actions.
2

Test access and approvals

Connect one business app and test a read action. Before enabling writes, review whether the connection is personal or shared and when Cassidy should ask for approval.
3

Connect a non-native system

Create a Custom Connector when the service provides an MCP server. For other systems, use a webhook or the Send API Request Workflow Action.
4

Protect credentials

Store credentials in Workflow secret keys or a Skill’s API Keys & Headers settings. Never place credentials directly in instructions, prompts, or code.
Shared connections let other people act through the connected account. Grant only the access your team needs and review write permissions before sharing.

Overview of integrations

Compare the ways Cassidy connects to external systems.

Connect and manage business apps

Configure live data access for Agents.

Connect non-native apps

Use webhooks and APIs when Cassidy has no native integration.

Understand prompt engineering

Continue by writing clearer instructions for connected work.