ConnectorsSlack

Connect Slack

Connect Slack, invite the Gurusup app to channels, and understand what Gurusup reads, what it does not, and how to stop it.

Admins only. Gurusup learns only from the channels you choose, and it also writes to Slack in two ways: it posts a notice in each channel it joins, and it messages colleagues it has questions for.

At a glance

TopicDetails
Who can connectAdmins
What you needA Slack account that can approve the app for your workspace
What Gurusup readsNew messages and the contents of shared files in the channels the app joins
How changes arriveAs messages are posted, edited or deleted
Past contentNone. Gurusup reads from the app's notice on. Earlier messages can't be imported, and editing one later doesn't bring it in. No Import history.
Knowledge accessDefault access, Restricted or Private, chosen when you connect. See Who can read it.

Before you start

  • Tell your team: the app posts a notice in every channel it joins.
  • Decide who should read these channels in Gurusup. Restricting later only covers what comes next.
  • The same Slack workspace can be connected to several Gurusup organizations, each approving it on its own. See The same account in several organizations.

Connect Slack

Open the Slack connector

In the sidebar, open Sources, then Catalog, find Slack (use Search sources if you need to) and click Connect on its row. Its page opens. Next to Organization accounts, click Connect for the organization. The dialog Connect Slack for the organization opens.

Choose who reads it

Optional. In the dialog, under Who can read it, choose Default access, Restricted or Private from Access mode. Every channel the app joins later starts with this access.

Connect and approve access

In the dialog, click Connect and approve access for your Slack workspace. Slack sends you back to the page you started from, and the dialog Finish setting up Slack opens.

Invite the app to your channels

The dialog shows the steps: Open a channel, Invite Brain with a button that copies the command, and Brain joins, with a sample notice. It adds "Brain only reads channels it has been invited to." Click Done and a message says "Slack connected." If you close the dialog without Done, you see no message, but Slack is connected.

In each channel you want Gurusup to learn from, run:

/invite @GuruSup Brain

You can also click the channel name in the channel header and add the app from the Agents & apps tab. You can invite it to more channels at any time.

Look for the notice

The app posts a notice in the channel. Gurusup reads from that notice on. See The notice in each channel.

The app cannot join a private channel by itself. Someone already in the channel has to run /invite @GuruSup Brain there.

In setup, Slack is a card under Live sources. Click its plug button (Connect Slack). The dialog Connect Slack for the organization asks Who can read it; choose and click Connect, approve, then invite the app as above. A Slack with no messages yet does not hold up Continue. Slack content that Gurusup fails to prepare three times is dropped. Channels connected in setup use the access you chose in that dialog, which starts on Default access, and so does every channel the app joins later.

What Slack asks you to approve

Reading messages and files in channels the app is in, reading basic information about channels and people including their email addresses, and sending messages. Sending lets the app post its notice and message a colleague directly. Gurusup also reads direct messages sent to the app itself, which is how colleagues answer its questions. See Contacts.

The notice in each channel

The first time the app is in a channel, it posts this notice, in Spanish for every organization:

Gurusup, añadido por (your Slack workspace name), conservará los mensajes y archivos, incluido su contenido, publicados después de este aviso para incorporarlos a la memoria corporativa de esa organización.

In English: Gurusup, added by your Slack workspace, will keep the messages and files, including their content, posted after this notice and add them to that organization's memory.

Channels where the app posted the notice before this wording changed show the older text, which says "metadatos de archivos" (file details). Gurusup reads the contents of files there too, from the same notice on.

  • No notice, no reading. If the app cannot join the channel or Slack does not let it post, the channel stays unread.
  • Messages before the notice are never read. Earlier messages can't be imported, and editing one later doesn't bring it in.
  • Slack Connect. If another Slack workspace joins a channel the app is in, the app posts the notice again, and Gurusup reads from the new notice on.

What Gurusup reads

Gurusup readsGurusup does not read
New messages in public channels, private channels and group messages the app has joined, after the noticeMessages posted before the notice
Replies inside threads. Replies also sent to the channel are not read.Channels the app has not joined
Edits and deletions of messages it already readDirect messages between people
Messages from other apps and botsSystem messages, such as joins, leaves or a changed topic or name
Messages that only contain a fileThe app's own messages, including its notice
The contents of files shared after the notice. See Files shared in channels.Files shared before the notice, Slack canvases, lists and posts, and files hosted outside Slack

Each channel is its own source, named Slack #channel-name. A group message is named Slack followed by the group's name, without the hash. Inviting the app to a channel adds it, and removing the app closes it. A channel in the list does not prove Gurusup is reading: the notice does.

Files shared in channels

