ServiceNow Jira Integration Options in 2026: IntegrationHub Spoke, REST API and No-Code Connectors Compared

Last updated: October 2026

There are four main ServiceNow Jira integration options in 2026: the native Jira spoke in ServiceNow IntegrationHub, a custom integration built on the ServiceNow and Jira REST APIs, an app from the Atlassian Marketplace or ServiceNow Store, and a standalone no-code integration platform such as ZigiOps by ZigiWave. The spoke suits teams that already pay for IntegrationHub and are happy to build flows, REST suits teams with developers to spare, and standalone platforms suit teams that want bidirectional sync without scripts or plugins on either side.

That is the short answer. The longer answer depends on what you need to sync, how many instances you run, who will maintain the integration in two years, and how your security team feels about data passing through a third party. This article compares all four options on concrete, documented criteria, so you can pick the right one before you write a single flow or line of code.

Why ServiceNow and Jira need to talk in the first place

In most enterprises, ServiceNow is where the service desk lives and Jira is where engineering lives. An incident is logged in ServiceNow, someone figures out it is a code problem, and then the fun begins: copy the description into Jira, paste the Jira key back into a work note, chase the developer for updates, and copy those back too.

Multiply that by a few hundred incidents a month and you have a full-time job nobody signed up for. It is also a broader industry problem. According to MuleSoft's 2025 Connectivity Benchmark Report, which surveyed 1,050 IT leaders, the average enterprise now runs 897 applications, yet only 29% of them are integrated. ServiceNow and Jira are usually two of the biggest unconnected islands.

A proper ServiceNow Jira integration replaces that manual relay with an automated, usually bidirectional sync of records such as incidents, problems, change requests and service catalog tasks on the ServiceNow side, and issues, bugs, tasks and epics on the Jira side.

The four ServiceNow Jira integration options at a glance

Before going deep, here is how the four approaches compare on criteria that actually show up in production. Every row is based on vendor documentation, which is named in the sections below.

Now let us look at each option properly, including the parts vendors tend to mention in small print.

Option 1: The ServiceNow IntegrationHub Jira spoke

If you search the official ServiceNow documentation for Jira integration, the Jira spoke is what you will find first. A spoke is a packaged set of IntegrationHub actions, triggers and subflows for a specific third-party system, built and maintained by ServiceNow.

How the Jira spoke works

According to ServiceNow's Jira spoke documentation, the spoke depends on several IntegrationHub components, including the IntegrationHub Runtime, the REST action step and Flow Designer dynamic inputs. You configure a connection and credential alias for your Jira instance, then use spoke actions inside Flow Designer flows. Typical actions include creating, updating and looking up Jira issues.

For the Jira-to-ServiceNow direction, the spoke offers triggers that subscribe to Jira events. ServiceNow's documentation notes that you must configure webhooks to use the spoke subflow, and that bi-directional webhooks require separate setup. In other words, two-way sync is achievable, but you assemble it from parts.

What the documentation says about requirements

Three details from the official ServiceNow documentation matter for planning:

• Subscription: the Jira spoke requires an Integration Hub subscription. If your ServiceNow contract does not include it, this is the first budget conversation.
• Jira Service Management: the Jira spoke does not support Jira Service Desk. ServiceNow offers a separate Jira Service Management spoke for that, which also requires an Integration Hub subscription.
• Jira Cloud only actions: some spoke actions are documented as usable with a Jira Cloud subscription only, which matters if you still run Jira Data Center.

ServiceNow keeps the spoke current. At the time of writing, the documentation lists Jira spoke version 6.1.3 as the latest. That is good news for compatibility, but it also means flows built on older versions may need review after upgrades.

When the Jira spoke is the right choice

The spoke is a sensible choice when your organization already has Integration Hub, your ServiceNow team is comfortable with Flow Designer, and the integration is mostly one-directional, for example creating a Jira issue when an incident is assigned to a development group. It keeps everything inside the ServiceNow platform, which some governance teams prefer.

It becomes harder work when you need full bidirectional sync of comments, attachments and statuses, multiple Jira instances, or both Jira Software and Jira Service Management in the same process. Each of those adds flows, webhooks and testing.

Option 2: A custom integration on the ServiceNow and Jira REST APIs

Both platforms have mature, well-documented REST APIs. A custom build typically looks like this:

