> For the complete documentation index, see [llms.txt](https://argos-ci.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://argos-ci.com/docs/learn/integrations/slack-integration.md).

# Slack integration

Connect Argos to Slack to notify your team about visual changes and get rich previews when an Argos build URL is shared in Slack.

{% hint style="info" %}
The Slack integration is available on Pro and Enterprise plans.
{% endhint %}

### What you get

* Automatic Slack notifications when builds are created, reviewed, approved, or rejected.
* Rich previews when pasting an Argos build URL in Slack.
* Fine-grained control over notifications using automation conditions.

### Slack notifications

Notifications are driven by **automations**: rules that post messages to the right channels at the right time. Typical signals you may want to route to Slack:

* A build is ready for review.
* Changes are requested.
* A build is auto-approved on main.
* Only failed or blocking builds.

Notifications include the build status, branch, author, and a direct link to the build.

![Slack notification sent by Argos](/files/997eda32874de8f5ed75771e5a72928ed8f9537e)

*Example of a Slack notification sent by Argos*

### URL unfurling in Slack

When you paste an Argos build URL into Slack, Argos automatically unfurls it.

The preview includes:

* Build status and outcome
* Project and branch
* Direct shortcut to open the build in Argos

This works in messages, threads, and shared links, which makes reviews and handoffs easier without extra clicks.

### Connect Slack to your team

Connecting your Slack workspace enables URL unfurling and makes Slack available as an automation action.

1. From the dashboard, select your team from the scope selector.
2. Go to the team's **Settings** tab.
3. Select the **Integrations** section.
4. Select **Connect to Slack** and follow the connection flow.

### Set up Slack notifications

Create a notification rule with Argos automations:

1. Select a project in your Argos team.
2. Go to the **Automations** tab and select **New Automation**.
3. Name your automation, e.g., "Notify Slack on build completion".
4. Under **WHEN**, select one or several events that trigger the notification.
5. (Optional) Under **IF**, add conditions such as "Build type is check".

   ![Automation conditions example](/files/1497994cbc5651b74d13450af9bd27e5a8eaead7)
6. Under **THEN**, choose the action **Send notification to Slack**. If your workspace isn't connected yet, select **Connect to Slack** and follow the connection flow.
7. Select the Slack channel and optionally provide the channel ID.

   ![Locate Slack channel ID](/files/990d849cd23027cf3053641e14d251d17f3e239a)

   *Finding the ID of a Slack channel*
8. Select **Send test notification** to verify the connection. A test message is sent to the selected channel.
9. Select **Create Rule** to activate it.

### Troubleshooting and tips

* Make sure the Argos app is authorized in your Slack workspace.
* For private channels, manually invite the bot with `/invite @Argos`.
* Only Argos team admins can configure Slack integrations.
* You can test notifications anytime using **Send test notification**.

Need help setting up Slack integration? Reach out via [Discord](https://argos-ci.com/discord) or [contact support](https://argos-ci.com/contact).


---

# 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://argos-ci.com/docs/learn/integrations/slack-integration.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.