18 Per-service connection guides
Step-by-step setup for each tool Claude Tag can connect to. Each guide covers the dedicated account to create, the credential to enter, and the URL to allow.
export const BetaNote = () => Claude Tag is in public beta. Features and behavior described here may change before general availability.;
Each guide covers one service: how to create the credential as a dedicated identity, what to paste into the Access bundle, and the Allowed websites value. For the model behind connections (credential types, Agent Proxy, allowed websites), see Give Claude access.
Always connect a dedicated account for Claude (for example, claude@yourcompany.example.com), not your personal login. Anyone in a channel under the bundle’s scope can use the connection through Claude, so whatever this account can reach is available to every member of those channels. See Create a dedicated account per service.
| Service | Category | Guide |
|---|---|---|
| Datadog | Monitoring | Connect Datadog |
| Sentry | Monitoring | Connect Sentry |
| PagerDuty | Monitoring | Connect PagerDuty |
| Linear | Issue tracking | Connect Linear |
| Asana | Issue tracking | Connect Asana |
| Jira and Confluence | Issue tracking | Connect Jira and Confluence |
| Notion | Knowledge and docs | Connect Notion |
| Google (Drive, Calendar, Gmail) | Knowledge and docs | Connect Google |
| HubSpot | Go-to-market | Connect HubSpot |
| Salesforce | Go-to-market | Connect Salesforce |
| Gong | Go-to-market | Connect Gong |
| GitLab | Code | Connect GitLab |
| BigQuery (custom) | Data warehouse | Connect BigQuery |
| Snowflake | Data warehouse | Connect Snowflake |
| Stripe | Billing | Connect Stripe |
| Vercel | Deployments | Connect Vercel |
GitHub is managed through the Claude GitHub App rather than a connection in this list; see Configure GitHub access.
Services marked (custom) have no preset button. Add them with Custom tool following their guide.
The presets and guides cover common services, not the full set Claude can connect to. Any app with an API can be added as a custom connection or a custom MCP server. See Connect a custom service for the credential types and form fields.
18.1 When a connection fails after setup
If Claude says it can’t reach a service you connected, start with the checks at the top of Troubleshoot Claude Tag setup. Confirm the connection is in a bundle attached to the channel’s scope, and rerun the test in a new thread, since a session loads its connections when it starts.
Two entries on the troubleshooting page cover connection failures directly:
- A connection works in one channel but not another: bundles attach per scope, so the failing channel’s scope is likely missing the bundle
- I hit an authentication error and couldn’t finish this turn: Claude posts that message when its own request fails an authentication check. A connected service’s failing credential surfaces as a tool error inside Claude’s reply instead