Receiving notifications
Choose which devices get which notifications, and when.
Devices
Each browser or phone that has notifications turned on is a device, listed on the Devices page. Every device decides for itself what it receives, so a work phone and a laptop can hear about different things. A notification always appears in your inbox; routing only decides which devices are notified.
| Setting | Choices |
|---|---|
| What it gets | For each source: Everything, Warnings and errors, Errors only or Off. New sources sets the choice for sources added later and any source without its own choice. |
| Delivery hours | Any time, Weekdays 9:00–17:00, Outside weekdays 9:00–17:00, or custom days and hours. Custom hours can run overnight, such as 22:00 to 06:00. Outside its hours the device is not notified at all. |
| Quiet hours | Hold notifications overnight and deliver them when quiet hours end. |
| Pause | Stops every notification to the device until you resume it. |
Times follow the workspace time zone, set by the owner in Settings › Profile. Send test on a device checks that it can be reached. A source's Send test notification reaches every unpaused device. Each notification shows which devices it reached, and why the others were skipped.
Delivery
Each source chooses how its notifications are sent, in the Notify step of its flow (Sources, then the source, then Flow). Every event still appears in your inbox straight away.
| Mode | What happens |
|---|---|
| Immediately | Each event is pushed as it arrives. |
| Grouped | Pushed as it arrives, but repeats of the same title replace the previous notification instead of stacking up. A sender can also group events explicitly with the group field in any mode. |
| Hourly, daily or weekly summary | Events are collected and sent as one notification, like 42 events today with a count per level, at the top of each hour, at the hour you choose each day, or on the day and hour you choose each week. |
| Custom schedule | Events are collected and sent on a cron schedule, set in the flow's JSON Editor or through the API. |
Custom schedules
A custom schedule sets "delivery": "custom" and a digest_cron with the standard five cron fields: minute, hour, day of month, month and day of week. Use numbers, *, ranges like 1-5, lists like 1,15 and steps like */30. Sunday is 0 or 7. Times follow the workspace time zone.
| Schedule | Sends |
|---|---|
0 9 * * 1-5 | At 9 AM on weekdays |
*/30 * * * * | Every 30 minutes |
0 8,17 * * * | At 8 AM and 5 PM every day |
0 9 1 * * | At 9 AM on the first of each month |
A summary counts events and lists the top three titles. It is sent to each device at the highest level it contains, so a summary with an error reaches devices set to Errors only. Changing the mode affects events received afterwards; anything already collected is still summarised.
Quiet hours
Set quiet hours per device, on the Devices page under When, to hold notifications overnight. They are delivered when quiet hours end. Leave Errors still come through on to be woken for errors. Sources marked Priority also come through.
Priority and error sources
Two options in a source's Notify step mark the events that matter most.
| Option | Effect |
|---|---|
| Priority: comes through quiet hours | Every notification from the source is delivered during quiet hours. |
| Treat every event as an error | Every event the source receives is recorded at level error, whatever level or success it sends. It is labelled as an error, reaches devices set to Errors only, and comes through quiet hours when Errors still come through is on. |
Use it for sources that only fire on failure, such as uptime alerts. Test notifications and Litehook's own alerts keep their own level.
Inbox and read state
The Notifications page is your inbox: every notification from every source, newest first, with repeats collapsed. Filter it by source or to unread ones. Each person's read and unread state is their own.