---
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


---

# Test webhooks manually

# Test webhooks manually {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read  
For tools including GitLab, Rally, Split.io, Jira, Bitbucket, and Argo CD, you have to test webhooks manually if there is any issue with the connection.

## GitLab {#test-wehooks-manually__section_vjt_jp1_3zb}

Role required:

* GitLab: GitLab admin privileges
* DevOps Change: sn_devops.admin or sn_devops.tool_owner
{#test-wehooks-manually__ul_cj2_cpb_3zb}  
To test webhooks manually in GitLab, you must:

1. Navigate to GitLab and select the project for which you want to test webhooks.
2. Navigate to SettingsWebhooks.

   When your project is configured in DevOps Change Velocity, webhooks are created for that project in GitLab. These webhooks are available under Project Hooks.

   For each project, two webhooks are created. One is for code events and the other for orchestration events.
3. To test a webhook, select Test and select Push events from the list.

   Note:  
   You can test for other events as well, for example Tag push events.  
   * If the webhook is configured correctly, you'll receive a success message. For example:![Success message.]()

   * If the webhook is configured incorrectly, you'll receive an error message. For example:

     To fix a webhook, you can try the following options:
     * Reconfigure the webhooks by selecting Configure from the project record page in DevOps Change Velocity. This reconfigures all the existing webhooks for the project.
     * Select Edit for the webhook and verify if the toolId is correct in the URL
       field. Verify if the Secret token is correct.

       You can find the correct values in the tool record page in DevOps Change Velocity.

     {#test-wehooks-manually__ul_qpy_f41_tyb}
   {#test-wehooks-manually__ul_aqk_qx1_3zb}
{#test-wehooks-manually__ol_xsj_ps1_3zb}

For detailed information about webhooks in GitLab, see [Webhooks](https://docs.gitlab.com/ee/user/project/integrations/webhooks.html).

## Rally {#test-wehooks-manually__section_dzx_rlb_3zb}

Role required:

* Rally: Rally admin privileges
* DevOps Change: sn_devops.admin or sn_devops.tool_owner
{#test-wehooks-manually__ul_enr_gpb_3zb}  
Rally doesn't provide an option to directly test for webhook connectivity. If you're not seeing Rally events in DevOps Change Velocity, you can try the following options:

* From your Rally instance, navigate to My SettingsSystem AdministrationExtensionsWebhooks.

  Check if there's a corresponding webhook created for your DevOps Change instance, and that it's Active.

* Reconfigure the webhook by selecting Configure from the project record page in DevOps Change Velocity. This reconfigures the existing webhook for the project.
{#test-wehooks-manually__ul_gjs_r4b_3zb}

For detailed information about webhooks in Rally, see [Manage Webhooks](https://techdocs.broadcom.com/us/en/ca-enterprise-software/valueops/rally/rally-help/administration/configure-your-subscription/manage-webhooks.html#:~:text=Webhooks%20are%20usually%20triggered%20by,to%20invoke%20behavior%20on%20another.).

## Split.io {#test-wehooks-manually__section_brr_ztb_3zb}

Role required:

* Split.io: Split.io admin privileges
* DevOps Change: sn_devops.admin or sn_devops.tool_owner
{#test-wehooks-manually__ul_crr_ztb_3zb}  
Split.io doesn't provide an option to directly test for webhook connectivity. If you're not seeing Split.io events in DevOps Change Velocity, you can try the following options:

* From your Split.io instance, navigate to Admin SettingsIntegration settingsIntegrations. Select the Configured tab, and select Edit for the ServiceNow DevOps application.

  Check if the ServiceNow DevOps application is configured correctly in Split.io. For details on configuring, see [Enable integration with ServiceNow DevOps in Split tool](https://servicenow-prod.fluidtopics.net/02_3JGZNjOOLav8i0XG_Og "Enable integration with ServiceNow DevOps in Split tool and restrict approvers to only the enabled integration for your environment.").
* Check if the status of the ServiceNow DevOps application is Active.

* Reconfigure the webhook by selecting Configure from the tool record page in DevOps Change Velocity. This reconfigures the existing webhook for the Split.io tool.
{#test-wehooks-manually__ul_drr_ztb_3zb}

You can also refer to [ServiceNow integration with Split.io](https://help.split.io/hc/en-us/articles/5524203735181-ServiceNow).

## Jira {#test-wehooks-manually__section_xyk_n1w_3zb}

Role required:

* Jira: Jira admin privileges
* DevOps Change: sn_devops.admin or sn_devops.tool_owner
{#test-wehooks-manually__ul_qmt_r1w_3zb}  
Jira doesn't provide an option to directly test for webhook connectivity. If you're not seeing Jira events in DevOps Change Velocity, you can try the following options:

* Navigate to:
  * For Jira Server navigate to AdministrationSystemWebHooks.
  * For Jira Cloud instance, navigate to SettingsSystemWebHooks.
  {#test-wehooks-manually__ul_cjh_sjp_y1c}

  Check if there's a corresponding webhook created for your DevOps Change instance.

* Select Edit for the webhook.  
  * Check if the status is Enabled.
  * Check if the Tool ID in the URL field is correct. The Tool ID is the value after ?toolId=.
  * Check if the secret token in the URL field is correct. Token value is at the end of the URL, after token=.
  {#test-wehooks-manually__ul_ug3_sfw_3zb}

  You can find the correct values of the Tool ID and Secret token in the tool record page in DevOps Change Velocity.

  For detailed information about webhooks in Jira, see [Webhooks](https://developer.atlassian.com/server/jira/platform/webhooks/).
* Reconfigure the webhook by selecting Configure from the tool record page in DevOps Change Velocity. This reconfigures the existing webhook for the Jira tool.  
  Note:  
  If you have connected your Jira tool using OAuth 2.0 based authentication, the webhooks are created for the OAuth 2.0 integration app in Jira when
  you configure automatically, whereas if you have connected using basic authentication, the webhooks are created for all your projects in Jira. If you choose to configure the
  webhooks manually for a Jira tool created using OAuth 2.0 based authentication, a duplicate webhook may get created.
{#test-wehooks-manually__ul_c4z_v1w_3zb}

## Bitbucket {#test-wehooks-manually__section_uch_p1w_3zb}

Role required:

* Bitbucket: Bitbucket admin privileges
* DevOps Change: sn_devops.admin or sn_devops.tool_owner
{#test-wehooks-manually__ul_yjw_r1w_3zb}  
Bitbucket doesn't provide an option to directly test for webhook connectivity. If you're not seeing Bitbucket events in DevOps Change Velocity, you can try the following options:

* Navigate to Bitbucket and select the repository for which you want to test webhooks. Navigate to Repository settingsWorkflowWebhooks.

  Check if there's a corresponding webhook created for your DevOps Change instance.

* Select Edit for the webhook.  
  * Check if the status is Active.
  * Check if the Tool ID in the URL field is correct. The Tool ID is the value after /event/.
  * Check if the secret token in the URL field is correct. Token value is at the end of the URL, after token=.
  {#test-wehooks-manually__ul_imc_2lw_3zb}

  You can find the correct values of the Tool ID and Secret token in the tool record page in DevOps Change Velocity.

  For detailed information about webhooks in Bitbucket, see [Manage webhooks](https://support.atlassian.com/bitbucket-cloud/docs/manage-webhooks/).
* Reconfigure the webhook by selecting Configure from the tool record page in DevOps Change Velocity. This reconfigures the existing webhook for the Bitbucket tool.
{#test-wehooks-manually__ul_gmc_2lw_3zb}

## Argo CD {#test-wehooks-manually__section_sbm_vbr_lzb}

Role required:

* Argo CD: Argo CD admin privileges
* DevOps Change: sn_devops.admin or sn_devops.tool_owner
{#test-wehooks-manually__ul_zvg_wbr_lzb}

Argo CD doesn't provide an option to directly test for webhook connectivity. To configure webhooks, see [Configure webhooks in Argo CD manually](https://servicenow-prod.fluidtopics.net/ihO28sIVXnl_HpvIlgPwQg "Configure webhooks in Argo CD to send sync notifications to the DevOps Change Velocity application.").

*[\>]: and then