Heroku release notifications on your phone.
Get a push notification when a new release of your Heroku app succeeds or fails, with the release version and what changed.
Monday 5 October
9:41
JustPushnow
Release
Get a push notification when a new release of your Heroku app succeeds or fails, with the release version and what changed.
Three steps to your first push
STEP 01
Install the recipe
One click in Studio gives you a personal webhook URL.
STEP 02
Paste your URL into Heroku
Add it as a webhook for api:release.
STEP 03
Get a push on your phone
With the text, sound and buttons from the recipe.
How to set up the Heroku api:release webhook
- Click Install in Studio and sign in. The recipe is added to your account and you get a personal webhook URL.
- In the Heroku Dashboard, open your app and choose More > View webhooks, then create a webhook. Or use the CLI command in the setup notes below.
- Paste your webhook URL as the URL and subscribe to the api:release event type.https://••••••••/•••••••• your personal URL, shown after install
- Save. Each app needs its own webhook.
- Subscribe the webhook to the **`api:release`** entity. In the Dashboard that's **More → View webhooks** on your app; with the Heroku CLI:
- ```
- heroku webhooks:add -i api:release -l notify -u your webhook URL -a your-app
- ```
- Use `-l sync` instead of `-l notify` if you want Heroku to retry failed deliveries.
- Heroku sends two or three events per release (created, then updated as the release phase runs). The recipe pushes once, when the status becomes `succeeded` or `failed`.
- Every config var change and add-on change also creates a release. Add `?deploys=1` to only get successful releases that ship code (failed releases always push):
- ```
- your webhook URL?deploys=1
- ```
- Heroku signs every delivery (`Heroku-Webhook-Hmac-SHA256`), but JustPush doesn't check that signature yet, so keep your endpoint URL private.
What runs when the webhook arrives
Studio calls handleRequest(request) with the incoming webhook and sends the message it returns. It's yours after install; change anything.
transform.js
1// Heroku → api:release (release succeeded or failed)
2// Fires when a Heroku app webhook subscribed to api:release reports a release reaching
3// "succeeded" or "failed". Pending steps (and updates that don't change the status) stay quiet.
4// Docs: https://devcenter.heroku.com/articles/webhook-events#api-release
5
6// Final release statuses, their labels and how loud to be.
7const STATUSES = {
8 // A failed release (usually the release phase) means the new version isn't live.
9 failed: { emoji: "❌", verb: "release failed", priority: 1 },
10 // A successful release is routine.
11 succeeded: { emoji: "✅", verb: "released", priority: -1 },
12}
13
14// Look a key up in one of the tables above, ignoring inherited names like "toString".
15function pick(table, key, fallback) {
16 return Object.prototype.hasOwnProperty.call(table, key) ? table[key] : fallback
17}
18
19// Only link to real http(s) URLs.
20function link(url, cta) {
21 return typeof url === "string" && /^https?:\/\//.test(url) ? [{ cta, url }] : []
22}
23
24function handleRequest(request) {
25 const body = request.body && typeof request.body === "object" ? request.body : {}
26 const data = body.data && typeof body.data === "object" ? body.data : {}
27 const include = body.webhook_metadata?.event?.include
28
29 // Guard: only release events.
30 if (body.resource !== "release" && include !== "api:release") {
31 console.log(`Ignoring Heroku "${include ?? body.resource ?? "unknown"}" event`)
32 return null
33 }
34
35 const status = pick(STATUSES, data.status, null)
36 // One push per release: on create when it's already final (no release phase), or on the
37 // update that changes the status. Updates that only flip "current" are skipped.
38 const previous = body.previous_data && typeof body.previous_data === "object" ? body.previous_data : {}
39 const changed = body.action === "create" || Object.prototype.hasOwnProperty.call(previous, "status")
40 if (!status || !changed) {
41 console.log(`Skipping release ${body.action ?? "event"} with status "${data.status ?? "none"}"`)
42 return null
43 }
44
45 // ?deploys=1 skips successful releases that aren't code deploys (config vars, add-ons).
46 const deploysOnly = ["1", "true", "yes"].includes(String(request.query?.deploys ?? "").toLowerCase())
47 if (deploysOnly && data.status === "succeeded" && !data.slug) {
48 console.log("Skipping a release without a slug (the URL has ?deploys=1)")
49 return null
50 }
51
52 const app = typeof data.app?.name === "string" && data.app.name ? data.app.name : null
53 const version = Number.isInteger(data.version) ? ` v${data.version}` : ""
54 const who = data.user?.email ?? body.actor?.email
55 const message = [data.description, who].filter((part) => typeof part === "string" && part).join(" · ")
56
57 return {
58 title: `${status.emoji} ${app ?? "Your app"}${version} ${status.verb}`,
59 message: message || (data.status === "failed" ? "The release failed" : "The release is live"),
60 topic: "Heroku",
61 priority: status.priority,
62 buttons: app ? link(`https://dashboard.heroku.com/apps/${encodeURIComponent(app)}/activity`, "View activity") : [],
63 }
64}
The Heroku api:release webhook
This is what Heroku sends to your URL for api:release. It is a sample, trimmed to the fields recipes use.
api:release · sample.json
1{
2 "id": "4273290b-193c-42fa-8931-7f2c92c5b28f",
3 "data": {
4 "id": "ddc2fba2-b2ad-41f5-bf7c-6e9b4614a53b",
5 "app": {
6 "id": "61cfe066-573f-45b4-a566-138323880eeb",
7 "name": "acme-api"
8 },
9 "slug": {
10 "id": "7adfdf15-f4a8-429d-bfbf-09d130ee2182"
11 },
12 "user": {
13 "id": "125f0179-2fc8-4833-9e20-6e9314f2b233",
15 },
16 "status": "failed",
17 "current": false,
18 "version": 42,
19 "created_at": "2026-09-29T07:29:51Z",
20 "updated_at": "2026-09-29T07:30:32Z",
21 "description": "Deploy 3f2a1bc9"
22 },
23 "actor": {
24 "id": "125f0179-2fc8-4833-9e20-6e9314f2b233",
26 },
27 "action": "update",
28 "version": "application/vnd.heroku+json; version=3",
29 "resource": "release",
30 "sequence": null,
31 "created_at": "2026-09-29T07:30:32Z",
32 "updated_at": "2026-09-29T07:30:32Z",
33 "published_at": null,
34 "previous_data": {
35 "status": "pending"
36 },
37 "webhook_metadata": {
38 "event": {
39 "id": "4273290b-193c-42fa-8931-7f2c92c5b28f",
40 "include": "api:release"
41 },
42 "attempt": {
43 "id": "8a44f820-2354-489d-9a11-a793cbf49979"
44 },
45 "webhook": {
46 "id": "b54e6a7e-d162-4bd7-ab42-1011582c19cc"
47 },
48 "delivery": {
49 "id": "d244009a-670f-4340-88e9-789a4f9002d5"
50 }
51 }
52}
Heroku release notifications: questions
Does this work on iPhone and Android?
Yes. Install the JustPush app from the App Store or Google Play and sign in. Every phone signed in to your account gets the notification.
Do I need to write code?
No. Install the recipe in Studio, paste your webhook URL into Heroku and you are done. The code is there if you want to change the text, the sound or the buttons.
Can I change what the notification says?
Yes. After install the recipe's code is yours. Edit it in Studio and test it against the sample payload before you save.
What does it cost?
JustPush is free for 30 days. After that it's $19.99 a year, or $39.99 once. There is no extra charge for recipes.
Ready when you are
Heroku on your phone in two minutes.
Install the recipe, paste one URL, done. Free for 30 days, no credit card required.