Connections & Integrations FAQ

How do I add a new connection?

Go to the Connections Marketplace from the sidebar. Browse or search for the service you want to connect. Click Add Connection and follow the setup flow. Depending on the service, you will either enter an API key or go through an OAuth authorization flow. Once added, the connection and all its tools are available to use in your automations and agents.

What is the difference between OAuth and API key connections?

OAuth connections authenticate through the service's own authorization flow: you are redirected to the service, grant permissions, and Chase Agents receives a token that it stores and refreshes automatically. API key connections use a key you generate from the service's developer settings and paste directly into Chase Agents. OAuth is more secure and handles token refresh automatically. API keys are simpler but require you to manage rotation manually.

Can I connect a service that is not in the Marketplace?

Yes. Use the Custom Connectors feature to add any service with a REST API. Provide the base URL and your credentials. Chase Agents uses the service's OpenAPI spec or a manually configured endpoint list to expose the service's endpoints as tools. This means any modern web service can be connected, not just those with native MCP servers.

How do I share a connection with my team?

When creating or editing a connection, set its access type to WorkspaceWide to make it available to all workspace members. Alternatively, set it to SpecificTeamMembers and select the users who should have access. Personal connections are private to you. Only workspace admins can change a connection's access type after it is created.

Why is my OAuth token expiring?

Chase Agents refreshes OAuth tokens automatically using the PKCE flow before they expire. If you are seeing authentication errors on an OAuth connection, the most likely causes are: you revoked the token from the external service's settings; the external service changed its OAuth configuration; or the scopes granted during the original authorization are no longer sufficient for the operations being attempted. Re-authorize the connection to resolve these issues.

Can I connect to my own internal tools?

Yes, as long as your internal tool is accessible via a public URL. Chase Agents blocks connections to private network addresses (localhost, internal IP ranges) as a security measure against SSRF attacks. Internal tools must be exposed through a public URL or a secure tunnel service to be connectable from Chase Agents. Enterprise customers can discuss private network connectivity options with the team.

How do I test if a connection is working?

From the Connections Marketplace, find the connection and open it. Use the health check feature to verify the connection can authenticate and make a test call to the service. A successful health check confirms the credentials are valid and the connection is ready to use in automations.

What if the service I need is not supported?

Use the Custom Connectors feature to add any REST API-based service. If the service you need is not a REST API service or has specific integration requirements beyond what custom connectors support, post a connection request in the Discord feature-requests channel. High-demand connections are prioritized for native MCP server development.