Messaging

AI agents that use Slack

UtilitySpaces gives an AI agent scoped access to Slack through its own encrypted connection, not your password. The agent can call 5 named Slack tools, and the one that writes waits for a person's approval unless an admin has set the connection to run without asking. Every call is written to a hash-chained audit log with its arguments and its result.

What an agent can do in Slack

Read channels, history, and members of a Slack workspace and post messages as the bot. An agent calls these by name, and matching is exact.

Every tool a Slack connection exposes, and whether it writes, which waits for approval by default
Tool	What it does	Waits for approval by default
Test auth	Check the bot token and identify the workspace and bot user.	No — read only
List conversations	List channels the bot can see.	No — read only
Get conversation history	Read recent messages from a channel the bot is in.	No — read only
List users	List members of the workspace.	No — read only
Post message	Post a message to a channel as the bot.	Yes — it writes

4 read tools, 1 write tool. Generated from the connector catalogue the product runs on, so it cannot list a tool that does not exist.

What teams hand an agent in Slack

Teams hand an agent the reading side of Slack first: catching up on a channel with Get conversation history, finding who is in the workspace, and summarising threads into the inbox. Post message is the one write, and it stops for approval unless an admin has set this connection to run without asking.

Summarise what happened in a busy channel overnight by reading its recent history and writing the digest into the UtilitySpaces inbox.
Find the right person for a question by listing workspace users and matching names or titles mentioned in a thread.
Post a status update to a channel when a scheduled flow finishes, such as a daily report or an incident note (once someone approves it)

Before you let it write, or keep out: Do not set Post message to run without asking for a bot sitting in channels with clients or the whole company in it: the bot can only read channels it has been invited to, but a posted message is visible to everyone there at once.

What waits for a person

Reads run on their own. These do not — each one waits in Approvals for an owner or admin unless an admin has set this connection to run writes without asking, and every call toSlack, approved, rejected or unattended, is logged.

Post message POST

What connecting Slack takes

Slack uses an API key you create in Slack and paste in once. A workspace admin sets the connection up; the fields are:

Bot User OAuth Token

Credentials are encrypted and bound to your workspace, never read back, and every outbound call passes one guarded fetch — the connector security posture sets out exactly how, and the security page covers the platform around it.

Where Slack fits

Give an agent Slack work by writing a message in the inbox, or put its tools in a scheduled flow. What the run cost is on the cost breakdown.

Other messaging integrations: Chatwoot, Discord, Gmail. Or see every application agents can connect to.

See it doing your actual work

Open a demo workspace, connect one app, and give an agent a real job. No card, no sales call.

Try the demo See pricing

We reply to every message within one business day.