Skip to main content

​
Overview

The Slack connection allows Qontext to read messages and threads from channels in a connected Slack workspace and ingest their text content into your Context Vault.
Only channels and content that the connected Slack app can access will be ingested into your vault.
Supported data types:
ObjectDescription
Channel messagesMessages posted in channels the app is invited to
ThreadsReplies and thread conversations linked to channel messages

​
Setting up the connection

You can connect Slack from your Qontext vault, authorize access in Slack, then choose how often to sync. The steps below walk you through the full flow.
1

Open Data Sources in your vault

In the Qontext app, open the vault where you want Slack data, then go to the Data Sources tab and click Add data source.Data Sources tab in a Qontext vault
2

Select Slack as the data source

Choose Slack from the list of available data sources. This starts the Slack connection flow.Select Slack from the list of integrations
3

Connect your Slack workspace

You can reuse an existing connection (if you’ve already connected this Slack workspace to Qontext) or create a new connection.Choose an existing connection or create a new oneIf you create a new connection, sign in to Slack when prompted and select the workspace you want to connect. On the Slack consent screen, review the requested permissions and click Allow. At this step the Qontext app is added to your Slack workspace so it can read the channels you authorize in the next step.Slack OAuth permissions consent screen
4

Configure what to sync (filters)

Select the channels you want Qontext to ingest. Only channels in which the Qontext app is a member can be ingested.
Public channels are automatically joined by the Qontext app when you select them.For private channels, the Qontext app must be added as a member first. In Slack, open the channel and type /invite @Qontext.
Select Slack channels to syncYou can add a time filter to limit how far back messages are synced. The time filter is only available after a channel has been selected: click All at the top next to the selected channel to open the date range option.Slack time filter by date
5

Set sync frequency

Choose how often Qontext should refresh data from Slack (e.g. daily, weekly, monthly). More frequent syncs keep the vault up to date but use more resources.Sync frequency settings
6

Set ingestion instructions (optional)

You can add ingestion instructions that tell Qontext how to interpret or prioritize the synced data. This step is optional.Ingestion instructions field
7

Review and create connection

Review your choices (workspace, channels, time filter, frequency), then confirm to create the connection. Qontext will start the initial sync shortly after.Review summary and create Slack connection

​
Managing permissions

​
Slack OAuth scopes

When you connect Slack, you’ll see a consent screen titled Allow the ‘Qontext’ app to access Slack. It lists the permissions (scopes) Qontext needs; they are read-only. You’ll see categories such as: 
- Content and info about channels & conversations — Messages, files, and other content in public and private channels, direct messages, and group conversations.
- Content and info about your workspace — User lists, channel lists, workspace settings, and other workspace-level metadata.
Granting these scopes is required for the connection to work. Qontext only reads data from Slack to ingest it into your vault; it does not post messages or change anything in your workspace.

​
Sync latency

The initial sync time depends on how many channels and messages are in scope. Large workspaces with many active channels can take up to 12 hours to fully index.
Subsequent syncs process incremental changes and typically complete much faster than the initial sync.

​
FAQ

Any Slack workspace Admin or member with permission to install apps can set up the Slack connection. Ensure the account can invite the Qontext app to the channels you want to ingest.
Yes. You can connect multiple Slack workspaces from the Data Sources tab in your Qontext vault. Add each workspace as a separate data source.
Disconnecting stops further syncs. Content already ingested from Slack remains in your vault until you request deletion. For data removal, contact support@qontext.ai.
Initial sync time varies: small or lightly used workspaces may finish in under an hour; very active workspaces with many channels and messages can take up to 12 hours. Subsequent syncs are incremental and faster.
Reconnect the integration and verify that the Qontext app is still invited to the relevant channels and has the required scopes. If the issue persists, contact support@qontext.ai.
Yes. All data is encrypted in transit (TLS) and at rest. Qontext only accesses channels and messages you explicitly authorize via the Slack OAuth flow.