Slack alerts post identity events into a channel your team already watches. This is an incoming webhook, not the Slack sign-in connector. One environment can have several channels, each with its own triggers.

## Create the incoming webhook

1. In Slack, create an incoming webhook for the channel that should receive alerts.
2. Copy the URL. It looks like `https://hooks.slack.com/services/...`.

## Add the channel in Authdog

In the [Authdog console](https://console.authdog.com):

1. Select the project and environment.
2. Open **Notifications > Channels**.
3. Select **Add Channel**.
4. Set **Channel Name** and **Channel Type** to **Slack**.
5. Paste the URL into **Webhook URL**.
6. Set **Default Channel** if you want the message routed to a named channel in addition to the webhook's default.
7. Pick the triggers. A growth channel might take sign-ups only. A security channel might take failures and privilege changes. An empty event list drains every event.
8. Save and send a test.

The webhook URL is stored as a secret and shown redacted after save. Delivery retries on failure, with backoff starting at 60 seconds, up to five attempts. A brief Slack outage does not drop the event.

## Test it

1. Send the channel's test delivery and confirm the message in Slack.
2. Trigger a real event you subscribed to, such as a sign-in in that environment.
3. Confirm a channel with a narrow trigger list stays quiet for events you did not select.

Create the production channel in the production environment. Dev and prod do not share webhook URLs.

## Related

| Read | To learn how to |
| --- | --- |
| [Notifications](/docs/console/notifications) | Channels, triggers, and delivery |
| [Events and webhooks](/docs/events-webhooks) | Retry and delivery records |
| [Audit](/docs/console/audit) | The event types a channel can subscribe to |
| [Marketplace](/marketplace/slack) | The listing for this integration |