Gurusup reads the contents of files shared in a channel after the app joined it: PDF, Word, PowerPoint, Excel, Markdown, text, CSV and HTML files, and ZIP archives of them. Channels the app already joined get this without any action from you.

  • Each file becomes its own document, linked to the conversation it was shared in. A reply or an edit to the message does not read the file again or count it twice.
  • Deleting the file, deleting its message, or removing the file from the message withdraws it from your memory.
  • Gurusup reads files up to 64 MiB, and keeps the first 1 MiB of text of each file. Files that Gurusup cannot read, or that Slack does not let it open, are skipped. The message itself is still read.
  • If reading a file fails, Gurusup tries again up to five times, then gives up on that file. A failing file never stops its message from coming in.

One row per Slack workspace

Sources shows one row per Slack workspace, named Slack · workspace name, even with a single channel.

On the rowWhat it means
ContributionThe sum of its channels
StatusThe worst status among its channels
  • A Slack Connect channel counts under the workspace you connected, not the one that hosts it.
  • Channels that joined before Gurusup recorded their workspace keep their own row.

Click the row to open the Slack page. Under Organization accounts you manage the workspace connection. The page does not list the channels one by one, and a channel has no page of its own: its documents and memories count on the workspace row.

How changes arrive

Gurusup reads each new message, edit and deletion in a joined channel as it happens. You do nothing after inviting the app.

Import past work

Slack has no way to bring in earlier history. If a channel matters, invite the app early.

Who can read it

Each channel is a source, and it starts with the access you chose when you connected Slack.

Knowledge accessWho reads it in Brain
Default accessEveryone, according to what they are already allowed to see: admins every category, members and agent accounts the categories an admin granted them.
RestrictedOnly the people you pick. Administrators are not included unless you pick them.
PrivateOnly you. Administrators are not included.

You cannot change one channel's access afterwards from Sources, so decide before you connect. Gurusup does not copy who is in a channel: a private Slack channel is read in Gurusup by whoever its access allows. Choose Default access, Restricted or Private when you connect. See Restrict a source to specific people.

Check that it worked

Find the notice

In the channel, find the notice from GuruSup Brain, then post a short test message.

Find the channel

On Sources, open Slack · your-workspace-name. Its Contribution and Last updated change once Gurusup has read the message. Open Ingest to follow the message itself.

Follow the message

Open Ingest and pick that source in the filter. The message moves from Queued to Learning to Learned. See Follow ingestion.

Reconnect

If the app is uninstalled in Slack, or Slack revokes its access, Gurusup closes every channel source and marks the connection as revoked. The account's row still has Reconnect, which sends you through the approval again. After you approve, invite the app to your channels again. What Gurusup learned stays.

A workspace with no channel yet has no row in Sources. Open Slack from Catalog: its page lists the workspace under Organization accounts, where you can reconnect or disconnect it. Click Connect for the organization again to connect another Slack workspace: each gets its own row.

Disconnect

Disconnect, under Danger zone on the Slack page (or in the menu on the account's row), removes the whole Slack connection with every channel, deletes the credentials Gurusup stored for your organization and closes questions Gurusup was waiting on through that workspace. The app stays installed in Slack until someone uninstalls it there, which also cuts off every other organization that connected the workspace. The dialog "Disconnect [name]?" says "Gurusup stops reading from Slack · [workspace name]. What it already learned stays." Click Disconnect to confirm, or Cancel. What Gurusup learned stays: see Remove, disconnect and what stays.

To stop a single channel, take the app out of that channel in Slack. Disconnect stops all of them.

Remove source only shows on a channel with its own row and no connection attached, because Gurusup never recorded its workspace. Open that row, then use Remove source under Danger zone and confirm.

If it does not work

Go through this list in order.

CheckWhat to do
Is the notice in the channel?If not, Gurusup is not reading. Check that the app is in the channel (click the channel name, then Agents & apps); in a private channel someone in it has to invite it. If it is in with no notice, remove it and invite it again.
Is the channel counted on the workspace row?Open Ingest and filter by the Slack source. If it is missing, refresh the page and wait a moment.
Did you post after the notice?Earlier messages are never read.
Is it something Gurusup reads?Direct messages, system messages and the app's own messages are not. Files shared before the notice, canvases, lists and posts are not either.
Was the app removed from the channel, or the app uninstalled?Invite it again, or see Reconnect.
Is the item Paused on Ingest, or ingestion paused?See Follow ingestion and When ingestion is paused or Demo Mode is on.
Several workspaces connected?Each workspace has its own row on Sources, and each channel counts under the workspace it was invited from.
MessageWhat to do
"The Slack connection changed while you were signing in. Refresh the page and connect again."The connection was changed while you approved. Refresh the page, then connect again.
"Organization-wide Slack Enterprise installations are not supported."Install the app in a single workspace, not across an Enterprise Grid.
"OAuth state expired. Start the connection again."The approval link lasts 15 minutes. Start again from the Slack page.
"Access to Slack wasn't granted, so nothing was connected. Start again when you're ready."Start again and approve.

Still stuck? See Connector troubleshooting, or contact support with the channel source name, when you posted and any message Gurusup showed.