Get a first look at what's coming. The Developer Passport Australia Release Preview kicks off March 12. Dive in! 

How bidirectional integration between ServiceNow and Jira works without using flow

Hafeeza_Shaik
Tera Contributor
Can someone provide an overview of how a bidirectional integration between ServiceNow and Jira works without using flows, instead leveraging spokes, APIs, and REST messages?

 

1 ACCEPTED SOLUTION

Ankur Bawiskar
Tera Patron

@Hafeeza_Shaik 

see these links

Jira Integration with ServiceNow using Webhook 

Jira to ServiceNow integration Scripted REST API Jira WebHook 

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader

View solution in original post

4 REPLIES 4

Ankur Bawiskar
Tera Patron

@Hafeeza_Shaik 

JIRA to ServiceNow usually is done using paid spoke.

if not spoke then you need to develop custom outbound and inbound integrations with JIRA

It all depends on what your customer requires.

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader

Can you provide a brief description of how the configuration is done in Jira to maintain parallel data synchronization across both instances?

Ankur Bawiskar
Tera Patron

@Hafeeza_Shaik 

see these links

Jira Integration with ServiceNow using Webhook 

Jira to ServiceNow integration Scripted REST API Jira WebHook 

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader

Vishal36
Mega Guru

Hi @Hafeeza_Shaik

This comes up pretty often when teams want ServiceNow and Jira talking to each other, but without relying on Flow Designer or low-code flows. A few things to keep in mind when you’re thinking about a bi-directional setup using spokes, APIs, and REST messages:

  • Mapping logic lives in scripts: Without flows, you’re usually relying on scripted REST messages and business rules to map incidents, tasks, or changes to Jira issues. This gives flexibility, but it also means more custom logic to maintain.
  • Bi-directional updates need guardrails: You’ll need a reliable way to prevent update loops when changes come back from Jira, typically via correlation IDs or custom flags.
  • Rich data handling is non-trivial: Attachments, comments, and inline text don’t sync automatically. Each requires additional API calls and error handling.
  • Traceability and scale: As volume grows, retry logic, auditing, and failure handling become just as important as the initial integration logic.

In your case, you may want to explore OpsHub Integration Manager (OIM), a ServiceNow Partner. It’s a no-code, plugin-free platform built for bi-directional ServiceNow–Jira integrations, preserves rich data like attachments and comments, and works out of the box without custom scripts.

Hope it helps!