Slack
Read workspace channels and users, inspect recent messages, post messages, and add reactions
Connect Slack when a project needs bounded access to workspace conversations. Swarmz supports shared project and published app-user connections.
Available operations
| Operation | What it does | Limit per minute |
|---|---|---|
list_channels | Lists visible public channels and joined private channels | 30 |
list_users | Lists users with safe profile fields | 30 |
list_messages | Reads recent messages from one channel | 60 |
post_message | Posts one message, optionally in a thread | 20 |
add_reaction | Adds one named reaction to a message | 30 |
The connection cannot read a private channel unless the authorized Slack identity can see it. Posting and reactions require Slack write permission.
Connect Slack
Ask the AI for the Slack feature and name who owns the account. For a team notification, say: “Post new trial signups to our Slack workspace.” For user-owned workspaces, say: “Let each signed-in user connect Slack and list their channels.”
For a shared connection, choose an existing Slack connection or select Connect new in the chat card, approve the requested access in Slack, then select Continue. For published app users, enter the app's HTTPS origin and select Configure. See Connector connection modes.
Verify Slack
- List channels and confirm one known channel name.
- Read messages from a test channel.
- Post a message containing a unique test marker, then confirm it in Slack.
- Add a reaction to that message and confirm the reaction.
- Remove the test message if your Slack role permits it.
If a private channel is missing, add or invite the authorized identity to the channel, then list channels again. If posting fails after reads succeed, reconnect and approve Slack write access.
Provider credentials stay encrypted in Swarmz. Generated code calls the connector gateway from a server route; it must not call Slack from browser code.