When the Jira Spoke Isn't Enough: 5 Signs You Need an External ServiceNow Jira Integration

Last updated: October 2026

The ServiceNow IntegrationHub Jira spoke is the official way to connect ServiceNow with Jira, and it works well for simple, ServiceNow-led flows. You likely need an external ServiceNow Jira integration tool when one of five things is true: you do not have an Integration Hub subscription, Jira Service Management or Jira Data Center is in scope, you need full bidirectional sync of comments, attachments and statuses, you run multiple instances, or the flows have become too costly to maintain. Third-party options range from Atlassian Marketplace apps to standalone no-code platforms such as ZigiOps by ZigiWave.

This is not an anti-spoke article. Spokes are a good piece of engineering, and if you already pay for Integration Hub and your use case is simple, using the native option is often the right call. But in community threads, the same question appears again and again: "We started with the Jira spoke, and now it is getting complicated. Should we keep building, or use something else?"

Here are the five signs that it is time to look beyond the spoke, based on what ServiceNow's own documentation says the spoke does and does not cover, followed by criteria for choosing a third-party tool if you decide to.

First, what the Jira spoke actually is

A spoke is a packaged set of IntegrationHub actions, triggers and subflows for a third-party system. According to ServiceNow's Jira spoke documentation, the spoke:

• Requires an Integration Hub subscription.
• Depends on IntegrationHub components including the runtime, the REST action step, the data stream action template and Flow Designer dynamic inputs.
• Provides actions to create, update and look up Jira records from Flow Designer.
• Provides triggers for Jira events, which require webhooks to be configured.
• Does not support Jira Service Desk; ServiceNow offers a separate Jira Service Management spoke for that.
• Includes some actions documented as usable with a Jira Cloud subscription only.

The latest version listed in the documentation at the time of writing is Jira spoke v6.1.3, and newer releases add Now Assist AI agents for Integration Hub. ServiceNow invests in this spoke, and it keeps improving.

Sign 1: You do not have, or do not want to buy, Integration Hub

The spoke is "native", but it is not included in every ServiceNow subscription. ServiceNow's documentation states plainly that the Jira spoke requires an Integration Hub subscription, and so does the Jira Service Management spoke.

If your organization already licenses Integration Hub for other spokes, the incremental cost of using it for Jira may be low. If it does not, you are comparing the cost of an Integration Hub subscription, plus the time to build flows, against the cost of a dedicated integration tool. For many teams whose only immediate need is ServiceNow and Jira, a dedicated tool is the cheaper and faster path.

Question to ask: what would Integration Hub cost us for this use case alone, and what else would we use it for in the next two years?

Sign 2: Jira Service Management or Jira Data Center is in scope

The Jira spoke is designed for Jira Software projects. ServiceNow's documentation notes that Jira Service Desk, now Jira Service Management, is not supported by the Jira spoke. The separate JSM spoke provides actions such as creating customer requests, looking up service desks and queues, managing organizations and customers, and looking up SLA information.

That means a process touching both a Jira Software development project and a JSM support project needs two spokes, two sets of connections and flows that coordinate between them. Add Jira Data Center to the mix and you also need to check which actions are documented as Jira Cloud only.

External tools usually treat Jira Software and Jira Service Management as variants of the same connected system. In ZigiOps, for example, you add Jira once and enable the JiraSD option in advanced settings to work with service desk requests. ZigiOps supports Jira Cloud and Jira Data Center from version 7.x upwards, according to its documentation.

Sign 3: You need true two-way sync, not just "create an issue"

The most common spoke use case is one-directional: when an incident is assigned to a development group, create a Jira issue. That is a tidy flow with a trigger, a few data pills and a "Create Issue" action.

Real escalation processes rarely stop there. Engineers comment in Jira and the service desk needs to see it. The service desk adds a screenshot and engineering needs it. Jira moves to Done and the incident needs to resolve, with mandatory resolution code and notes. The caller reopens the incident and Jira needs to know.

With the spoke, ServiceNow's documentation notes that you must configure webhooks to use the spoke subflow and that bi-directional webhooks require separate setup. In practice, full bidirectional sync means:

• A flow for incident creation and another for incident updates.
• Jira webhooks and spoke triggers for issue updates, comments and transitions.
• Logic to handle attachments in both directions.
• Correlation, so each update reaches the right record.
• Loop prevention, so updates written by the integration do not trigger the opposite flow.
• Status and priority translation in decision tables or branches.

None of this is impossible. It is simply a lot of flow logic to build, test and maintain. External tools such as ZigiOps provide these as built-in features: create and update operations in each direction, a correlation setting, a Last Time expression to avoid duplicates, trigger conditions to ignore changes made by the integration user, and conditional field mapping for statuses and priorities, all in a guided UI.

Sign 4: You run more than one instance

Multi-instance environments are where spoke-based integrations tend to sprawl. Common examples:

• Several Jira sites after an acquisition, or a separate Jira for a regulated business unit.
• ServiceNow production plus one or more sub-production instances that each need a working integration for testing.
• Managed service providers connecting their ServiceNow to many customers' Jira or JSM instances.
• A partner or supplier who uses their own Jira, outside your organization.

Each additional Jira instance means another connection and credential alias, and usually duplicated or parameterized flows. Each additional ServiceNow instance means repeating the setup there too.

External platforms are often built for this pattern. In ZigiOps, each pair of system instances is configured separately, and integrations can be exported and imported between environments. According to the ZigiOps licensing documentation, one license point enables unlimited integrations between a pair of instances, and there is no limit on the number of transactions, so adding volume to an existing pair does not change the bill.

Sign 5: Maintenance has become someone's part-time job

