Slack
The Slack connector lets an agent read what happened in your workspace and, with your approval, post to it.
When to use it
Section titled “When to use it”Slack is where decisions get made and then lost. An agent that can search it turns “someone posted the deploy checklist a month ago” into a working answer, and can summarize a channel you were away from.
If you want the opposite direction — asking an agent something from inside Slack — see Channels.
Connect it
Section titled “Connect it”-
Open Connectors in Agent Builder and choose Slack.
-
Sign in and approve the workspace. Access is per workspace.
-
Invite the app to the channels it should read. This is the step people miss — see below.
-
Bind the connection to the agent.
What an agent can do
Section titled “What an agent can do”| Operation | Gated |
|---|---|
| List channels | No |
| Read a channel’s recent history | No |
| Search the workspace | No |
| Read a thread’s replies | No |
| Post a message | Yes |
Search uses Slack’s own syntax — from:@user, in:#channel, quoted phrases — and is the right starting point when you do not know which channel something is in.
Posting
Section titled “Posting”Posting is gated, like every outbound action. You see the channel and the exact text before it goes out, and approving sends precisely that.
In an unattended run — a routine, for example — a post is refused rather than held. A scheduled Slack digest should write an artifact and notify you, or you should post it yourself once you have read it.
Limits
Section titled “Limits”- One Slack workspace per connection.
- Reading history requires the app to be in the channel. Private channels it has not been invited to are invisible.
- Direct messages are not covered.
- Posting always requires approval, including replies in a thread.
- The agent posts as the Endue app, not as you.