Skip to main content
Automation integrations require an Enterprise plan.
Integrations give automations access to context from other tools that your team uses. Once connected, an automation can search Slack threads, read Notion pages, look up Linear issues, and pull context from other apps to inform its content updates.

​
Connection scope

Integrations connect in one of two ways:
  • Shared integrations connect once for your entire organization and are available to your automations. 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. Google Calendar and Google Drive are personal.
Personal integrations keep user-specific data, like calendar events, scoped to the user who connected the integration instead of shared across the organization.

​
Connect an integration

Admins and editors can connect shared integrations on behalf of the organization.
  1. Go to the Integrations page in your dashboard settings.
  2. Find the integration you want to connect.
  3. Click Connect.
  4. Follow the OAuth prompts to authorize Mintlify to access your account.
Some integrations open an additional configuration step before the connection completes. Jira, Confluence, and Salesforce ask for your workspace URL or subdomain before the OAuth flow begins. API-key providers like Plain prompt you to paste an API key.

​
Supported integrations

​
How automations use integrations

Automations use connected integrations as tools. When an automation runs, the agent can search and retrieve content from the connected apps you enabled for that automation to build context for its updates. To enable integrations for an automation, open the automation’s settings and select the integrations you want the agent to use in the Available integrations section. Only integrations already connected for your organization appear in the list. See Manage automations for details. The agent only accesses integration data when it’s relevant to the automation’s task. It does not proactively read from connected apps.

​
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 integration 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. To narrow what the agent can see, restrict the connected account’s permissions in the source app. For example, invite the Mintlify Slack app only to specific channels, or share only selected Notion pages with the integration.

​
Approve the Mintlify app in Atlassian (Jira and Confluence)

If your Atlassian organization restricts marketplace or custom apps, your Atlassian admin has to approve the Mintlify app before anyone can connect Jira or Confluence. Users attempting to connect without approval see an authorization error on the OAuth consent screen. App identity:
  • App name: Mintlify
  • App ID: 872a4b8e-9e83-474d-99f9-dc79112da145
Admin steps:
  1. Go to admin.atlassian.com and open your organization.
  2. Go to Security > Data protection > Data security policy.
  3. Check the Marketplace and custom app access control setting. If it shows Blocked or Custom, the Mintlify app needs to be allowed.
  4. Edit the policy and either set the control to Allowed, or add an override for the Mintlify app using the app ID above.
  5. Click Activate to apply the policy.
After the policy is active, an admin or editor can complete the Jira or Confluence connection from the Integrations page.

​
OAuth scopes Mintlify requests

Mintlify uses Atlassian’s OAuth 2.0 (3LO) flow and requests read-only scopes so the automation agent can search and read the tickets or pages it needs to ground its updates. Mintlify does not request write, delete, or admin scopes. Jira scopes: Confluence scopes: The full list of scopes granted to the connection is shown on the Atlassian OAuth consent screen when a user first authorizes the integration, and can be reviewed at any time in your Atlassian admin console under Connected apps.

​
What Mintlify does with the data

  • Access is read-only. Mintlify never creates, edits, transitions, or deletes issues, comments, pages, or attachments.
  • Access is inherited from the authorizing user. The agent can only see projects and spaces that the connected Atlassian account already has access to. To narrow visibility, restrict the connected account’s project and space permissions in Atlassian.
  • Access is on-demand. The agent reads from Atlassian only when an automation run needs that context. Mintlify does not crawl or mirror Jira or Confluence into a durable copy.
  • Revocation is instant. Disconnecting the integration in the Mintlify dashboard, or revoking the app in Atlassian admin, immediately cuts off future access.

​
Data retention after disconnect

When you disconnect an integration, automations immediately lose the ability to read from that app. Mintlify doesn’t retain a durable copy of integration content. The agent fetches data on each run through the live OAuth token or API key, so disconnecting cuts off future access. Content that appeared in past automation runs or pull requests stays in place (published pages, PR history). Edit or delete the pages directly if you also want that content removed.

​
Troubleshoot a failed connection

If an integration stops working or shows an error in the dashboard, the underlying OAuth token usually expired, the connected app revoked it, or its required scopes changed. To restore access:
  1. Go to the Integrations page in your dashboard settings.
  2. Find the affected integration and click Configure.
  3. Click Disconnect.
  4. Click Connect.
  5. Complete the OAuth flow.
For API-key providers like Plain, generate a new API key in the source app and paste it into the integration’s configuration. If automations still can’t access data after reconnecting, confirm that the authorizing user has permission to view the relevant content in the source app.

​
Disconnect an integration

  1. Go to the Integrations page in your dashboard settings.
  2. Find the connected integration you want to disconnect.
  3. Click Configure.
  4. Click Disconnect.
Disconnecting a shared integration removes it for everyone in your organization, and automations immediately lose access to that tool. Disconnecting a personal integration only removes your own connection. Other teammates who have connected the same integration keep their access.