What are GitLab webhooks?
GitLab webhooks send an HTTP request when an event occurs in your GitLab account. Teams use them to react to pushes, merge requests, issues, and pipeline activity without repeatedly polling an API. Hookflo gives each delivery a searchable record and can notify the right team when an event arrives or signature verification fails.
Events to monitor
Choose the event types that matter in your GitLab configuration. Common examples include:
- Push Hook
- Merge Request Hook
- Pipeline Hook
Connect GitLab to Slack or email
- Create a webhook in Hookflo and select GitLab.
- Copy the unique Hookflo webhook URL.
- In GitLab project or group → Settings → Webhooks, add the Hookflo URL and choose the event types to send.
- Use the Secret token configured for the GitLab webhook. Hookflo currently validates the X-Gitlab-Token header for this integration.
- Save the endpoint, send a test event, and choose Slack or email for notifications.
Verify signatures and debug delivery issues
The secret token is configured on each GitLab webhook. Confirm the same token is saved in Hookflo and that the event is enabled.
When a delivery fails, check the selected event, destination URL, and provider-specific signing secret first. Hookflo keeps the event payload and verification result together so the issue is easier to diagnose.
Read GitLab webhook documentationHow can I get alerts for GitLab merge requests?
Add your Hookflo URL to GitLab Webhooks, enable Merge Request events, set a Secret token, and save that same token in the Hookflo GitLab configuration.