ServiceNow Jira Integration: Low-Code Setup Guide for ITSM Teams

Published in IT and IT Management on 13/04/2026.

Working across ServiceNow and Jira goes beyond the usual issues that come from using multiple tools for the same workflow — lost visibility, missing context, and extra administrative work. ServiceNow is built for ITIL (IT Infrastructure Library) governed service desks that track incidents through rigid workflows with SLA (service level agreement) timers and similar requirements. Jira is built for agile development teams that collaborate through sprint-based workflows.

Whether it’s due to an escalated incident or a cross-functional project, collaborating across these tools creates a significant bottleneck. The infrastructure they’re built on makes connecting them more difficult and the workflows that move through them are completely different.

In this guide, you’ll learn how to do this seamlessly.

Overview

Unito’s two-way sync integration for ServiceNow and Jira allows users of any technical background, from product managers to software developers and team leads, to sync ServiceNow records with Jira issues. This integration syncs updates back and forth between both tools, creates new work items, and can even automate repetitive actions. This in-depth guide shows you how that’s done.

Common use cases for a Jira-ServiceNow integration

An illustration representing integration between Jira and ServiceNow.

Connecting Jira Software to ServiceNow offers a range of benefits in everyday business scenarios for an IT service desk:

Incident management: Responding promptly to incidents is an essential ITSM responsibility. But when incidents need to be escalated from first-level agents in ServiceNow to developers in Jira, the handoff creates its own problems. Response and resolution requirements from SLAs might not be met during escalations, as information like incident states doesn’t carry over automatically.
Change management: For developers in Jira, a change in process or systems is often straightforward. A request is made, it’s evaluated, and it’s implemented. Service desks using ServiceNow rely on ITIL change management and a more rigorous workflow. An integrated system for change management within your organization ensures any internal transition is properly documented, approved, and communicated quickly.
DevOps coordination: By linking Agile release management in Jira with ITIL operational tracking in ServiceNow, your organization can foster better DevOps practices.

These use cases illustrate just how integral a well-configured synchronization between ServiceNow and Jira can be for optimizing your business operations. The key is speed and efficiency in all cases.

Whether you wish to deploy a faster incident management process, IT change management system, or to fulfill cross-departmental requests automatically, integration makes a difference.

This is especially true when it comes to cyber threats when every second of response time counts. Automating tedious manual tasks enables your team to spend more of their effort on problem-solving and using their primary skill sets.

When and how to choose a Jira-ServiceNow integration solution

“Our company uses ServiceNow for customer issue tracking across all departments. The IT department primarily works in Jira. Right now, we have to manually duplicate customer issues reported in ServiceNow into Jira. This also affects tasks like release testing, leading to delays, errors, and wasted effort. We’re looking for a solution that integrates Jira and ServiceNow, so we don’t have to enter the same information twice and constantly update statuses in both systems. Our goal is to streamline our workflow and improve visibility for everyone involved.”
– Unito customer interview

How to choose the right integration solution

This decision requires a number of key considerations, particularly planning out future maintenance and scalability. You need to be able to maintain and scale your stack without incurring costly fees or having teams spend months implementing updates. Other factors worth considering include: compatibility, ease of use, security measures, and support services.

Compatibility and ease of use

The next step in selecting the appropriate solution for your Jira or Jira Service Management to ServiceNow integration involves checking compatibility between tools. You need an option that seamlessly interacts with both ServiceNow and Jira without requiring extensive modifications or complex workarounds.

Here’s what you typically need to consider:

Native integrations: The integrated capabilities of Jira and the ServiceNow platform come with a range of benefits for those with an internal integration team capable of maintaining and updating the system. ServiceNow Integration Hub offers “spokes” for connecting with other tools, such as Jira. A spoke is defined as: “a scoped application that includes Flow Designer custom actions or subflows.”
Configuration: Since your needs likely vary from another user, opting for a platform that allows adjustments can help tailor the integration to meet specific demands. So while ServiceNow offers spokes, will they serve your needs efficiently? Will you be able to configure them with precision? How much effort will that require from your own department?
User interface (UI): A straightforward UI ensures that your team can manage the integration easily. If your team is handling large volumes of code, how much time is spent maintaining it? How much does it cost to outsource that work to a service provider? A low-code solution eliminates the need for costly outsourcing and lengthy development cycles, keeping your team in control and speeding up your time to value.

So if you need a configurable integration with an accessible UI, your best bet is likely a no-code solution that’s also fully configurable, such as Unito.

Support services

Evaluate the level of customer support provided. Effective support can drastically reduce downtime and ensure problems are solved quickly:

