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

# Slack Integration: Automate Your Team Notifications

> Connect Slack to Atmet to trigger workflows on channel messages and send automated notifications, DMs, and status updates to your team.

Slack is where your team's conversations happen — and the Atmet Slack integration makes it a two-way automation hub. You can start workflows the moment a message lands in a specific channel, or when a reaction is added to a message, and you can push Atmet's output back into Slack as messages or direct messages. Use it to deliver real-time notifications when a workflow completes, surface approval requests directly in the right channel, broadcast status updates from connected systems, or build lightweight ChatOps workflows that your whole team can interact with.

## Prerequisites

Before connecting Slack, make sure you have:

* A Slack account and access to the Slack workspace you want to automate
* Permission to install apps in your Slack workspace (Workspace Owner or Admin, or an administrator who can approve app installs)
* The name or ID of the channels you plan to use in your workflows

***

## Connecting Slack

<Steps>
  <Step title="Open Integrations">
    In the Atmet sidebar, navigate to **Integrations** and find **Slack** in the list.
  </Step>

  <Step title="Click Connect">
    Click the **Connect** button. You'll be redirected to Slack's OAuth authorization page.
  </Step>

  <Step title="Choose your workspace">
    In the top-right corner of the Slack authorization page, confirm you're authorizing the correct workspace. Switch workspaces if needed.
  </Step>

  <Step title="Authorize Atmet">
    Review the requested Slack permissions and click **Allow**. Atmet requests the scopes needed to read channel messages (for triggers) and post messages (for actions).
  </Step>

  <Step title="Confirm the connection">
    You'll be redirected back to Atmet. A green **Connected** badge confirms Slack is linked and ready to use.
  </Step>
</Steps>

<Note>
  You can connect multiple Slack workspaces to the same Atmet account. Repeat the connection flow for each workspace. Each connection is independent and can be assigned to different workflows.
</Note>

<Warning>
  If your Slack workspace requires admin approval for new app installs, the connection will remain in a **Pending** state until a workspace owner approves the Atmet app in **Slack → Administration → Manage Apps**.
</Warning>

***

## Triggers

<Accordion title="New message in channel">
  Fires whenever a new message is posted to a specific Slack channel.

  | Parameter | Description                                                                               |
  | --------- | ----------------------------------------------------------------------------------------- |
  | `Channel` | The channel to monitor. You can specify by channel name (e.g., `#support`) or channel ID. |

  **Use this trigger when** you want to react to team activity — for example, routing a message posted in `#support` into a ticketing system, or capturing approvals posted in `#approvals`.

  <Tip>
    Make sure the Atmet app is a member of the channel you want to monitor. Add it by typing `/invite @atmet` (or the name of your Atmet bot) in the channel.
  </Tip>
</Accordion>

<Accordion title="Reaction added">
  Fires whenever a reaction (emoji) is added to a message in a channel where the Atmet app is present.

  **Use this trigger when** you want to kick off a workflow based on team signals — for example, reacting with ✅ on a support message to create a ticket, or using 🚀 to trigger a deployment notification.
</Accordion>

***

## Actions

<Accordion title="Sending messages">
  | Action                   | What it does                                                                                                                                            |
  | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
  | **Send channel message** | Posts a message to any public or private channel the connected Slack app is a member of. Supports plain text and Slack's Block Kit rich message format. |
  | **Send direct message**  | Sends a direct message to a specific Slack user by their user ID.                                                                                       |

  Both actions support dynamic content — inject workflow variables, AI-generated summaries, or data from upstream steps directly into the message body.
</Accordion>

***

## Workflow ideas

<CardGroup cols={2}>
  <Card title="Approval request bot" icon="check-double">
    Trigger from an upstream event (a new deal in HubSpot, a form submission). Send a formatted Slack message to the `#approvals` channel asking for a yes/no decision, then route the workflow based on the response.
  </Card>

  <Card title="Support ticket from Slack" icon="headset">
    Trigger on new messages in `#support`. Use an AI step to classify urgency, create a Jira or Notion ticket, then send a DM to the submitter with the ticket link.
  </Card>

  <Card title="Daily standup digest" icon="calendar-day">
    Run on a schedule each morning. Query your project management tool for yesterday's completed tasks, generate a digest with AI, and post it to your team's `#standup` channel automatically.
  </Card>

  <Card title="Deployment notification" icon="rocket">
    Trigger on a GitHub PR merge. Format a release summary and post it to `#deployments` with the commit list, author, and a link to the diff — keeping everyone informed without manual announcements.
  </Card>
</CardGroup>

***

## Limitations and notes

<Info>
  Atmet's Slack integration uses the Slack Web API. For the **New message** trigger to work, the Atmet app must be a member of the channel you want to monitor. Add it by typing `/invite @atmet` (or the name of your Atmet bot) in the channel.
</Info>

<Note>
  The **Send channel message** action supports Block Kit formatting for rich layouts — buttons, sections, images, and dividers. Compose Block Kit JSON in your workflow's message payload to build visually clear notifications that stand out in busy channels.
</Note>

<Accordion title="What Slack permissions does Atmet request?">
  Atmet requests the following Slack OAuth scopes:

  | Scope              | Purpose                                                  |
  | ------------------ | -------------------------------------------------------- |
  | `channels:history` | Read message history in channels the app is a member of. |
  | `chat:write`       | Post messages to channels.                               |
  | `users:read`       | Resolve user IDs to names for DMs.                       |

  If your workflow requires private channel access, a Workspace Admin must grant the additional `groups:history` scope.
</Accordion>