• Group webhooks
• Configure a webhook in GitLab
• Mask sensitive portions of webhook URLs
• Configure your webhook receiver endpoint
• Failing webhooks
  • Re-enable disabled webhooks
• Test a webhook
• Create an example webhook receiver
• Validate payloads by using a secret token
• Filter push events by branch
• How image URLs are displayed in the webhook body
• Events
• Delivery headers
• Develop webhooks
  • Public webhook inspection and testing tools
  • GitLab Development Kit (GDK)
  • Recently triggered webhook payloads in GitLab settings
• Troubleshooting
  • Unable to get local issuer certificate
  • Webhook fails or multiple webhook requests are triggered
  • Webhook is not triggered

Webhooks

Webhooks are custom HTTP callbacks that you define. They are usually triggered by an event, such as pushing code to a repository or posting a comment on an issue. When the event occurs, the source app makes an HTTP request to the URI configured for the webhook. The action to take may be anything. For example, you can use webhooks to:

• Trigger continuous integration (CI) jobs, update external issue trackers, update a backup mirror, or deploy to your production server.
• Send a notification to Slack every time a job fails.
• Integrate with Twilio to be notified via SMS every time an issue is created for a specific project or group in GitLab.
• Automatically assign labels to merge requests.

You can configure your GitLab project or group to trigger a percent-encoded webhook URL when an event occurs. For example, when new code is pushed or a new issue is created. The webhook listens for specific events and GitLab sends a POST request with data to the webhook URL.

Usually, you set up your own webhook receiver to receive information from GitLab and send it to another app, according to your requirements. We have a built-in receiver for sending Slack notifications per project.

GitLab.com enforces webhook limits, including:

• The maximum number of webhooks and their size, both per project and per group.
• The number of webhook calls per minute.

Group webhooks

You can configure a group webhook, which is triggered by events that occur across all projects in the group and its subgroups. If you configure identical webhooks in a group and a project, they are both triggered by an event in the project.

Group webhooks can also be configured to listen for events that are specific to a group, including:

• Group member events
• Subgroup events

Configure a webhook in GitLab

To configure a webhook for a project or group:

1. In your project or group, on the left sidebar, select Settings > Webhooks.
2. Select Add new webhook.
3. In URL, enter the URL of the webhook endpoint. The URL must be percent-encoded if it contains one or more special characters.
4. In Secret token, enter the secret token to validate payloads.
5. In the Trigger section, select the events to trigger the webhook.
6. Optional. Clear the Enable SSL verification checkbox to disable SSL verification.
7. Select Add webhook.

Mask sensitive portions of webhook URLs

You can define and mask sensitive portions of webhook URLs and replace them with configured values any number of times when webhooks are executed. Sensitive portions do not get logged and are encrypted at rest in the database.

To mask sensitive portions of the webhook URL:

1. In your project or group, on the left sidebar, select Settings > Webhooks.
2. In URL, enter the full webhook URL.
3. Select Mask portions of URL.
4. In Sensitive portion of URL, enter the portion you want to mask.
5. In How it looks in the UI, enter the masking value.

To interpolate sensitive portions for each webhook, use url_variables. For example, if a webhook has the following URL:

https://{subdomain}.example.com/{path}?key={value}

You must define the following variables:

• subdomain
• path
• value

Variable names can contain only lowercase letters (a-z), numbers (0-9), or underscores (_). You can define URL variables directly using the REST API.

Configure your webhook receiver endpoint

Webhook receiver endpoints should be fast and stable. Slow and unstable receivers can be disabled automatically to ensure system reliability. Webhooks that fail might lead to duplicate events.

Endpoints should follow these best practices:

• Respond quickly with a 200 or 201 status response. Avoid any significant processing of webhooks in the same request. Instead, implement a queue to handle webhooks after they are received. The timeout limit for webhooks is 10 seconds on GitLab.com.
• Be prepared to handle duplicate events. In some circumstances, the same event may be sent twice. To mitigate this issue, ensure your endpoint is reliably fast and stable.
• Keep the response headers and body minimal. GitLab does not examine the response headers or body. GitLab stores them so you can examine them later in the logs to help diagnose problems. You should limit the number and size of headers returned. You can also respond to the webhook request with an empty body.
• Only return client error status responses (in the 4xx range) to indicate that the webhook has been misconfigured. Responses in this range can lead to your webhooks being automatically disabled. For example, if your receiver only supports push events, you can return 400 if sent an issue payload, as that is an indication that the hook has been set up incorrectly. Alternatively, you can ignore unrecognized event payloads.
• Never return 500 server error status responses if the event has been handled as this can cause the webhook to be temporarily disabled.
• Invalid HTTP responses are treated as failed requests.

Failing webhooks

Project or group webhooks that fail four consecutive times are automatically disabled.

Project or group webhooks that return response codes in the 5xx range are understood to be failing intermittently and are temporarily disabled. These webhooks are initially disabled for one minute, which is extended on each subsequent failure up to a maximum of 24 hours.

Project or group webhooks that return response codes in the 4xx range are understood to be misconfigured and are permanently disabled until you manually re-enable the webhooks yourself.

Re-enable disabled webhooks

If a webhook is failing, a banner displays at the top of the edit page explaining why the webhook is disabled and when it is automatically re-enabled. For example:

In the case of a failed webhook, an error banner is displayed:

To re-enable a failing or failed webhook, send a test request. If the test request succeeds, the webhook is re-enabled.

Test a webhook

You can trigger a webhook manually, to ensure it’s working properly. You can also send a test request to re-enable a disabled webhook.

For example, to test push events, your project should have at least one commit. The webhook uses this commit in the webhook.

Prerequisites:

• To test project webhooks, you must have at least the Maintainer role for the project.
• To test group webhooks, you must have the Owner role for the group.

To test a webhook:

1. In your project or group, on the left sidebar, select Settings > Webhooks.
2. Scroll down to the list of configured webhooks.
3. From the Test dropdown list, select the type of event to test.

You can also test a webhook from its edit page.

Create an example webhook receiver

To test how GitLab webhooks work, you can use an echo script running in a console session. For the following script to work you must have Ruby installed.

1. Save the following file as print_http_body.rb:

   require 'webrick'
   
   server = WEBrick::HTTPServer.new(:Port => ARGV.first)
   server.mount_proc '/' do |req, res|
     puts req.body
   end
   
   trap 'INT' do
     server.shutdown
   end
   server.start
   

2. Choose an unused port (for example, 8000) and start the script:

   ruby print_http_body.rb 8000
   

3. In GitLab, configure the webhook and add your receiver’s URL, for example, http://receiver.example.com:8000/.

4. Select Test. You should see something like this in the console:

   {"before":"077a85dd266e6f3573ef7e9ef8ce3343ad659c4e","after":"95cd4a99e93bc4bbabacfa2cd10e6725b1403c60",<SNIP>}
   example.com - - [14/May/2014:07:45:26 EDT] "POST / HTTP/1.1" 200 0
   - -> /
   

Validate payloads by using a secret token

You can specify a secret token to validate received payloads. The token is sent with the hook request in the X-Gitlab-Token HTTP header. Your webhook endpoint can check the token to verify that the request is legitimate.

Filter push events by branch

You can filter push events by branch. Use one of the following options to filter which push events are sent to your webhook endpoint:

