Notifications
Dreeve can push a notification to you when something needs your attention. It uses Shoutrrr, which speaks to a long list of services (ntfy, Gotify, Discord, Telegram, Slack, email, and plenty more) through a single URL format.
What triggers a notification
Section titled “What triggers a notification”| Trigger | Notes |
|---|---|
| A new import just ran | Your data has been imported and the app has been updated. |
| Gear maintenance is due | A maintenance task has reached its interval. |
| A new app version is available | A newer Dreeve release has been published. |
-
Work out the Shoutrrr service URL for your notification service. The Shoutrrr services documentation has the format for each one. A few examples:
ntfy://ntfy.sh/your-topicdiscord://token@idtelegram://token@telegram?chats=@channel-1gotify://gotify.example.com/token -
Add it under Settings → Integrations, in the notifications section. You can configure more than one, every notification goes to all of them.
-
Enable the notification jobs you want under Settings → Daemon.
Testing it
Section titled “Testing it”You can test your Shoutrrr config by manually triggering a notification:
> docker compose exec app shoutrrr send -v --url="ntfy://ntfy.sh/your-topic" --message="Hello" --title="Test"ntfy.sh with an authentication token
Section titled “ntfy.sh with an authentication token”If you are:
- Running a locally hosted NTFY server
- Requiring authentication to send notifications
- Using an authentication token
You may notice that the Shoutrrr documentation does not clearly explain how to format the notification URL in this scenario. Use the following format:
ntfy://:[email protected]/your-topic