DevOps Webhook Configuration - Troubleshooting Guide .ns-kb-css-body-editor-container { p {font-size: 12pt; font-family: Lato; color: #000000;} h2 {font-size: 24pt; font-family: Lato; color: black;} h3 {font-size: 18pt; font-family: Lato; color: black;} h4 {font-size: 14pt; font-family: Lato; color: black;} a {font-size: 12pt; font-family: Lato; color: #00718F;} a:hover {color: #024F69;} ul, li, ol {font-size: 12pt; font-family: Lato; color: #1F2937;} code {font-family: Menlo, Consolas, monospace; font-size: 10.5pt; background-color: #F2F4F7; color: #1F2937; padding: 1px 5px; border-radius: 3px;} } ServiceNow DevOps Webhook Configuration Troubleshooting Knowledge Base Covers: GitHub | GitLab | Jenkins | Azure DevOps | Jira | BitBucket | Argo CD | Rally | Harness Keywords Product: ServiceNow DevOps Change Velocity (DCV), ServiceNow DevOps, DevOps integration, DevOps Workspace, DevOps data model, DevOps webhook, DevOps tool integration Tools: Azure DevOps integration, Azure DevOps service hooks, GitHub webhook, GitHub Actions, GitLab webhook, Jenkins plugin, Jira webhook, Bitbucket webhook, Argo CD webhook, Rally webhook, Harness webhook Symptoms: webhook issue, webhook not working, webhook not triggering, inbound events not received, duplicate inbound events, sub-events missing, pull request events missing, tool needs attention, webhook configuration in progress, webhook 401 Unauthorized, webhook 403 Forbidden after upgrade, host parameter is null Configuration: Auto Configure with Existing Token, Auto Configure with New Token, webhook URL, tool ID, sn_devops_inbound_event, sn_devops_processed_inbound_event, sn_devops_tool, IP Address Access Control, sys_connection ACL, sn_devops.tool_owner, devops.system user, sn_devops.webhook_check_timeout Troubleshooting Webhook Configuration Issues Are you not receiving inbound events from your DevOps tools? Webhooks not triggering? This guide provides step-by-step verification to diagnose and resolve webhook configuration issues. Note: Before troubleshooting webhooks, ensure your tool is successfully onboarded and connected to ServiceNow. If your tool is not connected or has onboarding issues, refer to the Tool Onboarding Troubleshooting guide first. Reference: KB2683163 - DevOps Tool Onboarding Troubleshooting Guide Important: Follow these steps sequentially. Each step builds on the previous one to systematically identify where the issue lies. Step 1: Verify Basic Configuration Start here! Before troubleshooting webhooks, ensure your tool is connected and has discovered all necessary resources (pipelines, repositories, projects). Check: Tool connection status, credentials, permissions, and resource discovery. → Go to Step 1: Verify Basic Configuration Step 2: Verify Webhook Configuration from Tool Side Tool connected but still no events? Time to check the webhook configuration on the external tool side (GitHub, Jenkins, Azure DevOps, etc.). Check: Webhook URLs, tool IDs, event subscriptions, and duplicate webhooks. → Go to Step 2: Verify Webhook Configuration from Tool Side Step 3: Webhooks Exist But No Events Received Webhooks are configured correctly but ServiceNow still isn't receiving events? Let's debug deeper. Check: Token validity, webhook delivery history, HTTP response codes, and authentication issues. → Go to Step 3: Webhooks Exist But No Events Received Step 4: Tool-Specific Configuration & Limitations Each tool has unique webhook configuration requirements and limitations. Review tool-specific considerations. Check: Tool-specific limitations (Jenkins max 10 webhooks), token requirements, and configuration nuances. → Go to Step 4: Tool-Level Configuration & Limitations Common Webhook Issues Review the most frequently encountered webhook problems and their solutions. Includes: Duplicate events, missing sub-events, missing pull requests, tool throttling. → Go to Common Webhook Issues Need Official Documentation? Jump directly to ServiceNow's official webhook configuration guides for all supported tools. → Go to Official Documentation Links Step 5: Contact ServiceNow Technical Support Tried everything and still stuck? No worries — even the best of us need backup sometimes. Open a case with ServiceNow Technical Support through the Now Support portal. Two heads are always better than one. Pro tip: Include screenshots, error messages, tool sys_id, webhook URLs, and outbound HTTP logs. The more details you provide, the faster we can help you get back to shipping code. Table of Contents 1. Verify Basic Configuration Tool Connection StatusPermission CheckVerify Pipelines/Plans/Repositories/Projects are DiscoveredVerify Webhook Configuration in ServiceNow Instance 2. Verify Webhook Configuration from Tool Server Side Verify Webhook from Tool SideWebhook URL Format 3. Webhooks Exist But No Events Received Verify Webhook ConfigurationVerify TokenCheck Delivery History 4. Tool-Level Webhook Configuration & Limitations Jenkins ConfigurationAzure DevOps ConfigurationGitHub ConfigurationGitLab Configuration Common Webhook Issues Webhook Configuration in ProgressDuplicate Inbound EventsSub-Events Are MissingPull Request Events Are Missing Known Issues Webhook "Needs Attention" Warning with Working IntegrationWebhook 403 Access Errors After Instance UpgradeWebhook Auto-Configuration Fails - ACL Permission MissingWebhooks Sent But No Inbound Events Processed 5. Contact ServiceNow Technical SupportServiceNow Official Documentation Pro Tip: These steps are designed for step-by-step verification in case webhooks are not configured or not working properly. Follow them in order for the most efficient troubleshooting experience. Webhook Overview What is a Webhook? A webhook is an automated, event-driven mechanism for applications to communicate with each other over HTTP in real-time. In the context of ServiceNow DevOps Change Velocity, webhooks act as the crucial link for integrating third-party DevOps tools (like Jenkins, GitHub, or Jira) by sending instant notifications to ServiceNow whenever specific events occur in those tools. How a Webhook Works Registration/Configuration: A unique URL (endpoint) provided by the receiving application (ServiceNow) is registered in the source application's (e.g., GitHub) settings. This tells the source application where to send notifications.Event Trigger: A specific event occurs in the source tool, such as a code commit, a pull request being opened, or a CI/CD pipeline run completing.HTTP POST Request: The source application automatically sends an HTTP POST request to the configured ServiceNow webhook URL. This request includes a payload, usually in JSON or XML format, containing data and details about the event that just occurred.Receipt and Action: The ServiceNow instance, which is constantly listening for requests at that URL, receives the payload. A pre-configured script or business rule processes this data and triggers specific actions or workflows within ServiceNow. DevOps Standard Process: Before clicking the configure button, ensure the tool is created and connected successfully, and has discovered all necessary details (like projects, pipelines, repositories, and plans) before processing. Step 1: Verify Basic Configuration 1. Verify Tool Connection Status Table: sn_devops_tool Checks: Navigate to DevOps Workspace → ToolsFind the orchestration toolVerify Connection State = ConnectedVerify Overall Status = Connected (not Disconnected, Needs Attention, or Throttled)Check Valid Credentials = trueVerify Last Permission Check Result = Full permissions Permission Check Log in to ServiceNow instanceGo to Tools → Open your toolClick Check Permission and make sure you have all required permissionsIn case you are missing any permission, get credentials with required permissions, update credentials, and check permissions again Reference: For minimum required permissions for all DevOps tools, see Tool Required Permissions 2. Verify Pipelines/Plans/Repositories/Projects are Discovered Tables: sn_devops_pipeline, sn_devops_repository, sn_devops_plan, sn_devops_project, sn_devops_artifact Note: ALL the tables may not be applicable for all tools. Based on the capability of the tool, we discover those items. Checks: Navigate to DevOps Workspace → Pipelines/Repositories/Plans/ProjectsSearch for your pipeline/repositories/plan using name or native IDVerify pipeline/repositories/plan record exists (discovered)Verify Tool reference points to correct toolCheck Active = true Issue: If pipeline/repository/plan/artifact is not discovered, trigger a discovery from tool record or check if resource tracking is disabled. Note: Ensure there are no duplicate records for the same resource. Duplicates can cause processing issues. 3. Verify the Webhook Configuration in ServiceNow Instance Symptoms: Tool shows "needs attention" notification, webhooks not configured Root Cause: Webhooks are not automatically configured for all repositories/pipelines/projects/plans, especially those in "Unconfigured" state Resolution: Navigate to the tool record in ServiceNowGo to the "Repositories/Pipelines/Plans/Projects" tabFor unconfigured items, select "Auto Configure with Existing Token" from the "Configure" dropdown Note: "Auto Configure with New Token" only reconfigures repositories/pipelines/plans that are already in "Configured" state. Use "Auto Configure with Existing Token" for unconfigured items. Known Issue: If your tool shows "needs attention" notification but the integration is working correctly and events are being received successfully, refer to Webhook "Needs Attention" Warning with Working Integration in the Known Issues section below. Step 2: Verify Webhook Configuration from Tool Server Side Are you not receiving inbound events (like commit, pull request, pipeline details), even after configuring the webhook? There is a chance of webhook configuration issue. Follow the steps below. Verify Webhook from Tool Side Navigate into the tool (Azure DevOps, Jenkins, GitHub, GitLab, etc.) with your credentialsBased on the tool, check where the service hooks/webhooks/configurations are located and verify the webhooks that were createdThe webhooks will be created with instance URL, capability type, and tool ID. In the case of Azure DevOps, we will also have all project sys IDs Webhook URL Format: https://<your-instance_id>.service-now.com/api/sn_devops/v2/devops/tool/CapabilityType?toolId=<tool_id> Note: It will create separate webhooks for each capability type (except for few tools like Jenkins where only one configuration is created). Most tools create separate webhooks per capability type (e.g., one for commits, one for pull requests, one for pipeline runs). However, Jenkins uses a single plugin configuration that handles all events through one endpoint. Warning: If multiple webhooks are created for the same capability type and same tool subscribing to the same events, it will cause issues since it will send the same event multiple times for the same data. Step 3: Webhooks Exist But No Events Received Problem: No inbound events found in sn_devops_inbound_event table for the build. Important: Verify in sn_devops_processed_inbound_event table also, as processed events are moved to this table hourly. Debugging Steps 1. Verify Webhook Configuration Navigate to tool and check webhook sectionVerify webhook to ensure it's configured as per documentationCheck if webhook is active/enabled 2. Verify Token Verify if the token set to webhook is correctTo verify this, you can use test webhook feature or check delivery history 3. Check Delivery History In orchestration tool, navigate to webhook section and select the webhook and check delivery historyCheck for failed deliveries or HTTP errorsVerify response codes (look for 200/201 success codes)If response is 401: It means token is invalid - please reconfigure or update token manually Resolution: It's a configuration issue. Reconfigure webhook automatically or manually by following the steps mentioned in the official document. → Go to Documentation section Step 4: Tool-Level Webhook Configuration & Limitations Jenkins Configuration Type: Plugin-based (not webhook) Key Limitation: Maximum of 10 ServiceNow DevOps configurations Important Note: Jenkins uses a single plugin configuration that handles all events through one endpoint, unlike other tools that create separate webhooks per capability type. Sub-Events Handling: All sub-events (software quality, security, test summaries, and test results) will be sent to the default configuration if configuration details are not specified in the custom task, which are auto-configured during tool configuration. Azure DevOps Configuration Type: Service Hooks (webhooks) Key Requirement: Appropriate permissions for creating service hooks and service connections based on the credential type you choose (basic authentication, classic token, or OAuth) Important Note: Creates separate webhooks for each event type per project (Build completed, Code pushed, Release created, Work item updates, etc.). Requires project ID in webhook URL. Azure DevOps Limitation: If you create an Azure DevOps tool with a custom defined access level and reconfigure that tool due to a change in your onboarding user credentials, the existing service hooks for the created version and the version deployment will not be updated. Instead, two new service hooks are created with new configuration details. To avoid duplication of these service hooks, you should create the tool with full access level. Sub-Events Handling: Sub-events (test summaries, SonarQube results, packages, artifacts, change callbacks) are sent based on the instance service connection specified in the custom task in your pipeline. The service connection contains instance and project details, which are auto-configured during tool configuration. GitHub Configuration Type: Webhooks Key Requirement: Appropriate permissions for creating webhooks based on the credential type you choose (basic authentication, classic token, OAuth) Important Note: GitHub supports both auto-configuration and manual configuration at repository level. GitHub Actions workflows use secrets for sub-events. Auto-Configuration Limitation: Auto-configure at tool level only configures the repositories that are already configured. Sub-Events Handling: All sub-events (test summaries, SonarQube results, packages, artifacts, change callbacks) are sent based on the secrets defined in the custom task workflows. You need to manually create secrets in the repository: Navigate to Repository > Settings > Secrets and variables > ActionsCreate the following secrets: SN_INSTANCE_URL, SN_ORCHESTRATION_TOOL_ID, SN_DEVOPS_INTEGRATION_TOKENImportant: These secrets are NOT auto-configured during tool configuration and must be configured manually GitLab Configuration Type: Webhooks Key Requirement: Appropriate permissions for creating webhooks based on the credential type you choose (basic authentication, classic token) Important Note: GitLab uses ServiceNow Custom Actions with a generic Docker container image to collect data related to change request creation, SonarQube scan, artifact registration, and package registration in your pipeline. Configure webhooks in GitLab project Settings > Webhooks. Sub-Events Handling: All sub-events (test summaries, SonarQube results, packages, artifacts, change callbacks) are sent using Docker container with environment variables. You need to manually configure environment variables in your GitLab project: Navigate to GitLab Project > Settings > CI/CD > VariablesCreate the following environment variables: SNOW_TOKEN (masked variable), SNOW_TOOLID, SNOW_URLImportant: These environment variables are NOT auto-configured during tool configuration and must be configured manuallyValues are available in the "Configure webhooks manually" popup on the tool registration page For More Information: For more details and other tool-specific webhook configuration steps (Jira, BitBucket, Argo CD, Rally, Harness), check the official documentation. → Go to ServiceNow Official Documentation Most Common Webhook Issues 1. Webhook Configuration in Progress: How to Check Status and Errors Problem: When you click on "Configure" for single or multiple projects/repositories/pipelines, webhook configuration is taking time and showing "in progress" state. Cause: When you click on the configure button, multiple API calls are made to verify and create/update the webhooks. This process may take some time depending on the number of webhooks being configured. How to Check Status: Check Webhook Configuration Progress: Navigate to All > DevOps > LogsReview the webhook configuration logs to see the progress statusLook for any error messages or warnings in the logs Check API Call Status: Enable HTTP outbound logs: System Logs > Outbound HTTP RequestsFilter by the tool name or time frameReview the HTTP response codes to identify any failuresLook for 200/201 success codes or error codes like 401, 403, 404, 500 Wait for Process Completion: Allow the configuration process to complete. Large configurations may take several minutes. Pro Tip: If the configuration remains stuck for an extended period (more than 15 minutes), check the logs for specific errors and verify your credentials and permissions are still valid. 2. Duplicate Inbound Events Problem: Same inbound event is received multiple times for the same tool. Cause: Multiple webhooks configured for the same capability type and events. Resolution Steps: Log into the respective tool (Azure DevOps, GitHub, GitLab, Jenkins, etc.)Navigate to the webhook configuration section (e.g., Settings > Webhooks for GitHub/GitLab, Service Hooks for Azure DevOps)Verify and check all configured webhooksReview recent delivery history for each webhookIdentify and remove duplicate webhooks that subscribe to the same eventsKeep only one webhook per capability type per tool for the same events, based on instance details, tool ID, and other configuration details 3. Sub-Events (Software Quality, Test Summaries, Security, Artifact, or Package) or Callback Registration Are Missing Problem: Some inbound events are not being received even though we are getting the main events (code, pull request, pipeline). Cause: Configuration details in the tool are not defined correctly, or credentials/tokens have expired in tools (Azure DevOps, GitHub, Jenkins, GitLab, and so on). Resolution Steps: Log into the respective tool (Azure DevOps, GitHub, GitLab, Jenkins, etc.)Verify the pipeline and custom task you defined in your workflowCheck the configuration details specified in the custom task: Tool ID (ServiceNow tool sys_id)Instance URL (ServiceNow instance URL)Token/credentials Verify those configuration details match the tool record in ServiceNowTool-Specific Checks: GitHub: Check secrets and values in Repository > Settings > Secrets and variables > Actions (SN_INSTANCE_URL, SN_ORCHESTRATION_TOOL_ID, SN_DEVOPS_INTEGRATION_TOKEN)GitLab: Check environment variables in Project > Settings > CI/CD > Variables (SNOW_TOKEN, SNOW_TOOLID, SNOW_URL)Azure DevOps: Check service connection mentioned in the Azure DevOps task and verify it contains correct instance and project detailsJenkins: Verify the default configuration is active and contains correct instance URL, tool ID, and credentials For more tool-specific details: Refer to the ServiceNow Official Documentation section for comprehensive configuration guides for all supported tools. 4. Pull Request Events Are Missing Problem: Pull request-based inbound events are not being received. Cause: Webhook not configured for pull request events or permissions issue. Resolution Steps: Log into the respective tool (Azure DevOps, GitHub, GitLab, etc.)Navigate to webhook configuration sectionCheck webhook event subscriptions and verify pull request events are enabledVerify token permissions include pull request access Important: For some tools (like Azure DevOps), you need to enable pull request tracking and webhooks in the DevOps properties. Known Issue: Webhook 403 Access Errors After Instance Upgrade Issue Description: After instance upgrades, external tool webhook connections may fail with 403 Forbidden errors. Webhook events cannot reach ServiceNow, and webhook delivery fails. Symptoms: 403 access errors when external tools attempt to send webhook eventsWebhook events fail to reach ServiceNowLoad balancer logs show IP address blockingConfiguration test shows success, but actual webhook delivery fails Root Cause: Instance upgrades may introduce IP address blocking for external integrations. Webhook calls from external tool IP addresses are blocked unless whitelisted in ServiceNow. Resolution Steps: Identify the IP address: Check load balancer logs and transaction records to find the external tool IP address being blockedWhitelist the IP address: Navigate to System Security > IP Address Access Control in ServiceNowAdd the external tool IP address(es) to the whitelistCheck tool vendor documentation for current IP ranges (e.g., Azure DevOps, GitHub, GitLab) Verify Tool Secure Token: Ensure the secret token is not expiredTest webhook configuration: From the external tool, test the webhook deliveryCheck system logs: Verify 403 errors are resolved in load balancer and outbound HTTP logs Prevention & Best Practices: Review IP access control settings after instance upgradesMonitor platform release notes for changes to IP handling and integration securityMaintain documentation of whitelisted IP addresses for all external integrationsTest webhook delivery after upgrades before deploying to productionIf issue persists after whitelisting, escalate to platform team for IP blocking behavior review Known Issue: Webhook Auto-Configuration Fails - ACL Permission Missing Issue Description: Tool has valid credentials and full permissions, but webhook reports "Needs attention". When using "Auto Configure with New Token", a new token is generated but auto-configuration fails. Manual configuration may be required. Symptoms: Webhook status shows "Needs attention" despite valid credentials and permissionsAuto Configure with New Token generates token but fails to complete configurationError in logs: Request not sent to uri=... java.lang.IllegalArgumentException: host parameter is nullAuthentication failures during webhook auto-configuration attempts Root Cause: Missing role permissions for Access Control (ACL) record. The sys_connection.* read operation on the Connection table may lack the sn_devops.tool_owner role in Required Roles conditions, causing authentication failures during auto-configuration. Resolution Steps: Check ACL Configuration: Navigate to System Security > Access Control (ACL)Search for table: sys_connectionFind the read operation ACL record Verify Required Roles: Edit the ACL record for sys_connection.* read operationsEnsure sn_devops.tool_owner is included in Required Roles conditionsAdd the role if missing and save the ACL record Test Auto-Configuration: Retry Auto Configure with New Token from the tool recordVerify webhook status changes from "Needs attention" to configuredCheck system logs to confirm absence of IllegalArgumentException errors Verify Webhook Delivery: Trigger an event from the external tool and confirm it's received in ServiceNow Prevention & Best Practices: Verify ACL configurations include all required DevOps roles during platform upgradesTest auto-configuration features in non-production environments firstMonitor system logs for IllegalArgumentException errors during webhook configurationReview and document ACL modifications for DevOps-related tables Known Issue: Webhooks Sent But No Inbound Events Processed Issue Description: External tools successfully send webhook events to ServiceNow, but events are not appearing in inbound event tables and are not being processed. Work items, pipelines, and other resources are not synced. Symptoms: External tools show successful webhook delivery (200 OK response)No entries appear in sn_devops_inbound_event tableWork items, pipelines, and builds are not synced to ServiceNowNo processing errors visible in standard logsWebhook configuration appears correct Root Cause: The devops.system user has insufficient roles to process inbound events. Required roles may have been accidentally deleted or not properly configured, preventing events from being moved to the inbound event table. Resolution Steps: Check devops.system User Roles: Navigate to User Administration > UsersSearch for user: devops.systemReview the Roles tab and compare with a working environment (UAT/Dev) Restore Missing Roles: Add all required DevOps roles to the devops.system userTypical required roles include: sn_devops.admin, sn_devops.integration_user, and related rolesCompare with reference environment to ensure all roles are present Test Event Processing: Trigger a webhook event from the external toolCheck sn_devops_inbound_event table for new entriesVerify events are being processed correctly Prevention & Best Practices: Restrict access to devops.system user to prevent accidental role deletionDocument the complete list of required roles for the devops.system userImplement role validation checks in deployment automationRegularly audit critical system user roles as part of maintenance proceduresCreate alerts for missing roles on critical integration users Known Issue: Webhook "Needs Attention" Warning with Working Integration Issue Description: Customers may see the warning message "This tool needs attention. Webhook is not configured correctly" in DevOps Change Velocity, even though the integration is working correctly and inbound events are being received. Symptoms: Webhook status intermittently changes between Configured and Needs AttentionIntegration appears healthyPipelines, commits, and builds are still processedRepositories show Unconfigured status in DevOps WorkspaceNo errors in inbound event tables Root Cause: This behavior occurs when one or more discovered repositories are in an Unconfigured state under the DevOps tool (Project → Repositories tab). ServiceNow performs proactive webhook validation checks to alert customers that some repositories are not configured for real-time notificationsIn large environments, webhook validation may exceed the default timeout threshold (5 seconds), causing the warning to appear intermittently Limitations / Known Behavior: Webhook validation is time-bound and may timeout in large environmentsDiscovered repositories are not automatically configured for real-time trackingThe warning is informational and does not indicate webhook failureStatus may fluctuate even when webhooks are correctly configuredReal-time notifications require repositories to be explicitly tracked Impact: No impact to existing integrationsNo data lossNo inbound event processing failureWarning can be safely ignored if real-time tracking is not required Resolution / Workaround: Option 1: Ignore the Warning If real-time notifications are not required for unconfigured repositories, no action is needed. Option 2: Configure Repositories for Real-Time Tracking Navigate to DevOps WorkspaceOpen the tool recordGo to Project → Repositories tabEnable the Track flag for required repositories(Optional) Change Configuration Status to Configured for visibility Option 3: Increase Webhook Timeout (Use with Caution) System property: sn_devops.webhook_check_timeoutDefault: 5 secondsWarning: Increasing this value may reduce warnings but can impact instance performance Step 5: Contact ServiceNow Technical Support Tried everything and still stuck? No worries — even the best of us need backup sometimes. Open a case with ServiceNow Technical Support through the Now Support portal. Two heads are always better than one. Pro tip: Include screenshots, error messages, tool sys_id, webhook URLs, and outbound HTTP logs. The more details you provide, the faster we can help you get back to shipping code. Information to Include in Your Case: Tool Information: Tool name, tool sys_id, tool type (GitHub, Jenkins, etc.)Webhook Details: Webhook URLs, capability types, event subscriptionsError Messages: Exact error messages from tool or ServiceNowScreenshots: Webhook configuration, delivery history, ServiceNow logsOutbound HTTP Logs: From System Logs → Outbound HTTP RequestsInbound Event Tables: Check sn_devops_inbound_event and sn_devops_processed_inbound_eventTimestamp: When the issue occurred ServiceNow Official Documentation Configure webhooks in Azure DevOps manuallyConfigure webhooks for GitHub manuallyConfigure webhooks in GitLabConfigure Jenkins pluginConfigure webhooks for Jira manuallyConfigure webhooks in BitBucket manuallyConfigure webhooks in Argo CD manuallyConfigure webhooks for Rally manuallyConfigure webhooks in Harness manuallyImport-based evidence collection for orchestration capability