GitLab release created notifications on your phone.
Get a push notification when a new release is created in your GitLab project.
Monday 5 October
9:41
JustPushnow
Release created
Get a push notification when a new release is created in your GitLab project.
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 GitLab
Add it as a webhook for Releases events.
STEP 03
Get a push on your phone
With the text, sound and buttons from the recipe.
How to set up the GitLab releases events webhook
- Click Install in Studio and sign in. The recipe is added to your account and you get a personal webhook URL.
- In your GitLab project (or group), go to Settings > Webhooks and click Add new webhook.
- Paste your webhook URL as the URL.https://••••••••/•••••••• your personal URL, shown after install
- Under Trigger, tick Releases events and click Add webhook. Use the Test dropdown to send a sample event.
- Tick **Releases events** under **Trigger**. Pushes go out when a release is created; edits and deletions are ignored. A release with a future release date is marked "(upcoming)".
- A group webhook covers every project in the group. Links in the push come from the payload, so self-managed GitLab instances work too.
- GitLab can sign deliveries with a **Signing token** (`webhook-signature`, HMAC-SHA256) or send a plain **Secret token** (`X-Gitlab-Token`), but JustPush doesn't check either 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// GitLab → Release Hook (release created)
2// Fires when a new release is created in a project or group your webhook covers.
3// Docs: https://docs.gitlab.com/user/project/integrations/webhook_events/#release-events
4
5// Header names can arrive in any case.
6function header(request, name) {
7 const headers = request.headers || {}
8 const key = Object.keys(headers).find((k) => k.toLowerCase() === name)
9 const value = key ? headers[key] : null
10 return Array.isArray(value) ? value[0] : value
11}
12
13// Only link to real http(s) URLs.
14function link(url, cta) {
15 return typeof url === "string" && /^https?:\/\//.test(url) ? [{ cta, url }] : []
16}
17
18function handleRequest(request) {
19 const body = request.body && typeof request.body === "object" ? request.body : {}
20 const event = header(request, "x-gitlab-event")
21
22 // Guard: only release events. The header decides when it's there; the payload's
23 // shape is the fallback (for example in Studio's Test runner).
24 if (event ? event !== "Release Hook" : body.object_kind !== "release") {
25 console.log(`Ignoring GitLab "${event ?? body.object_kind ?? "unknown"}" event`)
26 return null
27 }
28
29 // Only new releases; updates and deletions are skipped. Release events keep `action` at the top level.
30 if (body.action !== "create") {
31 console.log(`Skipping release action "${body.action ?? "unknown"}"`)
32 return null
33 }
34
35 const repo = body.project?.path_with_namespace ?? body.project?.name ?? "a project"
36 const tag = body.tag ?? body.name ?? "a new version"
37 const name = body.name && body.name !== body.tag ? ` — ${body.name}` : ""
38 // An upcoming release has a release date in the future.
39 const upcoming = typeof body.released_at === "string" && Date.parse(body.released_at) > Date.now()
40
41 return {
42 title: `${upcoming ? "🗓️" : "🚀"} ${repo} ${tag}${upcoming ? " (upcoming)" : ""}`,
43 message: `Released${body.commit?.title ? ` from "${body.commit.title}"` : ""}${name}`,
44 topic: "GitLab",
45 priority: upcoming ? -1 : 0, // Upcoming releases are quieter than real ones
46 buttons: link(body.url, "View release"),
47 }
48}
The GitLab Release Hook webhook
This is what GitLab sends to your URL for releases events. It is a sample, trimmed to the fields recipes use.
Release Hook · sample.json
1{
2 "id": 314,
3 "tag": "v2.4.0",
4 "url": "https://gitlab.example.com/acme/web/-/releases/v2.4.0",
5 "name": "Faster checkout",
6 "action": "create",
7 "assets": {
8 "count": 4,
9 "links": [],
10 "sources": [
11 {
12 "url": "https://gitlab.example.com/acme/web/-/archive/v2.4.0/web-v2.4.0.zip",
13 "format": "zip"
14 }
15 ]
16 },
17 "commit": {
18 "id": "ee0a3fb31ac16e11b9dbb596ad16d4af654d08f8",
19 "url": "https://gitlab.example.com/acme/web/-/commit/ee0a3fb31ac16e11b9dbb596ad16d4af654d08f8",
20 "title": "Release v2.4.0",
21 "author": {
22 "name": "Jane Doe",
24 },
25 "message": "Release v2.4.0",
26 "timestamp": "2026-09-28T14:50:32+02:00"
27 },
28 "project": {
29 "id": 7,
30 "name": "web",
31 "web_url": "https://gitlab.example.com/acme/web",
32 "namespace": "Acme",
33 "default_branch": "main",
34 "path_with_namespace": "acme/web"
35 },
36 "created_at": "2026-09-28T12:55:12.000Z",
37 "description": "Faster checkout and Apple Pay.",
38 "object_kind": "release",
39 "released_at": "2026-09-28T12:55:12.000Z"
40}
GitLab release created 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 GitLab 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
GitLab on your phone in two minutes.
Install the recipe, paste one URL, done. Free for 30 days, no credit card required.