Guide: How to Connect ServiceNow to Azure DevOps with a Fully Configurable, No-Code, 2-Way Sync

Copper Contributor

Let's talk about integrations. You need them because your business runs on too many different software systems that don't communicate with each other, so people end up working in data silos without a reliable source of truth. So each department ends up dealing with incomplete data or relying on inefficient and unreliable manual data transfer processes.

 

So what are your options? Integrations break data silos, increase the capabilities of the entire software stack, improve overall efficiency, and provide you with real-time visibility and alignment.

 

However integration requests are overflowing the backlogs of every IT department.

 

Does that sound right? If not, let me know in the comments.

 

Integration solutions today are either too basic, or excessively complicated, forcing you to default to a complex and costly solution provided by external consultants or you get to DIY like building an IKEA bedroom set without instructions.

 

Unito is a Microsoft partner with a new integration for ServiceNow to Azure DevOpsWhat makes it different? It was designed with 2-way sync from the start in the form of a no-code platform that's still fully configurable. So you get 50+ powerful integrations right out of the box, and the ability to deeply customize and adapt them without writing or maintaining code. But you can if you want to.

 

So anyone can sync records in ServiceNow to Azure DevOps work items with real-time 2-way updates between fields.

 

How does it work? Users create low-code 2-way integrations called "flows". The flow represents the connection between ServiceNow and Azure DevOps.

 

  1. You start by selecting a table in ServiceNow and a project in ADO.
  2. Then, you choose a flow direction for item creation. Do you want manually created records to automatically add work items in ADO; vice versa; or both?
  3. Next, you set rules with an "if this, then that" logic to filter out unrelated records or work items. Typically you would add tags in ADO and only sync work items with those tags, but you can also filter by custom fields or any other native field.
  4. Finally, you set up a table of field mappings populated with drop-down menus that include data pulled from ServiceNow and ADO:
     ADO ServiceNow Fields.png

Here's a longer guide to connecting Azure DevOps projects to ServiceNow tables.

 

Let me know if you have any questions or comments!

0 Replies