Technical support: Accessibility to knowledgeable tech support teams who understand particulars about Jira and ServiceNow.
Documentation and training resources: Well-documented guides and tutorials facilitate smoother setup processes and troubleshooting procedures.

By carefully considering these factors within different technological offerings, you equip yourself with knowledge necessary to make an informed decision about which tool will best serve your needs for integrating ServiceNow with Jira effortlessly.

Integration options for your ServiceNow instance and Jira

An illustration representing the advantages of Unito and its 2-way sync.

Now that you know when you need an integration, let’s look at a few of your options.

ServiceNow Integration Hub

ServiceNow offers the Integration Hub, with pre-built connectors for over 200 popular tools, like Jira, GitHub, and Azure DevOps. These connectors are called Spokes, and ServiceNow’s Jira Spoke allows you to build custom connections for automating tasks and pushing data between these two tools. Here’s a breakdown of this integration option.

Technical skill required	Using ServiceNow’s Integration Hub and the Jira Spoke requires a certain level of technical knowledge. While a business user might be able to build their own integrations, it’ll require reading a significant amount of documentation. Developers and engineers will be able to get started more quickly, but that means your integrations require their involvement for building and management.
Sync direction	ServiceNow’s Spokes support some level of two-way syncing between Jira and ServiceNow, though less so than dedicated two-way integrations (as you’ll see below). Additionally, these spokes always push data to and from ServiceNow. You couldn’t, for example, move data between Jira and GitHub with these Spokes.
Licensing	Spokes come at an additional cost on top of your ServiceNow license. That means you need to closely compare what you get for your money with third-party solutions.
Maintenance	Most of the maintenance ServiceNow Spokes requires development resources, whether that’s through employees or third-party partners. When an integration goes down, it can be expensive to fix.
Setup time	Depending on the complexity of your workflow, it can take anywhere from days to weeks to set up an initial integration.

For many organizations, ServiceNow’s Integration Hub will be the first option they investigate and deploy, with varying degrees of success.

Automation solutions

Automation solutions like Zapier use simple if-this-then-that logic to take action in one tool based on triggers occurring in a different tool. With an automation like this, you could, for example, automatically create Jira issues to follow up on ServiceNow incidents that need input from a developer.

These solutions are easy to deploy, but they’re typically pretty limited in their functionality unless you spend significant time setting up and maintaining complex chains of individual automations.

RPA platforms

RPA stands for robotic process automation. These platforms allow users to automate even complex workflows with software bots that can take the same actions humans can. They can even interact with the interfaces of other software tools. That makes them sound like the perfect way to integrate ServiceNow and Jira, except for one word.

Maintenance. Even a slight change in a tool’s interface can completely break your bots, meaning you need to troubleshoot them regularly.

2-way sync

A 2-way sync solution like Unito doesn’t just automate the transfer of data between tools. It creates 2-way relationships between work items in tools like ServiceNow and Jira, meaning any update made in either tool is automatically reflected in the other.

These solutions are no code, but completely customizable. Quick to deploy, yet with robust security and administrative settings.

Here’s why these solutions are your best option, using Unito as an example.

The 2-way solution for your Jira-ServiceNow integration

Unito enables a real-time connection between ServiceNow and Jira so that updates between tools are always in sync end-to-end.

An illustration representing a Unito integration for ServiceNow and Jira.

Users can configure their flows through rules to filter out unrelated data, and a table of fields in Jira and ServiceNow. The field mappings table allows you to set the relationship between fields in each tool to link statuses, summaries, assignees, attachments etc. as well as set a separate sync direction for each pair of fields.

Seamless data flow: Bi-directional syncing ensures issues and updates in either Jira or ServiceNow are mirrored automatically, eliminating manual effort and ensuring everyone has the most current information.
Enhanced organization: IT service departments, support staff, and other departments can collaborate effortlessly. Issues move smoothly between Jira and ServiceNow based on your workflow rules, speeding up resolution.
Greater visibility: Real-time updates provide a clear and centralized view of all ITSM activities, regardless of which system they originate in. This enables faster decision-making and better insights for process improvement.

Setting up a single Unito flow only takes the average user ~12 minutes, making it far more accessible than an integration tool based in Groovy or JavaScript.

Illustrations representing stats about how easy to use Unito is.

Two people working on a laptop while smiling, in a banner advertising Unito's Savings Calculator.

Unito reduces the risk of manual input and error in ITSM

Unito reduces the need for manual data entry and all but eliminates the risk of human error, for a more effective collaboration between tools, optimized communication and visibility, and a more flexibile ITSM process.

Optimizing communication and visibility

