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

# Slack issue notifications

> Post Work issue creation, start, and completion notices to a Slack channel.

Starting with ReasonOS 1.0.2, a Slack notification subscription can post
short Work issue notices to a channel. The first version supports channel
notifications, without Slack commands, direct messages, or two-way sync.

## Connect a channel

1. In Slack, create an incoming webhook for the channel you want. Slack
   binds its webhook URL to that channel.
2. In ReasonOS, open **Settings → Organization settings → Webhooks** and
   choose **Add webhook**.
3. Below the endpoint field, left of the project selector (**Every
   project**), open the pill that reads **Signed webhook** and choose
   **Slack channel**. Enter a name, and paste the incoming webhook URL into
   the field above, now labelled **Slack webhook URL**. The type can be chosen
   only when adding a webhook; an existing webhook keeps its type when
   edited.
4. Choose the project and keep or narrow the three preselected issue events.
   An organization-wide subscription can receive events from every project.
5. Save the subscription.

You need permission to manage organization settings. A branch agent cannot
configure this integration for you.
The webhook URL is a credential: paste it into this form, not chat or an
issue. ReasonOS stores it encrypted and does not show it again. When editing,
leave the field empty to keep the current URL, or paste a replacement.

There is no **Send test notice** action in this version. Notices follow real
issue events after the subscription is saved.

## What gets posted

* **Created:** a newly created issue. Imported issues do not produce Slack
  creation notices.
* **Started:** a move into a status in the In Progress category.
* **Completed:** a move into a completed-category status.

A notice includes the linked issue identifier, title, and relevant status
transition. It does not include descriptions or comments. Custom statuses
count by their category: moving between two In Progress-category statuses
does not post. Reopening and completing an issue again produces a new
completion notice.

## Delivery and troubleshooting

Open the subscription's delivery history to inspect pending, delivered, or
failed attempts. A revoked integration or unavailable channel can fail a
delivery; check the Slack integration and replace its URL if needed.

ReasonOS uses bounded retries for temporary failures and rate limits.
Notices are ordered within each subscription; two subscriptions posting to
the same channel are independent. A lost acknowledgment can cause a
duplicate notice. Manual redelivery can post the notice again too.

For signed HTTPS integrations, see [Webhooks](/platform/webhooks).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.