The quietest sign is often the most expensive one. Look for these symptoms:

• Every new Jira field or workflow status becomes a ServiceNow development story.
• Only one or two people understand how the flows fit together.
• Integration issues appear in your backlog alongside the business work the integration was meant to free up.
• Spoke upgrades or Jira API changes trigger regression testing cycles.
• The service desk team has started copying updates by hand "just in case".

If the people who own the process, typically service managers, cannot change the integration themselves, it will always lag behind the process. A 100% no-code external tool moves that ownership to them.

Spoke vs external integration tool: a side-by-side view

When you should stay with the spoke

To be fair, the spoke is the better choice in several situations:

• You already license Integration Hub and use it for other integrations.
• The use case is one-directional or very light two-way.
• Only one Jira Cloud site and one ServiceNow instance are involved.
• Your governance rules require all integration logic to live inside ServiceNow.
• You have Flow Designer expertise available for ongoing changes.

If that describes you, keep the spoke and invest in good flow design: a single subflow per direction, a dedicated integration user, and documented status mappings.

Criteria for choosing a third-party ServiceNow Jira integration tool

If two or more of the five signs apply, it is worth evaluating third-party tools. These are the criteria that separate them in practice.

1. Bidirectional depth. Does it sync incidents, problems, changes and catalog tasks, plus comments, work notes, attachments and statuses, both ways?
2. Coding required. Can a service manager change a mapping without scripts? Some tools need Groovy or JavaScript for anything beyond the defaults.
3. Installation footprint. Does it require an app installed in Jira, in ServiceNow, or both? Standalone tools connect through APIs and avoid that.
4. Jira coverage. Jira Software, Jira Service Management, Cloud and Data Center.
5. Multi-instance support. How easy is it to add another Jira site or ServiceNow instance, and what does it cost?
6. Pricing model. Per synced item, per user tier, per task or per instance pair. Model your volume for three years.
7. Data handling. Does the tool store your ticket data? ZigiOps, for example, does not store any transferred data.
8. Security. Independent certification such as ISO 27001, encrypted credentials, access controls.
9. Deployment. On-premises, cloud or both, and high availability options.
10. Operational visibility. Can non-developers see what synced, what failed and why?

How ZigiOps fits as an external option

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 teams moving beyond the spoke, the practical differences are:

• No scripts: correlation, triggers, field mapping, conditional mapping and expressions are all configured in a guided UI.
• Ready templates: ServiceNow incidents to Jira tasks, Jira tasks to ServiceNow incidents, ServiceNow problems to Jira bugs, and ServiceNow service catalog tasks to Jira tasks.
• Standalone architecture: nothing to install inside ServiceNow or Jira for standard use cases; the integration user needs documented roles and read access to a few system tables for schema discovery.
• Multi-instance and unlimited transactions: each instance pair is configured and licensed separately, with no per-record charges.
• Deployment choice: on-premises on Windows or Linux, or cloud, with a primary and backup high-availability option.

Migrating from spoke flows to an external tool

1. Document your flows: triggers, conditions, mappings and any decision tables for status and priority.
2. Keep your correlation fields: if your flows already store the Jira key in correlation_id, reuse it so existing record pairs continue syncing.
3. Rebuild in a sub-production instance: recreate the logic as create and update operations, and test with real records.
4. Deactivate flows and enable the new integration in a maintenance window, starting with update operations so in-flight records continue syncing.
5. Monitor for a week, then retire the old flows and webhooks.

Frequently asked questions

What are the official ServiceNow Jira integration tools?

ServiceNow provides the Jira spoke and the Jira Service Management spoke in IntegrationHub. Both require an Integration Hub subscription and are configured with Flow Designer.

Can the ServiceNow Jira spoke do bidirectional sync?

Yes, but you assemble it from flows, spoke triggers and Jira webhooks. ServiceNow's documentation notes that bi-directional webhooks require separate setup.

What are the best third-party tools for ServiceNow Jira integration?

Common options include standalone platforms such as ZigiOps and OpsHub Integration Manager, and Atlassian Marketplace apps such as Exalate and Getint. They differ in coding requirements, installation footprint, pricing model and data handling, so compare them against the criteria above.

Can ZigiOps replace the ServiceNow Jira spoke?

Yes. ZigiOps covers the same incident-to-issue use cases and adds bidirectional sync of comments, work notes, attachments and statuses, Jira Service Management support and multi-instance configuration, all without code and without an Integration Hub subscription.

Does ZigiOps need to be installed inside ServiceNow?

No. ZigiOps is a standalone application that connects to ServiceNow through its API using an integration user. Some specialised ZigiOps use cases offer optional ServiceNow scoped applications, but standard ServiceNow and Jira integrations do not need one.

Is it worth keeping the spoke if we already pay for Integration Hub?

Often, yes, for simple one-way flows. Teams that already pay for Integration Hub still move to external tools when bidirectional sync, JSM, multiple instances or maintenance effort make the flows hard to manage.

Key takeaways

• The Jira spoke is ServiceNow's official Jira integration and requires an Integration Hub subscription.
• It does not cover Jira Service Management; the separate JSM spoke does.
• The five signs you need an external tool: no Integration Hub, JSM or Data Center in scope, true two-way sync, multiple instances, and rising maintenance effort.
• Choose third-party tools on bidirectional depth, coding required, installation footprint, pricing model, data handling and security.
• ZigiOps by ZigiWave offers a standalone, no-code alternative with no data storage, ISO 27001 certification and no transaction limits.

ZigiWave's website has more on this topic, including its Jira ServiceNow integration page, a guide to ServiceNow incident to Jira issue mapping, and an article on conditional mapping for Jira ServiceNow integrations.