A Jira ServiceNow integration eliminates the need to chase updates across multiple systems. Real-time syncing provide stakeholders with up-to-the-minute details on Jira issues and linked ServiceNow incidents or records. Instead of relying on scattered emails or Slack threads, everyone has clear, consolidated insights into issue status and progress. This promotes smoother handoffs between departments and better decision-making.

Flexible ITSM processes and reduced errors

Your ITSM department can configure their flow to align ServiceNow perfectly with Jira. Detailed field mapping ensures the right information flows between Jira issues and ServiceNow incidents. Comments, status updates, and issue assignments stay in sync automatically. This saves time, reduces the risk of errors, and lets you adapt the integration as your ITSM processes evolve.

Step-by-step instructions: Connect Jira to ServiceNow with Unito

Unito simplifies ITSM workflows, addressing these challenges head-on:

Quick configuration: Unito’s low-code setup means you’ll be up and running quickly. Intuitive configuration tools let you tailor the data flow to your specific ITSM processes.
Error reduction: Automated syncing eliminates manual updates, significantly reducing the risk of mistakes and data discrepancies.
Granular control: Fine-tune field mapping and syncing rules to ensure only the necessary information is shared between Jira and ServiceNow. This balances visibility with data control.
Enhanced visibility: Everyone involved, from IT service agents to those in other departments, sees the full up-to-date picture, promoting faster resolution.
Team management: The Unito team can help you put together a permission model to help you manage your workspace(s) effectively.

By the end of this guide, your ServiceNow-Jira integration will:

Create new Jira issues automatically based on ServiceNow records you create.
Create new ServiceNow records synced with the Jira issues you work on.
Update fields in real-time as you work in both tools.

This integration is best for:

Tools: ServiceNow and Jira
Use cases: Ticket escalation, product management, software development
Great for: Product managers, IT, customer success, software developers, project management

More of a visual learner? Check out this video tutorial!

Connecting ServiceNow to Unito for the first time

A ServiceNow admin needs to set up the initial connection between Unito and your ServiceNow account. From there, you can authorize Unito to sync data out of ServiceNow using OAuth 2.0 or a username and password.

Make sure you have the following information on hand to connect your account:

ServiceNow Domain URL: https://INSTANCENAME.service-now.com
OAuth 2.0: An OAuth Client ID and Secret
Username: Your ServiceNow username and password

Before you sync

You need to connect a ServiceNow account with CRUD rights (create, read, update, and delete) for the records and tables you plan on syncing to Unito. If you’re not sure how to do this, contact your ServiceNow admin for guidance.

Setup in Jira

If you’re connecting Jira to Unito via OAuth2, then simply follow the on-screen instructions when adding your account for the first time:

If you’re not using OAuth 2 to connect to your Jira Cloud workspace, you’ll need to do the following:

Set your Jira contact email visibility to anyone in your Jira profile page.
Set up an application link in Jira to sync your issues to ServiceNow.

If you’re connecting an on-premise Jira Server instance to Unito, you’ll need to follow this guide. You can also use ngrok to connect Jira Server to Unito.

Step 1: Connect ServiceNow and Jira to Unito

Sign up for Unito.
Click +Create Flow in the Unito app.
Click Start Here to connect ServiceNow and Jira.
Click +Choose account for each tool and complete the authorization process.
Choose the type of ServiceNow record you want to include in your flow. Unito supports all record types, including requests and incidents.
Choose the ServiceNow table and Jira project you want to sync.
Once that’s done, click Confirm.

First time connecting tools to Unito? Check out our in-depth guide.

Step 2: Choose flow direction

With flow direction, you determine where Unito automatically creates work items to match those you create manually. You have three options:

2-way: Both ServiceNow records and Jira issues are automatically created by your Unito flow to match the items your team creates manually in each tool.
1-way from ServiceNow to Jira: Jira issues will be automatically created by Unito to match ServiceNow records you create manually. Unito won’t create new ServiceNow records.
1-way from Jira to ServiceNow: ServiceNow records will be automatically created by Unito to match Jira issues you create manually. Unito won’t create new Jira issues.

Unito's flow direction screen, with ServiceNow and Jira connected.

Here’s a more detailed guide to how flow direction works.

Step 3: Build rules to sync specific work items

Unito rules can do two things:

Filter out work items you don’t want to sync. For example, you could create a rule that only syncs records set as High priority.
Automating certain actions. For example, you could create a rule that automatically assigns new Jira issues to a specific user.

To start building your rule, click Add a new rule, then choose a trigger and action.

You can learn more about setting rules here.

Step 4: Map fields between ServiceNow and Jira

Unito uses a visual field mapping interface, with dropdowns that show you which field combinations are possible. If you’re used to writing JQL queries to filter Jira issues, you’ll find Unito’s visual mappings just as powerful but easier to configure and maintain.

