---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Configure webhooks in GitLab manually

# Configure webhooks in GitLab manually {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Configure webhooks in GitLab manually to send job, push, and issues notifications to the DevOps application.

## Before you begin

Role required:

* sn_devops.admin or sn_devops.tool_owner in DevOps Change Velocity
* Maintainer (or higher) for the GitLab projects.
{#configure-webhooks-in-gitlab__ul_jsm_tdk_51c}

## About this task

Create webhooks for the following two triggers in GitLab for every project you want to track.

* Push events (code capability)
* Job events (orchestration capability)
* Issues events (planning capability)
{#configure-webhooks-in-gitlab__ul_xvm_zd1_gmb}

You can also access manual configuration from the GitLab tool record in DevOps Change Velocity.

## Procedure

1. In GitLab, navigate to ProjectSettingsWebhooks and add a webhook.
2. In DevOps Change Velocity, choose Configure manually when configuring the tool instance to send data.  
   Note:  
   You can also access manual configuration from the GitLab tool record in DevOps Change Velocity. From the tool record, select ConfigureConfigure manually.
3. Copy the Webhook URL field from DevOps Change Velocity connection details for GitLab.  
   Note:  
   Select Copy in the appropriate field to copy the value to your clipboard. The field label changes to Copied, but you can copy multiple times.

4. Modify the copied Webhook URL to reflect your tool details, and paste the URL in GitLab.  
   For example:

   <kbd class="ph userinput">https://&lt;your instance&gt;.service-now.com/api/sn_devops/v2/devops/tool/{code | plan | artifact | orchestration | test | softwarequality }?toolId=&lt;your ToolId&gt;</kbd>
   1. Select one of the tool capabilities <kbd class="ph userinput">{code | plan | artifact | orchestration | test | softwarequality }</kbd> to match your tool.  
      For example:

      <kbd class="ph userinput">https://&lt;your instance&gt;.service-now.com/api/sn_devops/v2/devops/tool/code?toolId=&lt;your ToolId&gt;</kbd>
   2. Copy the modified Webhook URL to the URL field of the new webhook in your GitLab instance.
   {#configure-webhooks-in-gitlab__substeps_ibv_bwf_2yb}
5. Copy the Secret token field from the ServiceNow instance connection details for GitLab, and paste in the Secret Token field of the new webhook in your GitLab instance.  
   {#configure-webhooks-in-gitlab__table_s3f_3wn_dyb__entry__2}

   | From DevOps Change Velocity | To GitLab |
   |-|-|
   | Webhook URL (modified) | URL |
   | Secret token | Secret Token |
   [Table 1. Copy field values]

   {#configure-webhooks-in-gitlab__table_s3f_3wn_dyb}
6. Select the check boxes for Push events, Tag push events, Comments, and Merge request events for coding capability events.  
7. Select Add webhook.
8. Repeat the procedure to create webhooks for planning and orchestration capability events in GitLab.  
   * For orchestration: Select the check boxes for Job events and Pipeline events.
   * For planning: Select the check boxes for Issues events and Confidential issues events.
   {#configure-webhooks-in-gitlab__ul_hlj_mvc_zcc}
9. Select Add webhook.  
   GitLab webhooks for DevOps Change Velocity integration:

{#configure-webhooks-in-gitlab__steps_gfv_y21_bxb}

*[\>]: and then