Azure DevOps与ServiceNow双向集成：Webhook支持PATCH方法及工作项状态更新触发JSON推送的技术咨询

Let me walk you through practical solutions to your key questions based on hands-on experience with these platforms:

1. Azure DevOps Webhook HTTP Method Limitations & PATCH Workarounds #

You’re spot-on that out-of-the-box Azure DevOps Webhooks only support HTTP POST requests—there’s no native option to configure a Webhook to send PATCH directly. Here are two reliable workarounds to meet ServiceNow’s PATCH requirement:

• Use a middleware layer: Deploy an Azure Function, Logic App, or lightweight custom service. Set your Azure DevOps Webhook to send POST events to this middleware, then have the middleware transform the request and send a PATCH call to ServiceNow’s REST API. Logic Apps is especially low-effort here, as it has pre-built connectors for both platforms—you can map fields and switch HTTP methods without writing full code.
• Leverage Azure Pipelines triggers: Create a Pipeline that fires when a workitem’s state or key fields update. Within the Pipeline, use a PowerShell/Python script to fetch the latest workitem details, then make the PATCH request directly to ServiceNow. This gives you full control over the request structure and method.

2. Automatically Push Full Workitem JSON on State Update #

To trigger an automatic push of complete workitem JSON when its state changes, you have three solid options:

• Azure Event Grid: Subscribe to the WorkItemUpdated event in your Azure DevOps organization. When a workitem’s state shifts, Event Grid will trigger an Azure Function or Logic App. In that function/app, use the Azure DevOps REST API (GET https://dev.azure.com/{org}/{proj}/_apis/wit/workitems/{id}?api-version=7.1-preview.3) to fetch the full workitem data, serialize it to JSON, and push it to your target endpoint (ServiceNow or your custom service).
• Pipeline-based automation: Configure a Pipeline with a workitem trigger set to activate on state changes. Add a step to call the Azure DevOps Workitem API, save the full response as a JSON file, then use a script to push this JSON to your desired destination. This is ideal if you already use Pipelines for other automation tasks.
• Custom Azure DevOps Extension: For more flexibility, build a lightweight extension (using the Azure DevOps Extension SDK) that listens for workitem state change events. The extension can directly fetch full workitem data and send the JSON payload without relying on external services. Pre-built extensions in the Azure DevOps Marketplace also handle workitem event forwarding if you don’t want to build from scratch.

内容的提问来源于stack exchange，提问作者user3440473