---
title: "Slack"
description: "Scoped Slack credentials for AI agents"
url: "https://gazebohq.com/services/slack"
---

Slack is where notifications land, approvals get routed, and agent outputs surface to humans. AI agents that post updates, send alerts, or manage workflows need Slack API access. Gazebo scopes that access per agent — so a notification agent can post to its channel without holding a token that touches your entire workspace.

## Why should AI agents use scoped Slack credentials?

A shared Slack bot token across agents means every agent can read any channel it has access to, post as the same bot identity, and — with the wrong scopes — access direct messages or workspace settings. Gazebo gives each agent its own named identity and enforces per-agent scope on every Slack credential request.

## How it works

1. Connect your Slack workspace to Gazebo using a bot token with the minimum scopes your agents require.
2. Create an access profile for each agent — scoped to the channels and operations it actually uses.
3. Each agent calls get_credential via MCP. Gazebo checks the policy and returns the Slack token.
4. Every access is logged: which agent, which timestamp, approved or denied.
5. Revoke future Slack token retrieval per agent. Revoke or rotate the provider token if a retrieved value may have leaked.

## Use cases

**Per-channel notification agents:** Give each notification agent access to post only to its designated channel — not your entire workspace. A deployment alert agent posts to #deployments; a billing alert agent posts to #billing. Neither can read the other's channel.

**Approval workflows with a full audit trail:** Every time an agent retrieves Slack credentials to post an approval request or update a thread, Gazebo logs it. Know exactly which agent sent which message and when.

**Revoke a noisy agent without touching others:** If an agent starts flooding a channel or posting to the wrong workspace, revoke its Slack access in one click. Every other agent keeps posting normally.