• All branches: push events from all branches.
• Wildcard pattern: push events from a branch that matches a wildcard pattern (for example, *-stable or production/*).
• Regular expression: push events from a branch that matches a regular expression (for example, ^(feature|hotfix)/).

To configure branch filtering for a project or group, see Configure a webhook in GitLab.

How image URLs are displayed in the webhook body

Relative image references are rewritten to use an absolute URL in the body of a webhook. For example, if an image, merge request, comment, or wiki page includes the following image reference:

![image](/uploads/$sha/image.png)

If:

• GitLab is installed at gitlab.example.com.
• The project is at example-group/example-project.

The reference is rewritten in the webhook body as follows:

![image](https://gitlab.example.com/example-group/example-project/uploads/$sha/image.png)

Image URLs are not rewritten if:

• They already point to HTTP, HTTPS, or protocol-relative URLs.
• They use advanced Markdown features like link labels.

Events

For more information about supported events for webhooks, see webhook events.

Delivery headers

Webhook requests to your endpoint include the following headers:

Develop webhooks

If you don’t have an existing HTTPS endpoint or URL for your webhook setup, you must deploy one on a server. This HTTPS endpoint is used in configuration. To develop against GitLab webhooks and capture the payloads, you can use:

• Public webhook inspection and testing tools
• The GitLab Development Kit (GDK)
• Recently triggered webhook payloads in GitLab settings

Public webhook inspection and testing tools

You can use public tools to inspect and test webhook payloads. These tools act as catch-all endpoints for HTTP requests and respond with a 200 OK HTTP status code. You can use these payloads to develop your webhook services.

You should exercise caution when using these tools as you might be sending sensitive data to external tools. You should use test tokens with these tools and rotate any secrets inadvertently sent to a third party.

These public tools include:

• Beeceptor to create a temporary HTTPS endpoint and inspect incoming payloads
• Webhook.site to review incoming payloads
• Webhook Tester to inspect and debug incoming payloads

GitLab Development Kit (GDK)

For a safer development environment, you can use the GitLab Development Kit (GDK) to develop against GitLab webhooks locally. With the GDK, you can send webhooks from your local GitLab instance to a webhook receiver running locally on your machine. To use this approach, you must install and configure the GDK.

Recently triggered webhook payloads in GitLab settings

You can review recently triggered webhook payloads in GitLab settings. For each webhook event, a detail page exists with information about the data GitLab sends and receives from the webhook endpoint.

Troubleshooting

GitLab records the history of each webhook request. You can view requests made in the last 2 days in the Recent events table.

Prerequisites:

• To troubleshoot project webhooks, you must have at least the Maintainer role for the project.
• To troubleshoot group webhooks, you must have the Owner role for the group.

To view the table:

1. In your project or group, on the left sidebar, select Settings > Webhooks.
2. Scroll down to the webhooks.

3. Each failing webhook has a badge listing it as:

   • Failed to connect if it’s misconfigured and must be manually re-enabled.
   • Fails to connect if it’s temporarily disabled and is automatically re-enabled after the timeout limit has elapsed.

   

4. Select Edit for the webhook you want to view.

The table includes the following details about each request:

• HTTP status code (green for 200-299 codes, red for the others, and internal error for failed deliveries)
• Triggered event
• Elapsed time of the request
• Relative time for when the request was made

Each webhook event has a corresponding Details page. This page details the data that GitLab sent (request headers and body) and received (response headers and body). To view the Details page, select View details for the webhook event.

To repeat the delivery with the same data, select Resend Request.

Unable to get local issuer certificate

When SSL verification is enabled, you might get an error that GitLab cannot verify the SSL certificate of the webhook endpoint. Typically, this error occurs because the root certificate isn’t issued by a trusted certification authority as determined by CAcert.org.

If that is not the case, consider using SSL Checker to identify faults. Missing intermediate certificates are common causes of verification failure.

Webhook fails or multiple webhook requests are triggered

If you’re receiving multiple webhook requests, the webhook might have timed out.

GitLab expects a response in 10 seconds. On self-managed GitLab instances, you can change the webhook timeout limit.

Webhook is not triggered

If a webhook is not triggered, check that:

• The webhook was not automatically disabled.
• The GitLab instance is not in Silent Mode.