Slack AI Agent: Connect Slack to Omni

What a Slack AI agent integration with Omni does

Our Slack connector connects a Slack workspace to Omni for indexing and searching supported messages, threads, and files. We index public and private channels where the bot is a member, as well as 1:1 and group DMs where the bot participates. We can also index supported file attachments shared through those conversations.

It is important to remember that crucial business information is not always documented. For example, decisions on products can be made during a project discussion, workarounds for customers can be decided in a support chat, and reasons for changes made by the engineering team can be explained in a discussion rather than a ticket.

By bringing such information into Omni, workers can search Slack context with information from other connected sources. We apply synced Slack permissions when retrieving indexed Slack content. Access rules for other sources depend on their connectors.

Omni vs Slackbot and Agentforce: which do you need?

Slackbot and Omni approach workplace AI from different directions.

Salesforce announced the general availability of Slackbot on January 13, 2026, with a phased rollout to Business+ and Enterprise+ customers through January and February. The product is integrated within the Slack environment and acts as an individual workplace agent that uses Slack chats, company data, and connected workflows.

Slack also offers Agentforce agents, allowing employees to interact with Salesforce-powered agents within their Slack workflows. Slack announced Agentforce in Slack on January 14, 2025.

We take a broader cross-tool approach. Rather than making Slack the primary interface, we connect Slack with other company systems as sources of company-wide context. You can self-host Omni and choose from multiple models and providers, including OpenAI-compatible endpoints.

The distinction is useful when choosing an approach:

Slackbot: A Slack-native workplace agent for finding information, organizing work, and taking actions within Slack and connected environments.
Agentforce in Slack: Brings Salesforce agents into Slack so employees can work with those agents through the Slack experience.
Omni: Uses Slack as one of the many connected sources alongside systems such as Jira, GitHub, HubSpot, and Fireflies.

Both approaches can be employed to serve various purposes in the enterprise setting. If teams feel strongly attached to the Slack and Salesforce platforms, the preferred approach would be to employ Slack-native agents. If teams require a self-hosted, multi-tool agent, then Omni will be useful for integrating Slack with a wide range of application tools.

Using Slack with Omni

We connect Slack as a data source for search and company context. Our connector indexes supported messages, threads, files, and direct messages so you can search them in Omni alongside your other company tools.

A native Slack chat experience is planned. Today, employees use Omni’s web experience to work with connected Slack content and information from other systems. This connector does not add an Omni chat interface inside Slack. Slack separately supports third-party agents and Agentforce experiences.

What an AI agent for Slack can do with company-wide context

A useful AI agent for Slack doesn’t have to assume that each of the conversations is an isolated piece of data. As Slack becomes integrated with other systems of the business, conversations may become part of larger project status insights, incident investigations and other internal workflows.

Investigate an incident across Slack, Jira, and GitHub

For instance, consider the case where an engineering team talks about a production bug on a Slack channel and logs the same in a Jira ticket while working on a GitHub pull request to fix the issue. Integration will help Omni link all the three together so that an employee can easily understand the discussions that took place, what was logged, and how the problem is being fixed through code changes without manually searching each system.

You can find more related information in our Jira integration documentation.

Combine customer conversations with HubSpot records

The customer issue can initially be found in a Slack conversation between the sales, support, and product departments. The HubSpot record associated with the problem can include information on the customer organization, the stage of the deal, tickets, emails, appointments, or any notes. The integration of Slack with HubSpot will allow Omni to assemble all this information when Sales or Account representatives are researching an account or preparing for a customer interaction.

More related information can be found in our HubSpot integration documentation.

Connect Slack decisions with Fireflies meeting transcripts

An organization may deliberate on an issue in Slack following its discussion at a recorded meeting in Fireflies. Fireflies can offer transcripts, meeting notes, action points, and meeting data, whereas Slack will offer discussion about the issue. It is important to connect the two sources to enable the employees to understand what was discussed at the meeting and later decided in Slack.

