Product guide

Team chat

The conversations where decisions actually happen — Slack, Teams, Discord and more — brought in read-only.

This category covers wherever your team already talks: Slack, Teams channels, Google Chat, Mattermost, Discord and Webex (spaces). Each turns a platform's channel or space history into monthly chat-log documents, so a decision made in chat is as searchable as anything written down.

None of them needs a sign-in screen: each connects with a bot token or an app credential created once in that platform's own settings, and each only ever reads — nothing is posted back. A channel or space becomes documents on the schedule you set, threads and replies included, and history already brought in stays searchable even after it ages out of the source's own lookback window. Who can then ask about it varies by platform: some mirror a private channel's own membership automatically, others rely entirely on the access groups chosen when the source was set up — each source's own Access section says which.

There's rarely a real choice to make here — connect whichever of these your organisation actually uses, and more than one if it uses several. One distinction worth knowing before you start: a source in this category only reads a platform's past conversation in. Making the assistant answer questions live inside Slack, Teams, Google Chat, Mattermost or Discord is a separate feature, Chat channels — the two run independently, or alongside each other, without conflict.

The connectors

• SlackConnect Slack to make channel history searchable — each channel becomes monthly chat-log documents with who said what and when, threads included, so decisions made in chat are as searchable as any…
• Teams channelsBring Microsoft Teams channel messages in as chat-log documents — the sync walks the connected account's teams and turns every channel into monthly documents, replies indented under their post. This…
• Google ChatBring Google Chat spaces in as chat-log documents — every named space a chosen workspace account is in becomes monthly documents, threads grouped under their opening message. This is a document…
• MattermostConnect Mattermost — on your own server — to make channel history searchable: each channel becomes monthly chat-log documents, thread replies indented under their root post. This is a document…
• DiscordBring Discord server channels in as chat-log documents — each text channel becomes monthly documents of who said what, when. This is a document source, separate from the Chat channels feature that…
• Webex (spaces)Bring Webex spaces in as chat-log documents — each group space becomes monthly documents of who said what, when, thread replies under their parent. Direct messages are never read. Read-only.

Shared files never come in as files

Every source in this category leaves attachments where they are — a message that carries a file becomes text noting a file was shared, never the file's own content. Most name it; Webex, whose API only reveals a filename on download, counts it instead. Share the document itself through a connector built for it — Drive, SharePoint, a folder — if it needs to be searchable on its own.

Last updated 20 Sep 2026