Rovo Slack connector not surfacing channel content

Question

Hi all,

We connected the Slack connector in June 2026, so we're on the new architecture where Slack search happens directly through Slack rather than Atlassian-side indexing.

Setup:

* Slack connector enabled in admin.atlassian.com, scoped to a specific public channel (#example)
* Custom Rovo agent created with Slack added as a knowledge source
* Confluence is also connected and working correctly as a knowledge source for the same agent

Issue:
The agent isn't surfacing any content from the Slack channel when answering questions, even though the connector shows as connected/authorized. It only appears to be using Confluence.

Questions:

Does the Slack connector index/search thread replies, or only top-level channel messages? Our team typically posts questions as top-level messages and answers in threads, so if only top-level messages are searchable, that would explain why the agent isn't finding useful content (the actual answers live in threads). Is there a way to verify indexing/search status for a specific channel, to confirm the connector is actually pulling from it?

We found a similar unresolved report ("Slack Integration Not Working - Rovo") where a connector showed as connected but returned no Slack results in Rovo prompts despite working in Confluence search, wondering if this is a related/known issue.

Thanks in advance for any guidance.

Arkadiusz Wroblewski · Answer

Hi and welcome to Atlassian Community @Ricardo Filho

Where was that channel scope configured? You connected Slack in June 2026, so you're using the newer Direct Slack connector.

There's a separate Atlassian Rovo Slack app where you can add Rovo/custom agents to Slack channels and configure triggers. I want to be sure these two configurations aren't mixed.

Open full Rovo Search, filter source to Slack, and search for: a unique phrase from a top-level #example message; and a different unique phrase only inside a thread reply.

That will tell us much more than connector's green status.

Best,

Arek 🤠

Gabriela - LeanZero · Answer

Hi @Ricardo Filho, a green connector in admin.atlassian.com is only the admin half of it. The other half is per person. Each user links their own Slack account to their Atlassian account, and it sits under Next steps on the connector page. Atlassian's wording there is hedged, users "may be asked to connect before they can see results" and might not be if that account has connected Slack before, but the reason is flat enough, "so Teamwork Graph can make sure your teammates only see results they usually have access to". An agent inherits it, since it "respects the permissions of the user who prompted it". Confluence is first party and needs no personal link, so an unlinked Slack account gives you the exact split you are describing. Whether it is what you have I cannot tell from here, and I have not run this connector on a tenant of my own, so all of this is off Atlassian's docs and the tracker.

Ask the same question in full-page Rovo Search and select Slack from the app list on the right, signed in as the account that got the empty agent answer. If it asks you to connect, that is your answer. It is per person, so clearing it for yourself clears nothing for whoever else tried the agent. Slack content in Search and still nothing from the agent means it is one for support, with AI-1262 quoted in it. No prompt and nothing from #example in Search either, and the connector is not reaching that channel at all, which sends you into Slack.

Threads are not it. If only top-level messages were searchable you would still be getting top-level messages, and you are getting nothing. That page says nothing about threads either way, its only exclusion is files and canvases, and Slack's own search returns replies.

That Search run is also your per-channel check, since there is no per-channel status screen on the Atlassian side and no index behind this connector to inspect. There is no channel picker in it either. The Atlassian configuration is a nickname, a disclaimer and Authorize Slack, and the page lists messages in all channels, public and private, plus DMs, so I would expect the #example scoping came out of the Slack authorization step. A Slack app with access to one channel is its own reason for thin results.

The report you found predates the October 2025 rewrite, so the mechanism behind it is not yours. The symptom carried over though, which is what AI-1262 is about, Support Slack connector results in Rovo Chat and Agents, raised 3 November 2025 and closed Done on 23 July 2026. A month before you posted. Its own listed workaround is to use Rovo answers to surface Slack content.