# Slack notifications | Waitlyze Docs

> Send signup and reward notifications to a Slack channel.

Canonical: https://waitlyze.com/docs/slack


Waitlyze sends short, best-effort Slack messages for a published waitlist. Signup count milestones (**1, 10, 100, 1,000**) are enabled by default; you can also choose every verified signup and reward-tier unlocks.

## Connect Slack [#connect-slack]

1. In Slack, add an incoming webhook for the channel that should receive milestones and copy its URL. Slack webhooks must use the official `hooks.slack.com` host.
2. In **Waitlist settings → Notifications**, paste the URL in the Slack card and save. Select one or more triggers, then select **Save triggers** when changing an existing channel.
3. Select **Send test**. The channel connects only if Slack accepts the test message. You can replace its URL or disconnect from the same card.

The session-protected API also supports `PUT /api/wait-lists/{id}/notifications/slack` with `{ "webhookUrl": "https://hooks.slack.com/services/…", "triggers": ["MILESTONE_COUNTS", "VERIFIED_SIGNUP"] }`. `PATCH` with `{ "triggers": ["REWARD_TIER_UNLOCKED"] }` updates preferences without replacing the URL. At least one unique trigger is required. Omit `triggers` on `PUT` to keep existing preferences (new connections default to milestones).

Use `GET` on the same path to check status, triggers, last test time, and error code, `POST` to test, or `DELETE` to disconnect.

## Access and delivery [#access-and-delivery]

The channel endpoint requires a signed-in Waitlyze session with waitlist-management access. It does not accept a signup API key. Owners and admins can manage the channel in the dashboard; other members can view its status.

The webhook URL is encrypted and never returned by the endpoint. Each waitlist can connect one Slack channel. Messages contain no subscriber email or phone. Failed deliveries mark the channel as needing attention without blocking signups, owner email, or customer webhooks. Chat messages are best effort, not a retried event feed.

For signed events, retries, and delivery history, use [Webhooks](/docs/webhooks). See [Notifications](/docs/notifications) for shared behavior and [Integrations](/docs/integrations/overview) for other connections.

## Related Links
- [API Reference](https://waitlyze.com/docs/api/reference) - REST API endpoints
- [Embed Widget](https://waitlyze.com/docs/embed) - Embed instructions
- [Waitlyze Home](https://waitlyze.com/) - Product overview