GitLab Push Notifications on Your Phone

Why use Hookfire with GitLab?

Instant push notifications

Get notified on your phone the moment a GitLab webhook fires. No more checking dashboards.

Subscribe to what matters

Choose exactly which GitLab events trigger notifications. Filter out the noise.

Team-wide delivery

Control who on your team gets notified and how: push notifications, record only, or both.

Setup in under 2 minutes

Copy a webhook URL, paste it in GitLab, and you're done. No code required.

Supported events

Event	Sample notification
Tag push `Tag Push Hook` 🏷️ Tag pushed in team/project testuser pushed tag refs/tags/v1.0.0	🏷️ Tag pushed in team/project testuser pushed tag refs/tags/v1.0.0
Merge request `Merge Request Hook` 🔀 MR open: !5 Add dark mode by Test User in team/project	🔀 MR open: !5 Add dark mode by Test User in team/project
Issue `Issue Hook` 🐛 Issue open: #12 Fix login bug by Test User in team/project	🐛 Issue open: #12 Fix login bug by Test User in team/project
Release `Release Hook` 🚀 Release create: v1.0.0 Release Version 1.0 create in team/project	🚀 Release create: v1.0.0 Release Version 1.0 create in team/project
Comment `Note Hook` 💬 Comment on MergeRequest in team/project Test User: Looks good to me!	💬 Comment on MergeRequest in team/project Test User: Looks good to me!
Pipeline `Pipeline Hook` ⚙️ Pipeline success: main Pipeline success on main in team/project	⚙️ Pipeline success: main Pipeline success on main in team/project
Job `Job Hook` 🔧 Job success: test-suite Job test-suite success on main in project	🔧 Job success: test-suite Job test-suite success on main in project
Wiki page `Wiki Page Hook` 📝 Wiki create: Getting Started Test User create wiki page Getting Started in team/project	📝 Wiki create: Getting Started Test User create wiki page Getting Started in team/project
Push `Push Hook` 📦 Push to team/project testuser pushed 1 commit(s) to refs/heads/main: Test commit	📦 Push to team/project testuser pushed 1 commit(s) to refs/heads/main: Test commit

How to connect GitLab

Step 1: Create an Integration

Go to your organization’s Integrations page.
Click Add Integration and select GitLab.
You’ll receive a unique Webhook URL. Copy it.

Step 2: Add the Webhook in GitLab

In your GitLab project (or group), go to Settings → Webhooks.
Click Add new webhook.
Paste your Hookfire webhook URL into the URL field.
Under Trigger, select the events you want (Push events, Merge request events, Issues events, etc.).
Set up one of the two ways GitLab proves a delivery is real (see step 3), then click Add webhook.

Step 3: Signing Token or Secret Token (recommended)

GitLab offers two options, and Hookfire checks either one.

Signing token (GitLab 19.0 and later, recommended by GitLab): click Generate signing token and copy it. It starts with whsec_ and is shown only once.
Secret token (older option): type a secret of your own into the Secret token field and copy it.

Go back to your Hookfire integration page and paste the token into the Signing Secret field. With a signing token, Hookfire checks the webhook-signature header GitLab adds to each delivery. With a secret token, it compares the X-Gitlab-Token header.

If you move from a secret token to a signing token, you can keep both on the GitLab side for a while. Paste whichever one you want Hookfire to check.

Step 4: Subscribe to Events

On your Hookfire integration page, toggle on the events you want to receive push notifications for.

Step 5: Test

Click the Test button on your integration page, or use GitLab’s Test button next to the webhook in the settings page.

Supported Events

Event	Description
`Push Hook`	Code was pushed to a branch
`Tag Push Hook`	A tag was pushed
`Merge Request Hook`	A merge request was opened, updated, or merged
`Issue Hook`	An issue was opened or updated
`Note Hook`	A comment was added
`Pipeline Hook`	A CI/CD pipeline changed status
`Job Hook`	A CI/CD job changed status
`Release Hook`	A release was created
`Wiki Page Hook`	A wiki page was created or updated

GitLab