Skip to content
Nowlark
Sign inGet the app
How it worksPricingDocsTeams
Sign inGet the app
Browse guides

Start

All guides

Alerts from your tools

GitHub alerts on your iPhoneGrafana alerts on your iPhonePrometheus Alertmanager alerts on your iPhoneDatadog alerts on your iPhoneSentry alerts on your iPhoneUptime Kuma alerts on your iPhoneHealthchecks.io alerts on your iPhoneHome Assistant alerts on your iPhone and Apple Watch

Recipes

Approve a GitHub deploy from your iPhoneMove from Opsgenie to Nowlark

Forms on your site

Add your Nowlark form to WordPressAdd your Nowlark form to WordPress.comAdd your Nowlark form to WixAdd your Nowlark form to WebflowAdd your Nowlark form to GhostAdd your Nowlark form to Google SitesAdd your Nowlark form to a site you build yourself

Reference

API referenceSupport

GitHub alerts on your iPhone

A failed workflow run arrives at High priority, and the next passing run replaces it. Pull requests, issues and releases come through the same repository webhook.

N
GITHUB ACME/SHOP · nowDeploy failure on mainBump checkout to v2.4
A failed workflow run. The next run of that workflow on main replaces it, so a fix shows as success.

What you need#

  • Nowlark on your iPhone, and your key from Settings › Connect an App › Create Your Key. Copy it when it is shown, because it is shown once. It starts nlk_.
  • A GitHub repository where you can change its settings, or an organization you own.

Add Nowlark to GitHub#

  1. In the repository, open Settings › Webhooks and click Add webhook. For every repository in an organization at once, open the organization's Settings › Webhooks instead.
  2. Paste this as the Payload URL, with your own key in place of nlk_…:
https://nowlark.com/v1/hooks/github?key=nlk_…
  1. Set Content type to application/json. Nowlark checks the key in the address, so Secret can stay empty.
  2. Under Which events would you like to trigger this webhook?, choose Let me select individual events and tick the ones you want: Workflow runs, Pull requests, Issues, Releases and Pushes.
  3. Click Add webhook. GitHub sends a ping, and a "GitHub webhook connected" notification, at Low priority, arrives on your iPhone.

GitHub cannot add a header to its webhooks, so the key goes in the address. Make a key just for GitHub. If the address leaks, revoke that key in Settings › Connect an App, and your other senders keep working.

What arrives#

In GitHub On your iPhone
A workflow run fails
"Deploy failure on main", at High priority. Tap it to open the run.
It passes again
The same notification changes to show the run passed, at Low priority. A passing run with no failure before it arrives silently, at Low.
A pull request is opened, reopened, marked ready, merged or closed
"PR #42 merged: Add Apple Pay", with who opened it.
An issue is opened, reopened or closed
"Issue #17 opened", with its title.
A release is published
"Released v2.4".
A push
How many commits, to which branch, and the last commit's message.

Pull requests, issues, releases and pushes arrive at Normal priority, so tick only the events you want to hear about. Anything else GitHub sends, such as a star or a label change, is accepted and ignored, so it never wakes you.

Each repository arrives as its own source, such as GitHub acme/shop. In the app's Sources tab you can give each a colour, and with the Upgrade Pass its own tone.

On a team channel#

Use a channel key instead of your own, and everyone on the channel gets a failed run. When the next run passes, the alert is resolved on the channel too, and no later escalation step goes out for it. Channels and escalation covers the rest.

Approve a deploy, too#

Approve a GitHub deploy from your iPhone pauses a workflow before production and asks you on your iPhone.

Get the app

PreviousAll guidesNextGrafana alerts on your iPhone