Integrations

Integrations pull meeting context from the tools you already use. Every connection runs over OAuth 2.1 with PKCE. Tokens live on your machine. We never see your Jira tickets, your Confluence pages, your Drive docs, or your Slack messages.

What it adds. Tickets referenced on the meeting invite or recently touched by attendees surface in the Meeting Brief. Live coaching can reference ticket context mid-call so you do not have to flip tabs to remember where a story stands.

1. Open Settings > Integrations > Jira.
2. Click Connect.
3. Pick your workspace in the Atlassian window.
4. Approve the scope and come back to the app.

Scope requested. Read access to issues the connected Atlassian account can already see. Nothing beyond what you can view directly in Jira.

Disconnect. Open Settings > Integrations > Jira and click Disconnect. The app revokes the token with Atlassian and deletes the local copy.

What it adds. Confluence pages that reference the project or the attendees surface in the Meeting Brief. Live coaching can quote relevant paragraphs when the topic on the call matches.

1. Open Settings > Integrations > Confluence.
2. Click Connect. This shares the Atlassian OAuth flow with Jira, so if Jira is already connected the handshake finishes in a click.
3. Approve the scope.

Scope requested. Read access to pages the connected Atlassian account can see.

Disconnect. Open Settings > Integrations > Confluence and click Disconnect.

What it adds. Attach specific documents to a meeting using the Google Picker. Content from the docs you pick feeds the Meeting Brief and the live coaching context.

1. Open Settings > Integrations > Google Drive.
2. Click Connect.
3. Grant the drive.file scope.

Scope requested. drive.file. This is file-scoped, not whole-drive. Only files you specifically pick in the Google Picker are ever visible to the app. The rest of your Drive stays invisible to IntelliPrompter even after you connect.

Disconnect. Open Settings > Integrations > Google Drive and click Disconnect.

What it adds. Recent threads in a channel linked to the meeting surface in the Meeting Brief. After the call, you can send a meeting summary back into Slack.

1. Open Settings > Integrations > Slack.
2. Click Connect.
3. Pick the workspace.
4. Approve the scope.

Scope requested. Channel history read for channels you add, plus write access for the channel you send summaries into. Channels you have not added stay invisible to the app.

Disconnect. Open Settings > Integrations > Slack and click Disconnect.

• Stored in your Mac keychain.
• Encrypted at rest by macOS.
• We never see them.
• If you wipe your machine, the tokens are gone with it.

• We do not sync your Jira, Confluence, Drive, or Slack to a cloud copy. There is no mirror on our side.
• We do not read anything you have not asked us to pull.
• Each integration call is on-demand. Something you did (a meeting starting, a brief being generated, a summary being sent) triggers the fetch. The app is not quietly scanning your tools in the background.

You can also revoke a token from the provider directly. Atlassian, Google, and Slack all offer an “Authorized apps” list in account settings. Removing IntelliPrompter there kills the token even if you never open the app.

The next time the app tries to use a revoked token, it fails the request and prompts you to reconnect. Nothing breaks loudly. The affected integration just stops surfacing results until you reconnect.

If an integration shows Connected but is not pulling anything into the brief, try Settings > Integrations > [provider] > Reconnect. The two most common causes:

• The refresh token expired and needs a fresh handshake.
• The scope was changed on the provider side (an admin tightened permissions, or you removed the app and re-added it).

• Meeting Brief. See what integrations feed into once connected.
• Privacy Modes. Pick a mode per meeting on top of your integration setup.
• Privacy policy. The full data-handling statement.
• Troubleshooting. Other common fix paths beyond integrations.