Notifications

The events that matter to an affiliate business — a new conversion at a notable size, a broken tracking link, a stalled payout, an integration that's stopped syncing, a postback validation failure — shouldn't be buried somewhere you check three times a day. They should reach the people who need to act on them, in the channels those people already use, at a cadence that surfaces the signal rather than drowning it.

Routy's notifications system handles delivery across Slack, email, browser web push, and an in-app inbox. Same event, the right channel for the right person, with routing rules that send the alerts a specific team member cares about to the channel they actually monitor.

After configuring notifications, the following becomes available:

• Multi-channel delivery — Slack, email, browser web push, and in-app inbox — pick the channel per event type. A high-priority alert (broken critical link) can fire to all four; a low-priority informational event (daily summary) might only fire to email.
• Slack integration for the alerts your team needs to act on in the moment. Routy posts alerts directly to the Slack channels you specify, with the relevant detail (link, source, error, timestamp) included in the message so the responder has context without needing to dig.
• Channel routing per event. Send conversion alerts to #sales, link-monitor alerts to #ops, payout updates to email-only, integration-sync failures to in-app, all configured once and routed automatically. No manual triage of "which channel does this go to" per event.
• Per-user preferences so each team member tunes the noise to their role. The media buyer doesn't need every payout notification; the finance person doesn't need every postback error; both can configure their own channels without affecting anyone else's setup.
• Throttling built in so a spike in events doesn't drown the channel. If something is firing 100 alerts a minute (because a broken postback is generating cascading failures), the throttle collapses them into one summary alert rather than flooding Slack.

System-critical notifications (password resets, account verifications, security alerts) are always delivered regardless of per-user preferences. Everything else is opt-in per event type, per channel, per user.

You pick which events to be notified about, choose the channels you want for each, and Routy starts delivering. The configuration happens at two levels:

• Account-level routing determines the default behaviour for each event type — which channels fire, which Slack channel a specific event type posts to, which team distribution list receives email alerts.
• Per-user preferences layer on top of the account-level defaults. A specific user can opt into more or fewer event types, change which Slack username receives @-mentions for them, or mute a category they don't care about.

Behind the scenes, every alert-worthy event in Routy fires into a notification queue, gets evaluated against the routing rules, and gets delivered to the matched channels. The throttling logic deduplicates repeat events within a short window so a misconfigured trigger doesn't generate a flood.

Worth knowing:

• Slack channel configuration uses Slack's standard OAuth flow to add Routy as an app, after which the integration can post to any channel the app is added to.
• Email delivery uses standard email infrastructure, with the from-address configurable per account.
• Web push works in browsers that support the Push API (Chrome, Firefox, Edge, and increasingly Safari). The browser asks for permission on first opt-in.
• The in-app inbox holds the full history of notifications for the account, with read/unread state per user, so even alerts that arrived outside working hours can be reviewed later.

The argument for proper notification routing is mostly about team efficiency at scale. When everything that needs attention ends up in one channel (or worse, in one email inbox), important alerts get lost in the noise. When alerts route to the right channel for the right person, response time on the critical events improves dramatically, and the team stops developing the "ignore all Routy notifications" reflex that comes from being over-notified.

Slack specifically tends to be the highest-value channel for active operations — the alerts arrive where the team is already working, the responses can happen in the same thread, and the audit trail of who responded to what is captured naturally. For operations using Slack for their broader team communication, the integration usually pays back the configuration time within the first week.

For lean teams running async, the per-user preferences matter more. A two-person operation where one person handles tracking and the other handles finance can configure their notification routing once and stop having to triage each other's alerts.