# Notifications | Waitlyze Docs

> Configure Slack and Discord signup and reward messages.

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


Waitlyze can send best-effort messages to one Slack channel and one Discord channel per waitlist. Open **Waitlist settings → Notifications** to connect, test, choose triggers, and disconnect each channel independently.

Each channel is inactive until you save an official webhook URL and send a successful test. A URL change requires a new test; changing triggers alone does not. The dashboard displays the channel status, last test time, and error code. Owners and admins can manage channels; other members can view status. Signup API keys cannot manage them.

## Choose a destination [#choose-a-destination]

<Cards>
<Card className="waitlyze-integration-card" icon={<img src="/integrations/slack.svg" width={20} height={20} className="size-5 object-contain" alt="" />} title="Slack" href="/docs/slack" description="Create an incoming webhook for signup and reward pings." />
<Card className="waitlyze-integration-card" icon={<img src="/integrations/discord.svg" width={20} height={20} className="size-5 object-contain" alt="" />} title="Discord" href="/docs/discord" description="Create a channel webhook for signup and reward pings." />
</Cards>

## Shared behavior [#shared-behavior]

- The default trigger sends at **1, 10, 100, or 1,000 signups**. Optionally enable **Every verified signup** and **Reward tier unlocked** per channel. At least one trigger must stay selected.
- Messages are sent for published waitlists only. They contain a waitlist name and count or a generic signup/reward summary, never subscriber contact details. Triggers are deduplicated by signup, milestone count, or referrer/tier threshold.
- Queued notifications are delivered by the outbox scheduler. They are best effort, not a retried event stream; a channel disabled before delivery does not receive queued messages.
- A failing channel is marked as needing attention and skipped. Signup intake, owner email, and webhooks continue independently.
- Use [Webhooks](/docs/webhooks) for signed event payloads, retries, and delivery recovery.

## 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