GitLab pipeline failed notifications on your phone.
Get a High-priority push notification when a GitLab CI/CD pipeline fails, optionally with a quiet push when one passes.
Monday 5 October
9:41
JustPushnow
Pipeline failed
Get a High-priority push notification when a GitLab CI/CD pipeline fails, optionally with a quiet push when one passes.
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 Pipeline events.
STEP 03
Get a push on your phone
With the text, sound and buttons from the recipe.
How to set up the GitLab pipeline 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 Pipeline events and click Add webhook. Use the Test dropdown to send a sample event.
- Tick **Pipeline events** under **Trigger**. GitLab sends an event for every status change (pending, running, …), but only failed pipelines push by default. Add `?all=1` to the URL to also get a quiet push when a pipeline passes:
- ```
- your webhook URL?all=1
- ```
- 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 → Pipeline Hook (pipeline failed)
2// Fires when a CI/CD pipeline fails. Add ?all=1 to the URL to also get a quiet push when one passes.
3// Docs: https://docs.gitlab.com/user/project/integrations/webhook_events/#pipeline-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
18// Query flags such as ?all=1.
19function flag(request, name) {
20 return ["1", "true", "yes"].includes(String(request.query?.[name] ?? "").toLowerCase())
21}
22
23function handleRequest(request) {
24 const body = request.body && typeof request.body === "object" ? request.body : {}
25 const event = header(request, "x-gitlab-event")
26
27 // Guard: only pipeline events. The header decides when it's there; the payload's
28 // shape is the fallback (for example in Studio's Test runner).
29 if (event ? event !== "Pipeline Hook" : body.object_kind !== "pipeline") {
30 console.log(`Ignoring GitLab "${event ?? body.object_kind ?? "unknown"}" event`)
31 return null
32 }
33
34 const pipeline = body.object_attributes ?? {}
35 // Pipelines report every status change (pending, running, …); only the end result matters.
36 const failed = pipeline.status === "failed"
37 const passed = pipeline.status === "success"
38
39 if (!failed && !(passed && flag(request, "all"))) {
40 console.log(`Skipping pipeline status "${pipeline.status ?? "unknown"}"`)
41 return null
42 }
43
44 const repo = body.project?.path_with_namespace ?? body.project?.name ?? "a project"
45 const where = [repo, pipeline.ref].filter(Boolean).join(" · ")
46 const what = body.commit?.title ?? (typeof body.commit?.message === "string" ? body.commit.message.split("\n")[0] : null)
47 const who = body.user?.username
48 // Jobs that broke the pipeline (allowed failures don't count).
49 const jobs = Array.isArray(body.builds)
50 ? body.builds.filter((job) => job?.status === "failed" && !job.allow_failure && job.name).map((job) => job.name)
51 : []
52 const number = pipeline.id ? ` #${pipeline.id}` : ""
53
54 return {
55 title: failed ? `❌ Pipeline${number} failed` : `✅ Pipeline${number} passed`,
56 message:
57 where +
58 (what ? ` — ${what}` : "") +
59 (who ? ` (@${who})` : "") +
60 (failed && jobs.length ? ` · Failed: ${jobs.join(", ")}` : ""),
61 topic: "GitLab",
62 priority: failed ? 1 : -1, // High for broken pipelines, Low for the optional success pushes
63 buttons: link(pipeline.url, "View pipeline"),
64 }
65}
The GitLab Pipeline Hook webhook
This is what GitLab sends to your URL for pipeline events. It is a sample, trimmed to the fields recipes use.
Pipeline Hook · sample.json
1{
2 "user": {
3 "id": 42,
4 "name": "Jane Doe",
5 "email": "[REDACTED]",
6 "username": "janedoe"
7 },
8 "builds": [
9 {
10 "id": 5510,
11 "name": "rspec",
12 "stage": "test",
13 "status": "failed",
14 "allow_failure": false,
15 "failure_reason": "script_failure"
16 },
17 {
18 "id": 5511,
19 "name": "lint",
20 "stage": "test",
21 "status": "failed",
22 "allow_failure": true,
23 "failure_reason": "script_failure"
24 },
25 {
26 "id": 5509,
27 "name": "compile",
28 "stage": "build",
29 "status": "success",
30 "allow_failure": false,
31 "failure_reason": null
32 }
33 ],
34 "commit": {
35 "id": "bcbb5ec396a2c0f828686f14fac9b80b780504f2",
36 "url": "https://gitlab.example.com/acme/web/-/commit/bcbb5ec396a2c0f828686f14fac9b80b780504f2",
37 "title": "Fix checkout totals rounding",
38 "author": {
39 "name": "Jane Doe",
41 },
42 "message": "Fix checkout totals rounding\n\nCloses #88\n",
43 "timestamp": "2026-09-28T11:11:50+02:00"
44 },
45 "project": {
46 "id": 7,
47 "name": "web",
48 "web_url": "https://gitlab.example.com/acme/web",
49 "namespace": "Acme",
50 "default_branch": "main",
51 "path_with_namespace": "acme/web"
52 },
53 "object_kind": "pipeline",
54 "merge_request": null,
55 "object_attributes": {
56 "id": 1204,
57 "iid": 87,
58 "ref": "main",
59 "sha": "bcbb5ec396a2c0f828686f14fac9b80b780504f2",
60 "tag": false,
61 "url": "https://gitlab.example.com/acme/web/-/pipelines/1204",
62 "name": null,
63 "source": "push",
64 "stages": [
65 "build",
66 "test"
67 ],
68 "status": "failed",
69 "duration": 281,
70 "created_at": "2026-09-28 09:12:03 UTC",
71 "finished_at": "2026-09-28 09:16:44 UTC",
72 "default_branch": true,
73 "detailed_status": "failed"
74 }
75}
GitLab pipeline failed 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.