One notification, every channel the user has.

Send a notification to a notifiable and it is delivered to each channel it asks for: the database (an in-app bell), mail, Discord.

Read the Notifications docs

notify_discord example output: the Discord webhook JSON payload, bot mode, and a failed send with a retry-after.

What you get

Channels: database, mail and Discord.
A receipt records what was delivered where; a channel that failed is a NotificationFailed event.
Honest limit: notifications are not queued yet — queue a job that sends one.

In the docs

Notifications

src/app/notifications/post_live.rs

// One notification, every channel the user can be reached on: the
// database (the in-app bell), mail, Discord.
Notify::instance().send(&author, &PostLive { post }).await?;

impl Notifiable for User {
    fn notifiable_id(&self) -> String {
        self.id.to_string()
    }

    fn notifiable_type(&self) -> &'static str {
        "User"
    }

    fn route_for(&self, channel: &str) -> Option<String> {
        match channel {
            "mail" => Some(self.email.clone()),
            _ => None,
        }
    }
}

Up close

Select an image to see it full size.

curl output of /api/notifications: 5 unread, the latest a post.live notification. — The database channel stores each notification for the bell menu; the API reads them back with an unread count.

Worker log line: notified the author, delivered=["database", "broadcast", "mail"]. — Sending returns a receipt of what each channel did, so the job can log exactly where the notification went.

Lookout timeline rows: notification post.live with its database insert, broadcast, view and mail. — One notification, three channels, visible as children of the notification span.

All features