When you map fields, you pair fields in ServiceNow with fields in Jira so data always goes right where it needs to be. Unito can usually map most fields automatically, whether they’re exactly the same (Assignee→Assignee) or compatible (URL→Text). You can also choose to map fields manually to fully customize your flow.

A screenshot of Unito's mapping screen, asking the user if they want to map fields automatically or manually.

Here’s what you’ll see when Unito maps your fields automatically.

To add a new field mapping, click +Add mapping then Select a field. When you choose the field you want to map in one tool, Unito will automatically recommend compatible fields in a dropdown under the other tool.

Fields identified with a cog icon can be customized further once they’re mapped. For example, a Status field can be customized so its options match those in another field.

A screenshot of the field mapping screen in Unito, with a submapping for an Issue Status field open.

For example, you can map ServiceNow’s Incident State field to Jira’s Status field. This achieves two things:

When Unito automatically creates a work item in one tool to match the item in the other, these fields are set to the right option. A Jira issue created to match a ServiceNow record will have its Status set to To-Do if that option is mapped to an equivalent To-Do Incident State in ServiceNow.
Unito will automatically update the field in one tool to match the field in the other as you work. If you change the Incident State in a ServiceNow record from To-Do to Blocked, for example, Unito might switch the Status field in the matching Jira issue from Backlog to Blocked. Essentially, this mapping allows you to match progress in Jira to progress in ServiceNow.

The values don’t need to match exactly for this to be the case. You could match a “To-Do” status in Jira to “Blocked” in ServiceNow, representing the fact that records in ServiceNow are blocked while development work happens in Jira.

Step 5: Launch your ServiceNow-Jira integration

That’s it! You’re ready to launch your flow. Unito will automatically keep ServiceNow records and Jira issues in sync. This will allow your teams to collaborate more effectively without copying and pasting data or jumping back and forth between tools.

Book a demo to see if this integration is right for you

Assess your organization

Summary: Jira ServiceNow integration

For enterprise-level IT and engineering teams, efficient cross-departmental collaboration is crucial. Unito’s Jira + ServiceNow integration simplifies incident management and other core ITSM tasks via low-code, 2-way syncing to mitigate wasted time and lost opportunities.

Reduced human error: The automated flow of data between tools reduces the risk of human error caused by manual updates and saves time. Unito’s fully configurable field mappings allow users to enjoy greater flexibility than they would with ServiceNow Integration Hub.
Greater Visibility and Control: Real-time updates provide a clear, consolidated view of incidents, records, tasks, and issue lifecycles, regardless of origin. This increased visibility enables faster decision-making and resolution.
Enhanced Customer Experience: By streamlining ITSM processes with a Jira + ServiceNow integration, support teams can resolve issues faster to make your customers happier.

FAQ: ServiceNow-Jira integration

Does Jira integrate with ServiceNow?

You can integrate Jira with ServiceNow in a number of ways:

The Jira Spoke in the ServiceNow Integration Hub, which is available with ServiceNow at an extra cost.
Script-based integration tools like the Exalate app, which require some level of technical knowledge to work best.
Two-way sync integration platforms like Unito, which automatically sync data back and forth between Jira and ServiceNow.

When should you use Jira vs. ServiceNow?

While Jira and ServiceNow have some similarities, they’re used very differently. ServiceNow is typically the hub for an organization’s service workflows, whether that’s ITSM (IT service management) or customer service.

Jira allows teams to manage service workflows as well (especially through Jira Service Management), but it’s best suited to product work and project management. That’s why most organizations will use both tools.

What integrations are supported by ServiceNow?

Through the ServiceNow Integration Hub and third-party apps, ServiceNow offers over 1,000 integrations.

How does Unito handle ServiceNow state to Jira status mapping?

Unito’s field mappings use a visual interface with dropdowns to match ServiceNow states with Jira statuses. You can pair individual statuses in Jira with ServiceNow states without writing scripts, and the statuses don’t have to match to be mapped.

Does Unito support custom ServiceNow fields and tables?

Yes. Every ServiceNow field is technically a custom field, and Unito supports a wide range of them. Unito works with any ServiceNow table, not just incidents.

What’s the difference between Unito and the ServiceNow Jira Spoke?

ServiceNow’s Jira Spoke requires some level of technical knowledge, whether you’re building or maintaining integrations. You also will only be able to pair ServiceNow and Jira. Unito is a standalone platform that’s easy to use and no-code. It also supports over 60 integrations, allowing you to use the same platform to pair ServiceNow and Jira, ServiceNow and GitHub, Jira and Trello, and more.