1. An outbound REST Message in ServiceNow, called from a business rule or flow, that creates or updates a Jira issue through the Jira REST API.
2. A Jira webhook (or Jira Automation rule) that calls a Scripted REST API endpoint in ServiceNow when the issue changes.
3. A correlation strategy, usually storing the Jira key in the incident's correlation ID field and the ServiceNow sys_id or number in a Jira custom field.
4. Loop prevention, so an update made by the integration user does not bounce back and forth forever.
5. Error handling, retries, logging and alerting for when either API is unavailable.
6. Field transformations for statuses, priorities, users and anything else that does not match one to one.

None of this is exotic. It is, however, a lot of moving parts that someone has to own. Authentication alone involves Jira API tokens or OAuth, ServiceNow credentials or OAuth profiles, and rotation policies for both.

When the REST API route makes sense

Custom code makes sense when the use case is narrow and stable, your developers already maintain ServiceNow scripts, and you need behaviour no product supports. It makes less sense when requirements change often, because every new field or status becomes a development ticket. The integration you build to remove tickets can quietly become a source of them.

Option 3: Apps from the Atlassian Marketplace or ServiceNow Store

The Atlassian Marketplace lists several ServiceNow connectors for Jira. They differ a lot in architecture and pricing, so "a Marketplace app" is not one option but several.

• Exalate is installed on both sides of the connection. Its Marketplace listing states that you need to install Exalate on your Jira and on ServiceNow. Sync rules are written in Groovy, and Exalate's documentation describes Aida, an AI assistant that generates Groovy scripts from plain-language descriptions. New Exalate pricing is based on active items in sync: Starter covers up to 25 items, Scale up to 100, Pro has custom limits and Enterprise is unlimited, per Exalate's own documentation.
• Getint offers ServiceNow integration as a Jira app, with SaaS and on-premises deployment options listed on Capterra. Its Marketplace listing highlights one-way or two-way sync and lists ISO 27001 and SOC 2.
• OpsHub Integration Manager also has a bidirectional ServiceNow integration for Jira on the Marketplace, aimed at larger multi-project deployments.

Marketplace apps are quick to trial and often good value for a single Jira and ServiceNow pair. The questions to ask are about scale: how pricing grows with synced items or Jira users, whether you need an app on both sides, and how much scripting your use case will eventually require.

Option 4: A standalone no-code integration platform

The fourth option is a dedicated integration platform that sits between ServiceNow and Jira as its own application. It connects to both systems through their APIs and handles the sync logic itself, so neither side needs a plugin, spoke or custom script.

How ZigiOps handles ServiceNow Jira integration

ZigiOps, from ZigiWave, is a standalone, 100% no-code integration platform that connects ITSM, ITOM, DevOps and CRM tools in real time, without storing any of the transferred data. It is ISO 27001 certified and has no limit on the number of transactions.

For ServiceNow and Jira specifically, the ZigiOps documentation describes the building blocks:

• Connected systems: you add ServiceNow with its instance URL and an integration user, and Jira with its URL and a username plus password or API token. For Jira Service Management, you enable the JiraSD option in the connected system's advanced settings.
• Templates: ready-made integration templates exist for common flows, including ServiceNow incidents to Jira tasks, Jira tasks to ServiceNow incidents, ServiceNow problems to Jira bugs and ServiceNow service catalog tasks to Jira tasks.
• Correlation: ZigiOps stores the ID of one record in a field of the other, for example the Jira key in the ServiceNow correlation_id field, so it can keep updating the right pair in both directions.
• Triggers: a polling trigger (the documentation recommends a 1 minute interval) or a listener trigger that receives incoming HTTP requests.
• Field mapping and conditions: map fields in the UI, combine fields with static text, and use conditional mapping, for example sending Jira priority "Highest" only when ServiceNow impact and urgency are both 1.
• Expressions: built-in transformations such as Last Time (to collect only new records and avoid duplicates), Pattern for regular expressions, and date formatting.

Because ZigiOps is a standalone application rather than a plugin, there is no app inside Jira or ServiceNow that has to be re-certified or reinstalled when either platform is upgraded. It can run on-premises on Windows or Linux, or in the cloud.

When a standalone platform is the right choice

Standalone platforms fit best when you need bidirectional sync of incidents, comments, work notes, attachments and statuses, when more than one Jira or ServiceNow instance is involved, when the people maintaining the integration are service managers rather than developers, or when your security review prefers that no copy of ticket data is kept by the integration layer.

How to choose between the ServiceNow Jira integration options

A practical way to choose is to answer five questions in order. The first "yes" usually points to the best fit.

Costs that are easy to miss

Licence price is only one line in the budget. When comparing ServiceNow Jira integration options, also estimate:

• Build time: hours to configure flows, scripts or mappings, including testing in a sub-production instance.
• Maintenance time: hours per quarter to update flows or scripts after a new field, a new Jira workflow status or a platform upgrade.
• Volume growth: what happens to cost if synced items double. Per-item pricing and transaction-based pricing grow with you, whether you like it or not.
• Instance growth: the cost of adding a second Jira site or a sandbox pair.
• Security review: the effort to approve a vendor that stores your ticket data versus one that does not.

Common mistakes when evaluating ServiceNow Jira integration options

A few patterns come up again and again in ServiceNow and Atlassian community threads:

• Assuming the spoke is free. It is included only if your subscription includes Integration Hub.
• Forgetting Jira Service Management. If your support team uses JSM rather than Jira Software, check that the option you pick supports it. The Jira spoke does not; the JSM spoke, many apps and ZigiOps do.
• Mapping fields instead of meaning. ServiceNow states and priorities are driven by impact and urgency; Jira workflows are team-defined. Plan status and priority translation tables before you build.
• Skipping loop prevention. Every two-way integration needs a rule that ignores changes made by the integration user, or you will see the same comment posted forty times.
• Testing only the happy path. Test attachments, long descriptions, closed and reopened tickets, and what happens when one system is down.

A note on volume and scale

Volume matters more than most teams expect. Integrations start with a handful of escalated incidents and grow into syncing problems, changes and catalog tasks across several projects. With per-item pricing, that growth shows up on the invoice. With custom code, it shows up in the backlog.

ZigiOps is licensed per pair of system instances rather than per record. According to the ZigiOps licensing documentation, one license point enables unlimited integrations between a specific pair of instances, for example ServiceNow instance 1 and Jira instance 1. Adding a second Jira instance adds a second point. For sizing, the documentation describes small and enterprise deployment types and supports horizontal scaling by adding more ZigiOps instances when data volume exceeds the enterprise profile.

Frequently asked questions

Can ServiceNow integrate with Jira natively?

Yes. ServiceNow provides a Jira spoke in IntegrationHub, plus a separate Jira Service Management spoke. Both require an Integration Hub subscription, and you build the integration logic with Flow Designer flows, actions and triggers.

Does the ServiceNow Jira spoke support Jira Service Management?

No. ServiceNow's documentation states that Jira Service Desk is not supported by the Jira spoke. For Jira Service Management you use the separate JSM spoke, a Marketplace app or a standalone platform such as ZigiOps.

Can I integrate ServiceNow with Jira without coding?

Yes. No-code options include some Marketplace apps and standalone platforms. ZigiOps is 100% code-free: connections, field mappings, conditions and triggers are all configured in a guided UI.

Can ZigiOps sync comments and attachments between ServiceNow and Jira?

Yes. ZigiOps synchronizes related records such as comments, work notes and attachments along with the main record, in both directions, based on the mapping you configure.

Does ZigiOps store ServiceNow or Jira data?

No. ZigiOps does not store any of the transferred data. It keeps only a small runtime state, a few kilobytes of files used to track what has been synchronized, which is also what makes failover to a backup server straightforward.

Is ZigiOps a ServiceNow or Jira plugin?

No. ZigiOps is a standalone application that connects to both systems through their APIs. You do not install an app inside Jira or ServiceNow for a standard incident-to-issue integration.

What is the best ServiceNow Jira integration option for multiple instances?

For multiple Jira or ServiceNow instances, a standalone platform is usually simpler than chaining spoke flows or duplicating custom code. With ZigiOps, each pair of instances is configured and licensed separately, with no limit on transactions per pair.

Key takeaways

• The four ServiceNow Jira integration options are the IntegrationHub Jira spoke, custom REST APIs, Marketplace or Store apps, and standalone platforms such as ZigiOps.
• The Jira spoke requires an Integration Hub subscription and does not cover Jira Service Management; a separate JSM spoke does.
• Custom REST integrations offer full control at the price of full ownership.
• Marketplace apps vary widely: check whether they need installing on both sides, whether they need scripting, and how pricing scales with synced items.
• ZigiOps by ZigiWave offers bidirectional, 100% no-code sync as a standalone application, with no data storage, ISO 27001 certification and no transaction limits.

For a deeper look at the configuration side, the ZigiWave website has a dedicated Jira ServiceNow integration page and a ServiceNow incident to Jira issue mapping guide, and ZigiOps is listed on the Atlassian Marketplace as a no-code ServiceNow integration for Jira Service Management.