Integrations for the agent and automations

Connect third-party apps so the Mintlify agent can use live context in Slack, during automation runs, or as a trigger for custom automations.

Integrations connect the Mintlify agent to other tools your team uses. The agent can use connected apps while responding in Slack or running an automation. Events from some shared integrations can also start a custom automation.

Integrations have one of two connection scopes.

• Shared integrations connect once for your organization. The Slack agent can use them, and you can add them as tools to supported automations. Shared integrations that provide events can also trigger custom automations.
• Personal integrations connect separately for each teammate. The Slack agent uses the personal account of the teammate who is chatting with it. Automations cannot use personal integrations as tools or triggers.

For example, if two teammates connect separate Google Drive accounts, each sees results from their own Drive when asking the agent a question in Slack.

There is no limit to how many teammates can connect their own accounts. In a Slack thread with multiple participants, the agent uses the personal integrations of each message's sender.

Admins and editors can connect shared integrations on behalf of the organization. Each teammate connects their own personal integrations.

1. Go to the Integrations page in your dashboard settings.
2. Find the integration you want to connect.
3. Click Connect.
4. Follow the authorization prompts.

You can also connect an integration while configuring an automation. Under Advanced options, select an unconnected app in the automation's Integrations field, then complete the authorization flow.

Prompt the agent to connect an app, such as "Connect Google Drive." The agent returns an authorization link in the Slack thread. Complete the authorization, then send another message in the same thread so the agent can confirm and use the connection.

The dashboard shows the integrations currently available to your organization.

After you install the Mintlify Slack app, the agent can use integrations while answering questions or updating your documentation. You do not have to select integrations for each Slack conversation.

The agent can use:

• Shared integrations connected to your organization.
• Personal integrations connected by the teammate who sent the request.
• Slack channels and threads that the installed Mintlify app has permission to read.

For example, ask the agent to compare a Linear issue with a Google Drive product brief or answer a question using a Notion page. You can also ask it to update documentation using context from a Jira issue.

The agent only accesses integration data when it is relevant to the request.

Automation tools give the agent additional context after an automation starts. You can select only shared integrations.

1. Open the automation's settings.
2. Expand Advanced options.
3. In Integrations, select the integrations that the automation can use.
4. Connect any selected integration that is not already connected.
5. Save the automation.

If an integration is an automation trigger, it is always a tool for that automation. This lets the agent retrieve additional details after it receives the event that started the run.

Custom automations can run when an event occurs in a supported shared integration or when a new message posts to a selected Slack channel.

1. Create or open a custom automation.
2. For Trigger, select Integration.
3. Select or connect a shared integration.
4. Select the Trigger event.
5. Complete any additional event fields that appear.
6. Save and enable the automation.

The supported events depend on the integration:

When the event occurs, Mintlify starts the automation and includes the event payload as context for the agent. Duplicate deliveries of the same event do not start duplicate runs.

When you use Slack messages as a trigger, only new top-level messages in selected channels start a run. Thread replies do not trigger automations.

The agent has read-only access through third-party integration tools. It can search and retrieve content, but it cannot use these tools to create, edit, or delete data in the connected app.

The agent inherits the access of the account that authorized the connection:

• For a shared integration, it can read content available to the connected workspace account.
• For a personal integration, it can read content available to the teammate who connected it.
• For Slack, it can read public and private channels that include the Mintlify app.

Authorization providers may group permissions differently. Review the authorization screen for the exact permissions requested before connecting an app. To narrow access, restrict the authorizing account's permissions or only grant the Mintlify app access to specific resources.

If your organization restricts which apps users can authorize, ask the relevant administrator, such as your Google Workspace or Atlassian administrator, to approve the Mintlify app.

1. Go to the Integrations page in your dashboard settings.
2. Find the connected integration and click Configure.
3. Click Disable integration.

Disconnecting a shared integration removes it for everyone in your organization. Automations can no longer use it as a tool, and custom automations configured to use it as a trigger stop receiving new events.

Disconnecting a personal integration only removes your connection. Other teammates keep their personal connections.

If an integration stops working:

1. Confirm that the authorizing account can still access the relevant content.
2. Open the integration's Configure dialog and disable it.
3. Connect the integration again and complete the authorization flow.
4. If the connection is for the Slack agent, send another message in the original Slack thread.

If an administrator blocks authorization, ask your app or workspace administrator to approve Mintlify. The authorization screen shows the app identity and permissions that require approval.

• Migrate from Confluence to Mintlify
• Automations overview
• Mintlify REST API introduction