Quiet hours and digest

Quiet hours (Do Not Disturb) are a per-user schedule during which Notifly does not escalate routine notifications to external channels: email, SMS, calls, chats (Slack, Telegram, Discord, Teams, Mattermost), PagerDuty, Opsgenie and webhooks. Urgent messages (priority at or above the threshold) still wake you up; everything else waits until morning and arrives as a single digest.

Configure them in Profile → Quiet hours (or Cmd/Ctrl+K → “Quiet hours”), and also in the Android app: Settings → Quiet hours. It is a single account setting — it applies on all devices.

How it works

Setting	Meaning
Window (start–end)	Local time in your time zone. End earlier than start means the window crosses midnight (23:00–08:00)
Days	Weekdays, by the day the window starts: “Fri” = Friday night to Saturday morning
Time zone	IANA zone (Europe/Berlin, America/New_York…). Daylight saving time is handled automatically
Urgency threshold	Messages with priority at or above it are delivered and escalated as usual. Default: 8
Digest	When the window ends — one email to your account address and a summary message in your system channel

While a quiet window is active, the delivery worker skips escalation methods that have “matured” for messages below the threshold and marks them as suppressed for good. So at 8:00 you don’t get a flood of SMS for the whole night — you get one digest.

When exactly a message counts as “night-time”

The decision is made at the moment the escalation was due — message creation time plus the method’s timeout. A 22:50 message with a 30-minute timeout matured at 23:20, inside the quiet window, so it goes to the digest. A 07:45 message with the same timeout matures at 08:15 and is sent as usual: that is not a catch-up, just an honest unread timeout.

Whose settings apply: a channel’s escalation is configured by its owner, so the channel owner’s quiet hours are used.

Push notifications

The server delivers instant push (WebSocket) as usual — silencing on the device is done by the app using the same settings: the Android app shows notifications below the threshold without sound, vibration or alarm mode (marked “quiet hours”) and keeps a copy of the settings so it can stay quiet even offline. Nothing is lost — the messages are in your feed, just like during the day. The iOS app likewise shows such messages silently (while it is open — in the background the iOS app receives no notifications).

Digest

If something was suppressed during the window and the digest is enabled, a few minutes after the window ends you get:

• an email to your account address: message counts per channel, up to 10 of the most important titles (by priority) and a link to the admin panel;
• a message in the system channel of your feed with the same summary (markdown).

Messages you already read by morning are left out; if everything was read, there is no digest. The digest is sent exactly once per window.

REST API

# Current settings (new users: disabled, 23:00–08:00 Europe/Moscow)
curl -H "X-Notifly-Key: $TOKEN" https://api.notifly.ru/current/user/quiet-hours

# Save
curl -X PUT -H "X-Notifly-Key: $TOKEN" -H "Content-Type: application/json" \
  https://api.notifly.ru/current/user/quiet-hours \
  -d '{"enabled":true,"timezone":"Europe/Berlin","start":"23:00","end":"08:00",
       "days":[1,2,3,4,5,6,7],"breakthroughPriority":8,"digest":true}'

The body is the whole object; fields you omit keep their previous values. The response is the saved object in canonical form ("8:00" → "08:00", days sorted). Validation errors return 400: unknown time zone, time not in HH:MM, start equal to end, a day outside 1..7, empty days with enabled: true, a threshold outside 0..10.

See also

• Delivery & escalation — which methods are suppressed and how timeouts work.
• Maintenance windows — planned work: silence for channels and monitors rather than for a person.
• Android app — where the settings apply to push.