Connection scope
Integrations connect in one of two ways:- Shared integrations connect once for your entire organization. Anyone on the team can prompt the agent to use them. Slack, Notion, Linear, Jira, Confluence, Salesforce, Intercom, HubSpot, and Plain all connect this way.
- Personal integrations connect per user. Each teammate authorizes their own account, and the agent can only use a personal integration on behalf of the user who connected it. Google Calendar and Google Drive are personal.
Connect an integration
Admins and editors can connect shared integrations on behalf of the organization.- Go to the Agent integrations page in your dashboard.
- Find the integration you want to connect.
- Click Connect.
- Follow the OAuth prompts to authorize Mintlify to access your account.
Supported integrations
| Integration | Scope |
|---|---|
| Confluence | Shared |
| Google Calendar | Personal |
| Google Drive | Personal |
| HubSpot | Shared |
| Intercom | Shared |
| Jira | Shared |
| Linear | Shared |
| Notion | Shared |
| Plain | Shared |
| Salesforce | Shared |
| Slack | Shared |
How the agent uses integrations
The agent uses connected integrations as tools. When you ask the agent a question or give it a task, it can search and retrieve content from your connected apps to build context. For example:- “Summarize the Slack thread about the v2 API migration and write it up for the knowledge base.”
- “Check the Linear ticket for this feature and document the behavior.”
- “What did the team decide about rate limiting? Check Slack.”
Permissions and access
Each integration requests the OAuth scopes or API-key permissions it needs to search and retrieve content from the connected app. Mintlify requests read-only scopes wherever the provider offers them. Review the exact scopes during the OAuth consent screen before authorizing the connection. The consent screen lists every permission the agent receives, and you can revoke the connection at any time from the dashboard or from the connected app’s own integrations settings. If your organization restricts which apps users can authorize, ask the relevant admin (such as your Slack or Google Workspace admin) to allow the Mintlify integration before connecting.What the agent can read from each app
The agent inherits the access of the account that authorized the connection. It can only read content that the authorizing user (for personal integrations) or the connected workspace account (for shared integrations) already has access to in the source app.| Integration | Content the agent can access |
|---|---|
| Confluence | Pages and attachments in spaces the connected account can read |
| Google Calendar | Events on calendars the connected user can view |
| Google Drive | Files and folders the connected user can view, including shared drives |
| HubSpot | CRM records (contacts, companies, deals, tickets) the connected account can read |
| Intercom | Conversations, contacts, and help center articles the connected account can read |
| Jira | Issues and comments in projects the connected account can read |
| Linear | Issues, projects, and comments in teams the connected account can read |
| Notion | Pages and databases explicitly shared with the Mintlify integration |
| Plain | Threads and customer records accessible with the provided API key |
| Salesforce | Standard and custom objects the connected account can read |
| Slack | Public channels the workspace grants access to, plus private channels you add the Mintlify app to |
Data retention after disconnect
When you disconnect an integration, the agent immediately loses the ability to read from that app. Mintlify doesn’t retain a durable copy of integration content. The agent fetches data on each request through the live OAuth token or API key, so disconnecting cuts off future access. Content that appeared in past agent responses or pull requests stays in place (chat transcripts, published pages, PR history). If you also want that content removed, edit or delete the pages and conversations directly.Troubleshoot a failed connection
If an integration stops working or shows an error in the dashboard, the underlying OAuth token has usually expired, been revoked in the connected app, or had its required scopes changed. To restore access:- Go to the Agent integrations page in your dashboard.
- Find the affected integration and click Configure.
- Click Disconnect.
- Click Connect.
- Complete the OAuth flow.
Disconnect an integration
- Go to the Agent integrations page in your dashboard.
- Find the connected integration you want to disconnect.
- Click Configure.
- Click Disconnect.