Notifications overview
Coolify sends team notifications when selected deployment, backup, scheduled task, container, and server events occur. Each notification channel has its own connection details and event selections, so you can send urgent alerts to one destination and routine updates to another.
How notifications work
A notification requires both parts of the configuration:
- An enabled channel with valid connection details.
- The event selected under that channel's Notification Settings.
Coolify stores notification settings for the current team. Team members with permission to update notification settings can change a channel, while sending a test notification requires the corresponding permission.
Choose a channel
| Channel | What you need | Guide |
|---|---|---|
| Hosted email, system-wide transactional email, SMTP, or a Resend API key | ||
| Discord | A Discord webhook URL | Discord |
| Telegram | A bot API token and chat ID | Telegram |
| Slack or Mattermost | A Slack-compatible incoming webhook URL | Slack & Mattermost |
| Pushover | A Pushover user key and application API token | Pushover |
| Webhook | An HTTP or HTTPS endpoint that accepts JSON POST requests | Webhook notifications |
You can enable more than one channel. Event selections are independent for each channel.
Configure notifications
The exact fields differ by channel, but the main flow is the same:
- Open Notifications in the Coolify sidebar.
- Select a channel.
- Enter and save the channel's connection details.
- Turn on Enabled.
- Under Notification Settings, select the events to send through this channel.
- Send a test notification and confirm that it arrives at the destination.
If the test does not arrive, keep the channel enabled while you check its credentials, destination permissions, and provider logs.
What to read next
- Notification events explains every selectable event and its trigger.
- Webhook payload reference documents the JSON body for each webhook event.