> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/integrations/communication/slack/setup-guide.md).

# Slack setup guide

Mobly's Slack integration sends event-triggered notifications to channels in your Slack workspace. This article covers connecting Slack to Mobly. For configuring which notifications fire and what they include, see the [Notifications](/help-center/notifications/notifications.md) section.

## What you can do

* **Connect Mobly to your Slack workspace** via OAuth
* **Route notifications to specific channels** — pick which channel each notification type lands in
* **Customize what each notification includes** in Mobly's Notifications configuration

## Before you connect

You'll need:

* A **Slack workspace admin** (to authorize the Mobly app)
* The **channels** Mobly should be allowed to post to. The Mobly app needs to be added to each channel where you want notifications

## Connect Slack to Mobly

1. In Mobly, go to **Integrations** in the left nav
2. Find **Slack** under the **Communication** category and click its card
3. On the **Connect** tab, click **Connect**
4. Slack's OAuth flow opens — pick the workspace you want to connect (if you're in multiple), then approve the permissions Mobly requests
5. The window closes and you're back in Mobly. The Slack card now shows **Connected** with a globe icon

## Add the Mobly app to channels

After connecting, the Mobly app needs to be added to any Slack channel where you want notifications to appear:

1. In Slack, open the channel you want notifications in
2. Click the channel name at the top to open channel settings
3. Go to the **Integrations** tab
4. Click **Add an app** and search for **Mobly**
5. Add it

Repeat for any other channels.

## Configure which notifications fire

Connecting Slack and adding the app to channels is the integration setup. The next step — deciding which notifications fire and what they include — lives in the broader Notifications configuration.

See the [Notifications](/help-center/notifications/notifications.md) section for that.

## Pause, disconnect, or reconnect

The Connect tab has two buttons next to the Slack status:

* **Disable** — pauses notifications but keeps the connection. Notifications stop firing; mappings/channel selections are preserved.
* **Disconnect** — fully removes the Slack connection. The Mobly app stays in Slack (you'd need to remove it from each channel separately if you want a clean break).

To re-authenticate, click **Connect** again on the Connect tab.

## Common gotchas

* **The Mobly app isn't in the channel** — notifications fail silently if the app wasn't added. Add it via the channel's Integrations tab.
* **Workspace admin revoked the app** — if a workspace admin removes the Mobly app from the workspace, all notifications stop. Reconnect from Mobly and re-add the app to each channel.
* **Private channels** — work the same way, but require manual addition of the Mobly app since Slack doesn't auto-suggest the app in private channels.

## Related articles

* [Communication integrations](/help-center/integrations/communication.md)
* [Notifications](/help-center/notifications/notifications.md) — what notifications fire and what they include


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.getmobly.com/help-center/integrations/communication/slack/setup-guide.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.