> ## Documentation Index
> Fetch the complete documentation index at: https://docs.monk.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Slack Integration

> Manage infrastructure from Slack — respond to questions, approve changes, and get alerts without opening your coding agent

## What It Does

Connect Monk to your Slack workspace and it sends you questions, configuration forms, and task completion summaries directly in Slack. You respond right there — no need to open your coding agent.

Monk asks in both the chat and Slack at the same time. Whichever one you respond on first wins — the other is cancelled automatically. When a task finishes, you get a summary in Slack with suggested next steps you can trigger without switching back to your agent.

There are two Slack features:

* **Remote Control** — two-way interactive prompts for answering questions, filling out forms, approving changes, and following up on completed tasks from Slack
* **Watcher Alerts** — one-way monitoring notifications with AI-powered diagnosis and a Fix with Monk button

Available on Pro and Team plans.

## Connect Slack

<Steps>
  <Step title="Ask Monk to connect Slack">
    In your coding agent:

    ```
    ask Monk to connect Slack
    ```
  </Step>

  <Step title="Authorize in Slack">
    A browser window opens where you authorize the Monk app in your Slack workspace. You need permission to install apps in the workspace.
  </Step>

  <Step title="Pick a channel">
    Back in the chat, Monk shows a list of your Slack channels and DMs. Pick where you want to receive messages. You can also send to a DM with yourself for a personal notification channel.
  </Step>
</Steps>

That's it. Monk confirms the connected channel, and you can check the connection state at any time by asking Monk for Slack status.

## Remote Control

Once Slack is connected, Monk sends interactive messages to your Slack channel whenever it needs your input — during deployments, configuration changes, scaling, credential requests, and more.

### What you can do from Slack

**Answer questions** — When Monk needs a decision ("Continue deployment to production?", "Which region?"), you get a Slack message with buttons or a text input. Tap a button or type your answer.

**Fill out forms** — Configuration forms (cluster settings, watcher thresholds, service parameters) appear as interactive Slack forms. Fill them out and submit without switching back to your agent.

**Approve file changes** — When Monk's code editor wants to modify files, you get an approval request in Slack listing the affected files and operations. Approve or reject with a reason.

**Provide credentials** — When Monk needs cloud credentials, it notifies you in Slack. The actual credential entry happens securely on your machine, but the notification means you know to check in when you're ready.

**See task results** — When Monk finishes a build, deployment, cluster operation, or other long-running task, you get a summary of what was done along with suggested next steps as clickable buttons. Tap a button to trigger the next action directly from Slack.

### Task completion notifications

When Monk finishes a task that involved a build, deployment, cluster operation, CI/CD setup, or other significant work, it sends a completion summary to Slack. The notification includes Monk's summary of what was accomplished and, when available, action buttons for common follow-up steps like opening the app, checking logs, or deploying.

Clicking an action button sends that prompt to Monk as a new message, and the response comes back to Slack — so you can go through an entire build-deploy-verify workflow from Slack without being at your computer. Each conversation's messages are grouped into a Slack thread, with the chat title shown at the top for easy identification.

### How it works

Monk asks on all available interfaces simultaneously — the chat and Slack. The first response wins. If you answer in Slack, the chat prompt is dismissed. If you answer in the chat, the Slack message is updated to show it was handled.

This means you can start a long-running operation, close your laptop, and handle the next decision from your phone when the Slack notification arrives.

### Example flow

1. You tell Monk to deploy your project and close your laptop
2. Monk provisions infrastructure, builds containers, and hits a decision point — "The deployment needs a database. Set up PostgreSQL?"
3. A Slack message arrives on your phone with **Yes** and **No** buttons
4. You tap **Yes**
5. Monk finishes deploying and sends a summary to Slack: "Deployed to production. All 3 workloads healthy." with buttons like **Open the app** and **Check logs**
6. You tap **Check logs** and the log output appears in Slack

## Watcher Alerts

[Watcher](/features/watcher) monitors your cluster 24/7 and sends one-way alert notifications to Slack when something goes wrong — crashes, CPU spikes, disk pressure, health check failures.

Watcher alerts use a separate Slack webhook (not the relay connection). During [Watcher setup](/prompting/watcher-setup), Monk offers to configure Slack alerts. If you accept, it opens a quick OAuth flow where you authorize an Incoming Webhook and pick a channel. Monk handles the entire setup — no manual webhook URLs needed.

Each alert includes:

* AI-powered diagnosis explaining what happened and why
* Severity level and affected service
* A **Fix with Monk** button that opens your coding agent with full context

See [Watcher](/features/watcher) for configuration options and alert format details.

## Managing the Connection

### Change channel

Ask Monk to change the Slack channel and pick a different one from the list.

### Disconnect

Ask Monk to disconnect Slack. This clears the connection on your side but does not uninstall the Monk app from your Slack workspace.

### Reconnect

If the connection drops (network issues, restarts), Monk reconnects automatically. You can also ask Monk to reconnect Slack.

### Connection status

Ask Monk for Slack status at any time to see whether the connection is active.

## FAQ

<Accordion title="Do I need Slack connected for Monk to work?">
  No. Slack is optional. Without it, Monk asks all questions in the chat. Slack just gives you a second interface so you can respond when you're away from your computer.
</Accordion>

<Accordion title="Can multiple people respond to the same question?">
  The first response wins. If someone answers in Slack and someone else answers in the chat, whichever comes first is used. The other is cancelled.
</Accordion>

<Accordion title="Is the Watcher webhook the same as the remote control connection?">
  No. Remote control uses a persistent WebSocket connection through the Monk relay service. Watcher alerts use a standard Slack Incoming Webhook. They're configured separately and can go to different channels.
</Accordion>

<Accordion title="What Slack permissions does the Monk app need?">
  The app needs permission to post messages and read channel lists in your workspace. It uses Slack's Socket Mode — no public URLs or firewall changes needed on your side.
</Accordion>

<CardGroup cols={2}>
  <Card title="Watcher" icon="radar" href="/features/watcher">
    24/7 cluster monitoring with AI-powered Slack alerts
  </Card>

  <Card title="Watcher setup guide" icon="bell" href="/prompting/watcher-setup">
    Step-by-step setup including Slack alert configuration
  </Card>
</CardGroup>