Skip to main content
All CollectionsAPI and integrations
Setting up a GitLab Group Hook
Setting up a GitLab Group Hook

Have changes in GitLab sync back to follow-ups instantly

George Mabey avatar
Written by George Mabey
Updated over a week ago

We rely on a GitLab Group Hook to enable:

1️⃣ Syncing changes to follow-ups in GitLab back to incident.io

2️⃣ Linking merge requests to incidents automatically when you mention the incident reference (e.g. INC-123) in a merge request.

3️⃣ Posting updates to merge requests in the incident channel, for example when a linked MR is merged.

🛠️ Setting up

You'll need a GitLab Group Owner to do this setup.

1️⃣ Find your secret token

Under Settings → Integrations → GitLab, you'll find a unique secret token. Copy this down - you'll need it to successfully configure the hook.

2️⃣ Create the hook

Within your top-level group, click Settings then Webhooks:

Then 'Add new webhook'.

For the URL use https://app.incident.io/webhooks/gitlab.

For the Secret token, paste in the secret token from the incident.io dashboard.

Under Trigger, select:

☑️ Issues events

☑️ Merge request events

Everything else can be left as the default. Click Add webhook.

3️⃣ Verify the connection

In Settings → Integrations → GitLab, you can see when the last webhook was received. Make a small change to an issue to trigger a webhook:

You're all set 🎉

Did this answer your question?