To find out more, check our Fireflies integration documentation.

This is how cross-tool context may provide greater value than just searching through Slack. Slack contains conversations and decisions, but connected systems may include the tickets, code, customers' data, transcript of the meeting, and many other details that help in understanding the whole context.

How to connect an AI agent to Slack

Connect your Slack workspace to Omni in five steps:

Create a Slack app

Create a Slack app for our connector using the app manifest in our setup guide. The connector uses a read-only bot.
Install the app in the Slack workspace

Install the app in the relevant Slack workspace and authorize the permissions required by the connector. Workspace admin access is a prerequisite for installing the app.
Give the bot access to relevant channels

During sync, the bot automatically joins all public channels. For private channels, explicitly add the Omni bot to the channels you want indexed.
Connect Slack in Omni

Open Settings → Integrations in Omni, select Slack, and provide the Slack Bot User OAuth Token required by the connector. An App-Level Token can also be provided if real-time updates through Socket Mode are enabled.
Start the synchronization

Configure the Slack source, then start the initial sync. We support full and incremental syncs, plus near real-time message indexing through Slack Socket Mode when an app-level token is provided.

The initial sync indexes the last two years of history per conversation by default. You can adjust the history horizon in your deployment’s Slack connector configuration.

Follow our Slack connector guide for the full app manifest, permissions, app configuration, and synchronization options.

Permissions: what Omni reads from Slack

Permissions are important when workplace conversations are connected to an AI agent.

Our Slack connector uses a read-only bot. We index messages in public and private channels where the bot is a member, and 1:1 and group DMs where the bot participates. During sync, the bot automatically joins all public channels.

For private channels, you must add the bot manually. The bot can see DMs it participates in. Slack’s bot tokens cannot read private DMs between two other users.

We apply synced Slack channel and DM permissions when retrieving indexed content, so search results are filtered using the access information from Slack. See our Slack connector guide for source access details.

The connector is read-only, so Omni cannot post Slack messages or modify Slack content through this integration.

Omni is also open-source software under the Apache 2.0 license, meaning that you can view the implementation and run the software in your own environment. You can self-host using Docker Compose or Terraform-based deployment options.

Review the Omni open-source code on GitHub.

Works better together

Connecting Slack with other tools gives an AI agent more context for specific tasks:

Slack + Jira

Identify a production issue that was discussed on the Slack thread and linked to a Jira ticket, with details of the problem and its resolution recorded.

Jira integration

Slack + Fireflies

Link a Slack follow-up discussion with the Fireflies transcript and action items from the meeting which resulted in the decision being made.

Fireflies integration

Slack + HubSpot

Combine the internal Slack chat about the customer with HubSpot deals, tickets, emails, and account activity.

HubSpot integration

Omni brings together context from company tools rather than working with one system at a time. Browse our integrations for Slack, Jira, GitHub, Fireflies, HubSpot, and other supported workplace systems.

FAQs

Is this the same as Slack AI or Slackbot?

No. Slackbot is a Slack-native workplace agent that Salesforce announced on January 13, 2026, with a phased rollout to Business+ and Enterprise+ users. Omni is a different AI agent platform that connects Slack to other company systems and can run on your own infrastructure.

Slackbot announcement

Can Omni read private channels and DMs?

Yes, when the bot has access. Private channels need the bot to be invited, and 1:1 or group DMs can be indexed only when the bot participates in the conversation. Bot tokens cannot read private DMs between two other users. We apply synced Slack permissions when retrieving indexed content.

Slack connector guide

Can employees talk to Omni inside Slack?

Not through this connector. Slack is currently a connected source for indexing and search in Omni, not a native Omni chat application within Slack. A native Slack experience is planned.

Slack connector guide

Does the Slack integration work on self-hosted Omni?

Yes. You can run Omni and the Slack connector in your own environment. You can also use other model providers and OpenAI-compatible endpoints while keeping Omni self-hosted. Docker Compose and Terraform deployment options are available.

Deployment options