---
sidebar_position: 7
title: Slack Integration
---

# Slack Integration

Connect a Slack workspace so your agents can post messages, reply in threads, react, read history, and resolve users. Slack uses **OAuth (V2)** — one click, no token pasting.

## How It Works

You authorize the Zibby Slack app against your workspace. Slack returns a bot token (`xoxb-...`) that Zibby stores encrypted, along with the team ID/name. The `slack` skill then exposes Slack's API to any node that declares it.

## Connect Slack

1. In the Zibby dashboard, open a project → **Project Settings**, expand the **Chat integrations** card, and click **Connect** on the **Slack** row
2. You're redirected to Slack to authorize the Zibby app and pick a workspace
3. Approve the requested scopes
4. You're redirected back to Project Settings — the row shows the connected team name

## What Agents Can Do

Nodes that attach the [`slack` skill](../skills/slack.md) get tools to list channels, post and reply, react, read channel/thread history, and look up users (by email, search, usergroups). This powers routing in recipes like [Sentry triage](../recipes/sentry-triage.md), where the agent resolves an author email to a Slack user and DMs them.

## Reference (SDK / CLI)

When running agents directly, the connector reads the bot token and team ID from the environment.

## Troubleshooting

**Message not delivered** — the bot must be invited to private channels before it can post there.

**User lookup returns nothing** — `slack_get_users` excludes bots and deactivated accounts; confirm the user is active in the workspace.