Skip to content
Nowlark
Sign inGet the app
How it worksPricingDocsTeams
Get the appSign in
Support menu

Start

Support home

Guides

Send a notificationSchedule, repeat and escalateQuestions and receiptsSources, tones and your feedConnect your toolsTeams, roles and invitesChannels, escalation, webhooks and emailForms and spam protectionConsole, company sign‑in and SCIMAccount, keys and devices

Help

Contact

Schedule, repeat and escalate

Send later, send on a schedule, repeat until someone opens it, and pass it on to the next person when nobody answers.

Send now, send later, send until someone answers, or send to the next person when the first one does not.

Send later#

Add delay (seconds from now) or at (a time with a zone, like 2026-10-07T09:00:00Z) to any send. It waits on the server, so your computer can be off when it arrives.

curl https://nowlark.com/v1/notify \
  -H "X-Nowlark-Key: nlk_…" -H "Content-Type: application/json" \
  -d '{"source":"Standup","title":"Standup in 5","delay":3300}'
NowYou send it. Nothing reaches the phone.
+55 minutesIt arrives, within 15 seconds of its time and never before.
A delay can be from 10 seconds to 7 days.
  • A mistake is told to you now, not at the time it was due: a bad field, or a feature your account does not have, is the answer to the call that asked.
  • Up to 200 sends can wait per account. GET /v1/scheduled lists them and DELETE /v1/scheduled/{id} cancels one that has not fired.
  • A retry is safe. A dedupe_key already used by a waiting send returns duplicate: true and queues nothing.
  • Muting, a priority cap and the repeat rules are applied when it arrives, so a source you mute after scheduling stays muted.

Send on a schedule#

Add every (seconds) with count or until. One of the two is required, so a series always ends.

-d '{"source":"Standup","title":"Standup in 5","every":86400,"count":5,"delay":3300}'
Day 109:55
Day 209:55
Day 309:55
Day 409:55
Day 509:55 · the last
Five sends, a day apart. Up to 1,000 sends, over at most a year.

Urgent means until you open it#

A notification at priority 2 keeps alerting, every 5 minutes for up to an hour, until you open it on any device. Tapping it, reading it in the feed or Mark as Read stops it. Swiping it away does not.

0 minFirst alert
5 minAlerts again
10 minAlerts again
You open itEvery repeat stops, on every device
The default rhythm. Change how often and for how long in Settings › Alerts & Sounds.
  • Long-press a repeating notification in the feed and choose Stop Repeating to quiet it without marking it read.
  • With the Upgrade Pass a source can repeat its own way: open it in Sources and change Repeat, to turn it off for a sender that cries wolf or make the one that matters keep going longer.
  • A newer send with the same replace_key ends the older one's repeating too.
  • Each repeat replaces the last on the phone instead of stacking, and reads "Still unopened". At most five alerts repeat at once per account; a newer one stops the oldest. Repeats do not count against a key's hourly limit.

Pass it on when nobody answers#

On a team channel, escalation tells a second group when the first has not opened the alert.

0 minOn call
10 minBackup and lead, only if still unopened
30 minEveryone on the channel
Anyone opening it, from any device, cancels every later step.

Know what became of it#

GET /v1/receipts/{id} says whether a notification was sent, opened, still repeating, expired or replied to. With callback_url, Nowlark also calls your server once when it is first opened. See Questions, receipts and callbacks.

PreviousSend a notificationNextQuestions and receipts