Connect Slack to AI: answers from your channels without scrolling back
Slack can be connected to AI. The assistant finds messages back in the channels the connector is allowed to reach, knows which channels and colleagues exist, and can post a message in a channel when you ask. It never posts on its own initiative: a message in Slack is on your colleagues' screens straight away.
What the assistant does for you inside Slack
Finding back what was said
You ask the question in plain language and the assistant finds the messages that deal with it. It comes back with what was said, which channel it was in and who wrote it.
Narrowing the search
A search can be limited to one channel, to the messages of one colleague or to a period. A question about last week in the logistics channel therefore really does stay inside last week and inside that channel.
Knowing which channels exist
The assistant knows the channels the connector has access to. Name a channel and it knows which one you mean, even when the name has changed along the way.
Pulling in the right colleague
It knows who is in the workspace and can genuinely mention someone in a message, so that person gets a notification. That saves a separate nudge to wake somebody up.
Posting a message on request
Ask for it and the assistant puts a message in the channel you name, or sends it to one person. It says up front what it wants to post and where, and a reply stays inside the existing thread.
Where a team notices it right away
Customer service
- Situation
- A customer calls back about a complaint discussed last month in a busy channel, and the colleague who handled it is off.
- What the agent does
- The assistant searches the customer name inside that channel and that period and summarises the thread, including who promised what.
- Result
- The caller gets an answer on the spot instead of a promise that somebody will look into it.
Project team
- Situation
- At the start of a project the lead wants to know which commitments were made in the run-up, spread over three channels.
- What the agent does
- The assistant searches each channel on the project name, reads the messages around it and lists the commitments with where they came from.
- Result
- A kickoff document that matches what was actually said, without anyone reading back all evening.
HR and recruitment
- Situation
- A recruiter wants to know who in the organisation has worked with a particular technology, but does not know the names.
- What the agent does
- The assistant searches the term in the channels it is allowed to reach and names the colleagues who wrote about it.
- Result
- A short list of people you can approach directly, with the messages it is based on.
Operations
- Situation
- An outage has been fixed and the channel needs to know, but the person who fixed it is still in the system and half forgets.
- What the agent does
- On request the assistant posts a short closing note in the right channel, as a reply inside the existing thread about the outage.
- Result
- Everyone who was following sees that it is done, and the channel stays readable because it stays with the thread.
Management
- Situation
- A decision was taken somewhere in a channel, but nobody remembers when or on what grounds.
- What the agent does
- The assistant finds the discussion back, puts the arguments in order and names the date the decision was made.
- Result
- A recap built on the messages themselves, usable in a report or an evaluation.
Connecting your Slack workspace
-
1
Connecting from the platform
You grant IntraGPT permission from your own Slack environment. That permission is yours, so an administrator can take it away just as easily.
-
2
Deciding what takes part
You choose which channels are in reach and whether the assistant may only read along or also post. Read only is a perfectly good choice and changes nothing else about the way it works.
-
3
What the assistant gets to see
It gets the messages that belong to the question, with the channel and the sender. It does not reach beyond the agreed channels, even when somebody asks it to.
-
4
Reading back what happened
Every time the assistant consults Slack or puts something in it, that lands in the log. For a posted message you can therefore trace where it went and at whose request it was sent.
Reading along in channels is not a small thing
Slack holds throwaway remarks, sensitive conversations and customer names side by side. The connector is bounded to what you point at, and everything the assistant posts can be traced.
Where the data lives: Nederland of de EU
Access stays yours
The permission belongs to your own Slack environment and can be withdrawn in one move. IntraGPT holds no employee passwords.
Only the agreed channels
What falls outside the reach does not exist for the assistant. A channel the connector may not touch never turns up in an answer, even if somebody explicitly asks for it.
Posting is never silent
Sending a message is a visible act. The assistant announces where it will put it, does it on request, and the act then sits in the log.
The model on a server of our own
The conversations the assistant reads out of Slack are processed on our own server in the Netherlands. They do not go to an American model provider and are never used for training.
Questions about the Slack connector
Can I connect Slack to ChatGPT?
ChatGPT has no managed connection to your workspace, and almost nobody wants to move internal conversations into a public chatbot. With IntraGPT you chat the same way, but with a connector that only reaches the agreed channels and whose every action is recorded. The model runs on a server of our own.
Does IntraGPT work with Slack?
Yes. Slack is a working integration already in use at customers. The assistant finds messages back, knows which channels and colleagues exist and can post something on request. What exactly falls inside the reach is agreed during setup.
Does the assistant see all our channels?
No, only the ones you point at. A channel that is not included stays out of the search results and therefore never reaches an answer. To keep a sensitive channel out you do not have to configure anything special: it simply is not part of the reach.
Can the assistant start posting by itself?
No. Posting only happens on an explicit request, and it first shows what it wants to post and in which channel. If you do not want that option at all, we set the connector up to read along and nothing can be written.
Can we withdraw the connection again?
Yes, and an administrator can do it without us. The permission belongs to your Slack environment; the moment it is gone the assistant sees nothing. What happened up to that point stays readable in the log.
Does it keep working when somebody leaves?
Yes. The connector hangs off the organisation, not off one employee's personal account. When somebody leaves, nothing has to be set up again. It is worth checking at that moment who is allowed to manage the connector.
What does a Slack connector cost?
Connecting sits inside the project we run together. What drives the work is whether the assistant only reads along or also posts, how many channels take part and which roles may use it. In a first conversation we make that concrete for your situation.
How long does setup take?
The connector itself is up quickly. The lead time almost always sits in the internal agreement: who grants permission, which channels take part and whether the assistant may post. Once those choices are made, switching it on takes minutes.