ServiceNow-Jira Connector: The Options Compared Side by Side
A ServiceNow-Jira connector turns ServiceNow records into Jira work items, sending status updates and comments back. This guide compares eight connector types side by side.
If you need a breakdown of the specifics of integrating ServiceNow and Jira (e.g., use cases and what can actually be synced between them), check out Unito’s ServiceNow-Jira integration guide.
| Connector | Direction | Who configures it | Real-time or batch | Records it pairs | Work notes, comments, attachment support | Pricing model | Who maintains it |
|---|---|---|---|---|---|---|---|
| Exalate | One-way or two-way | A ServiceNow or Jira admin | Real-time | Incidents, change requests, problems, and custom entities with Jira work items | Scripts decide which journal entries go out; attachments sync | Per item in sync; ServiceNow integrations only available with Pro and Enterprise plans | Exalate updates its connectors; your admin rewrites any Groovy scripts an API change breaks |
| Getint | One-way or two-way | An admin, with no code | Three-minute updates on Tools and Systems plans, near-real-time on Custom plan | Incidents, change requests, tasks, and bugs, with Jira work items | Attachments and comments sync | Per number of events | Getint updates its connectors; your admin fixes mappings that break |
| Zapier | One-way per Zap | Anyone | Trigger-based, intervals vary per plan | One ServiceNow table per trigger, with Jira work items | No dedicated comment or work note step; a ServiceNow attach-file action exists | Per task; ServiceNow app requires a paid plan | Zapier updates its app integrations; whoever built the Zaps fixes the ones that break |
| Unito | Two-way by default, or one-way | A ServiceNow admin connects a service account and can add an optional business rule; a Jira admin connects Jira; a Jira project admin builds the flow | Real-time | With Advanced Sync: any table the account can read and write, with any Jira work item type | Public comments and work notes, both ways; attachments copied | Per item in sync | Unito |
| Workato | One-way per recipe | Whoever builds the recipes, often an integration team | Real-time and batch triggers | ServiceNow records with Jira work items | Upload work item attachment action; comments supported | Credit-based | Workato updates its connectors; whoever built the recipes fixes the ones that break |
| MuleSoft Anypoint | Two-way, as built | MuleSoft developers | As built | Whatever the build covers | As built | Subscription by Mule Flows and Mule Messages; contact sales | Your MuleSoft team |
| ServiceNow Jira spoke | One-way by default; two-way requires a flow each way | A ServiceNow developer, in Flow Designer | Event-driven flows, plus Jira triggers | Any record your flow reads, with Jira work items | Add attachment action; comment mapping is whatever your flow writes | Subscription-based on top of a ServiceNow plan | ServiceNow updates the spoke; your team maintains flows |
| Custom build | Custom to your build | Your engineers | Whatever you build | Anything each tool’s API exposes | Depends on what you build | Engineering time, hosting, maintenance | Your engineers |
The 8 best ServiceNow-Jira connectors
Exalate: best for admins who know Groovy
Exalate is a two-way sync platform that syncs data back and forth between tools, including ServiceNow and Jira. Admins can set up Exalate by installing the app in each tool, launching the connection in one system, and approving it in the other. Exalate can sync both standard and custom work items, comment threads, and user mentions.
Exalate doesn’t just offer this simple connection. More advanced users can write and deploy Groovy scripts that execute almost any action or integration task. That can include syncing fields the baseline integration doesn’t support, restricting syncing to internal comments, and more. Exalate also has a built-in AI assistant that can draft scripts from plain-language descriptions (e.g., “write me a script that syncs Jira Epics with ServiceNow records and automatically sets the Build field”). Exalate is ISO 27001:2022 certified and can run in the cloud, on Docker, and on premises.
Exalate’s scripts are code. Someone has to build and maintain them, which means either having the technical skill to write them or experience working with AI coding tools. That typically means only a few people on your team can manage and troubleshoot more complex Exalate integrations.
Pricing for Exalate has two factors: items in sync and available integrations. The Starter and Scale plans have items-in-sync limits of 25 and 100, respectively. The Pro plan has custom items-in-sync limits, while Enterprise plans have no limit. Jira is available with all plans, but ServiceNow is only available with Pro and Enterprise plans.
Getint: best for no-code two-way sync (or one-time migrations)
Getint is a no-code integration platform that connects ServiceNow and Jira, plus 17 other tools. It supports both one-way and two-way connections, linking ServiceNow records with Jira work items, mapping fields and moving comments and attachments between them. Getint also has a migration mode for teams that only need to transfer historical records over once.
An admin can connect ServiceNow and Jira in Getint, picking the table and project they need to sync, mapping fields and statuses, then choosing integration direction, all without code.
Getint offers three plans: Tools, Systems, and Custom. The plans vary in cost and integration availability. The Tools plan is $250 a month and includes integrations for ClickUp, monday.com, Asana, HubSpot, GitHub, Zendesk, Wrike, and GitLab. The Systems plan is $480 a month and also includes integrations for Jira, Azure DevOps, ServiceNow, and Salesforce. The Custom plan includes all integrations, custom setup and deployment, and has custom pricing.
Zapier: best for simple one-way handoffs
Zapier is a one-way automation platform with integrations for thousands of apps, including ServiceNow and Jira. Users build Zaps, each with a trigger in one tool and an action in the other. For example, a Zap could automatically create a work item in Jira whenever a specific field is updated in ServiceNow.
You can build a Zap in minutes with no code or other technical skills. Zapier also has built-in templates covering popular trigger and action pairings for ServiceNow and Jira. Each Zap performs a single action, like creating a single type of work item or updating a single field when a trigger fires.
As easy as they are to build, Zaps still have their drawbacks. They only move data in one direction. Using Zapier for complex workflows involves chaining multiple Zaps to handle work item creation, updates, and comments, especially if you want to do this in both directions. That involves a longer setup time, more maintenance, and significant troubleshooting to prevent infinite loops and conflicts.
Unito: best for two-way sync without scripts
Unito is a no-code, two-way sync platform with over 60 integrations for tools like ServiceNow, Jira, Azure DevOps, Salesforce, and more. Unito users can build flows that connect one type of ServiceNow record with one type of Jira work item (e.g., ServiceNow incidents and Jira bugs). Deep rules give users control over what gets synced and when, while deep field mappings send data where it needs to go. The ServiceNow-Jira integration page lists every supported object and field type.
Two-way sync is the default for Unito flows, but users can also build one-way flows or set flow direction for individual field mappings (i.e., some are one-way and others are two-way) to match a workflow’s needs. Unito supports standard and custom fields, comments, attachments, and hierarchies (e.g., Jira epics, stories, tasks, subtasks). Once a ServiceNow admin and a Jira admin connect the accounts, a Jira project admin can build flows with no code.
Some features, like premium connectors, Advanced Sync, and a dedicated integration consultant, are only available on selected Unito Enterprise plans.
Unito has limits worth knowing before you build. In Jira, Advanced Sync doesn’t sync these field types: checkbox, labels, version, group and multi-user pickers, cascading select. Comments sync both ways, but comment edits and Jira @mentions don’t.
Workato: best for integration teams automating across many tools
Workato is an enterprise automation platform built around recipes. A trigger in one app is followed by actions in others. Workato’s ServiceNow and Jira connectors support both real-time and batch triggers, as well as actions that create and update records and upload attachments. A recipe can, for example, create a Jira epic whenever a support agent escalates a ServiceNow record.
Workato has over 1,200 connectors and its recipes can branch, transform data, and affect multiple systems. That allows integration teams to run ServiceNow-Jira recipes alongside other automations, and even have recipes that trigger actions in other tools after managing escalations from ServiceNow to Jira.
Each Workato recipe goes in one direction. Keeping a ServiceNow record and a Jira work item in sync as teams work requires a recipe for each direction (i.e., one to push data from ServiceNow to Jira and one to send data back the other way).
MuleSoft Anypoint: best for developer teams already on MuleSoft
MuleSoft’s Anypoint Platform lets developers design, build, and run integrations. This offers teams a midpoint between building a connector from scratch (described later in this list) and using a platform with pre-built connectors.
In MuleSoft Anypoint, developers build flows in Anypoint Studio, calling the ServiceNow and Jira APIs. They control integration direction, timing, data transformations, and error handling, so the integration can match almost any workflow, including one that touches systems other than ServiceNow and Jira in the same flow.
That control comes with the most setup, maintenance, and troubleshooting of any option on this list, short of a fully custom build. Developers build, test, and deploy each flow, then fix it when APIs change. Other teams can’t adjust flows on their own.
Anypoint is sold on contract, so you’ll need to reach out to its sales team for a quote.
ServiceNow Integration Hub spoke: best for ServiceNow-centric teams
ServiceNow’s Integration Hub is a platform that allows developers and engineers to set up automations between ServiceNow and other tools using spokes. Some are pre-built, meaning you only need to pay a subscription fee to access them and start using the integration. The Integration Hub also allows developers to build their own custom spokes with JavaScript and ServiceNow’s APIs.
The Integration Hub has over 180 pre-built spokes, including Jira. The integrations you build with these spokes are highly customizable, allowing for two-way sync and deep field support.
The Jira spoke needs an Integration Hub subscription on top of your ServiceNow license. Two-way sync means registering a Jira webhook against your instance and building a flow for each direction.
That said, deploying even pre-built spokes can take months, especially if you’re trying to replicate the functionality of two-way sync platforms. If you have a team dedicated to deploying, managing, and customizing Integration Hub spokes, then this is a solid option. Otherwise, it might take more resources to manage than you have available.
Custom build: best for teams with engineers to own it
Both ServiceNow and Jira have REST APIs, meaning software developers and engineers can build integrations between them from scratch or with platforms that can access these APIs (but don’t have pre-built connectors like the other platforms in this list). Custom builds give teams full control over what an integration does, and where data that it transfers is hosted. A custom integration can match a workflow exactly, rather than forcing a team to adapt its workflows to pre-built integrations.
These custom connectors have one main drawback: resources. Building an integration requires time and effort from in-house engineers or enough budget to hire outside contractors. Costs scale rapidly with either approach, consuming resources that could be dedicated to other priorities. This doesn’t end when the build’s finished. When a custom-built connector breaks, your team (or hired contractor) has to fix it. With pre-built connectors, vendors maintain and update integrations when APIs, rate limits, and authentication requirements change. The cost of these fixes adds up over time.
Integration Hub spoke or third-party connector?
When integrating ServiceNow with any other tool, there’s a question every ServiceNow admin needs to answer. Why use a third-party connector when the Integration Hub exists?
For an organization with multiple workflows centering on ServiceNow and a dedicated ServiceNow developer, the Integration Hub might be the best option to manage integrations not just with Jira, but with the rest of your stack. It requires an extra subscription, which is no different from using a third-party connector. Either way, integrations cost extra; the question is how much.
That said, deploying Integration Hub spokes can take weeks, if not months, and maintaining them is your responsibility. Most third-party connectors take less time to deploy and vendors do the bulk of maintenance and troubleshooting.
Choosing between the Integration Hub and a third-party connector comes down to how much you value customization over deployment and maintenance burden. If you want deeper customization at the cost of more troubleshooting and longer deployments, then the Integration Hub is preferable. But if you want a platform that can handle all your integrations (whether they include ServiceNow or not) and take less time to deploy, then a third-party connector is preferable.
What about other built-in integrations?
The Integration Hub isn’t the only built-in option for integrating ServiceNow and Jira. ServiceNow admins might also consider:
- Agile Development 2.0: This built-in integration allows you to build an agile software development environment into ServiceNow, integrated with Jira or Azure DevOps. That allows software development planning to happen in ServiceNow while execution happens in Jira.
- Atlassian’s ServiceNow app for Jira Service Management: This app is intended to turn ServiceNow incidents into alerts for teams in Jira Service Management (or the reverse). It’s typically used by on-call teams that need to be notified when an incident is logged in either tool. It doesn’t keep records in sync across these tools, making it narrowly suited to notifications and handoffs rather than cross-team collaboration.
These built-in integrations are more specific than Integration Hub spokes and take less time to deploy, making them uniquely suited for certain workflows. That said, this comes with limitations that make them less attractive options for other needs.
Jira Software or Jira Service Management: what changes
Most connectors list “Jira” as a single tool, but the version the Jira team uses completely changes what the integration needs to do. A Jira Software project is typically used by an engineering team receiving escalations. A ServiceNow incident becomes a bug, developers work on it, and status updates get sent back to ServiceNow automatically. A Jira Service Management project usually represents another service desk, with its own customers, its own SLAs, and its own portal.
There are other differences worth mentioning between the two platforms, which might come up when you’re integrating them:
- Jira Software has one kind of comment, visible to everyone with project access, while Jira Service Management has a “Reply to customer” type of comment that sends a notification to customers (usually by email) and shows up in a customer-facing portal.
- Developer statuses (Backlog, To Do, In Progress, Done) don’t typically match the statuses on the customer support side. Statuses in Jira Service Management tend to map more closely with those in ServiceNow.
- Engineers in Jira rarely have their own SLAs, while service desks in Jira Service Management have SLAs that run in parallel with SLAs for teams in ServiceNow.
When integrating ServiceNow with Jira, admins need to make sure they know which version of Jira that integration is handling. Otherwise, they might run into situations where an integration exposes internal comments to customers, or an integration might not handle the specific work item types admins need.
Most integration vendors handle both Jira Software and Jira Service Management, but not all of them might have the depth to handle issues like internal vs. external comments or mapping different statuses.
How do work notes and comments cross between ServiceNow and Jira?
ServiceNow has two kinds of journal entries: work notes and comments. Work notes are used for internal communication, like when agents collaborate on a support ticket. Comments are meant for all other types of communication, and callers or requesters can see them. Jira Service Management has a similar distinction: Reply to customer comments send a notification to customers while internal notes remain hidden. Jira Software, however, doesn’t have this distinction. That means replies from developers in Jira Software might accidentally get exposed to customers without the right rules in your integration. So every integration has to make two decisions:
- Which ServiceNow journal entries go out to Jira?
- Where do comments from Jira land when they reach ServiceNow?
A common setup is to sync only work notes from ServiceNow to Jira, meaning engineers don’t see customer-facing comments. Then, any replies from Jira become work notes, meaning customers and requesters don’t see them.
Not all integrations can support this distinction, however. Unito allows users to build rules that filter out either public comments or work notes, and inbound comments become work notes by default. Exalate scripts allow you to differentiate between public comments and work notes when you integrate ServiceNow with Jira. Automation platforms like Zapier, however, may not have the depth to make this distinction.
Which ServiceNow-Jira connector fits each job?
| Job to be done | Sync direction | Start with | Watch out for |
|---|---|---|---|
| Incident-to-bug escalation: a ServiceNow incident becomes a Jira bug, and status and comments come back | Two-way | A two-way sync tool like Exalate, Getint or Unito. Zapier works if you only need the bug created. | Which ServiceNow journal entries leave ServiceNow, and which Jira status moves the incident to Resolved |
| Change requests to development work: a change request becomes a Jira epic or story, and progress goes back for approval | Two-way | A two-way sync tool, or the Jira spoke if your ServiceNow team already runs Integration Hub | One change request often spans several work items. Decide which one’s status updates the change. |
| Service desk to service desk: Jira Service Management and ServiceNow, common between vendors and their clients | Two-way | A two-way sync tool that supports Jira Service Management request types | A ServiceNow work note written as a reply to the customer gets emailed to the customer. Each desk also runs its own SLA clock. |
| On-call alerting: ServiceNow incidents page a Jira Service Management team | Two-way, alert actions only | Atlassian’s ServiceNow app | It creates and closes alerts, not tickets, and supports one team per integration without code changes. |
| One-off migration: moving historical records from one tool to the other | One-way, once | Getint’s migration mode, or a script on both REST APIs | Closed records, comment history and attachments. Plan the cutover so no one works in both tools at once. |
What a custom ServiceNow-Jira connector costs to keep alive
“With Celigo, we would have to write all the code and then there’s a ton of work to maintain it. Whereas with Unito, it was as simple as clicking to connect fields between Jira and Wrike.” – Boveda case study
A custom connector doesn’t just cost a significant amount of time, effort, and money to build. It also creates maintenance and troubleshooting costs.
Built-in and third-party connectors need less maintenance from your team, because vendors handle most of it. Custom connectors have to be maintained and troubleshot by your team or the contractors you hire through API changes, rate limit updates, and similar issues. Custom object usage and new fields can involve building new capabilities into custom connectors. With a third-party connector, that kind of improvement is done for you. Additionally, when a custom-built connector breaks, it’s on you to fix it.
There’s another hidden cost most teams don’t consider. What happens when the engineer who built the connector leaves? A custom ServiceNow-Jira connector won’t fail the day an engineer leaves. It can take weeks or months before anyone notices. Something changes in the ServiceNow or Jira API, breaking the integration. An authentication token expires and no one knows how to refresh it. No matter what fails, the result is still the same. ServiceNow updates stop reaching Jira, and teams only find out when a customer calls in for an update and gets an outdated answer.
The cost then falls on whoever has to try to fix the broken connector. An engineer spends weeks going through code before they know what to change or update. Meanwhile, support agents are back to manually transferring updates between ServiceNow and Jira until the connector is back online.
Even when you build a custom connector through a vendor, if that connector requires significant scripting or coding work, you’re paying more than just a monthly subscription or yearly contract fee.
FAQ: ServiceNow-Jira connector
What tools support integrations with ServiceNow and Jira?
Many integration platforms can pair ServiceNow and Jira, including:
- Exalate
- Getint
- Zapier
- Unito
- Workato
- MuleSoft
Both ServiceNow and Jira also have built-in integrations that can pair the two.
What’s the best way to sync incidents, tasks and project updates between ServiceNow and Jira two-way?
The best way to sync incidents, tasks, and project updates back and forth between ServiceNow and Jira is using integration platforms that are built for two-way sync from the ground up, such as Exalate, Getint, and Unito.
What are the alternatives to ServiceNow Integration Hub for syncing with Jira?
The alternatives to ServiceNow Integration Hub for syncing with Jira include:
- Two-way sync platforms like Exalate, Getint and Unito.
- One-way automation tools like Workato and Zapier.
- Custom connector builds.
Is a ServiceNow-Jira connector bidirectional?
That depends on the platform used to build or deploy that connector. Some are built specifically to be two-way, like Exalate and Unito. Others, like Zapier and Workato, are built to be one-way by default, but multiple integrations can be paired to replicate two-way sync.
Is there a free ServiceNow-Jira integration?
Not for ongoing sync. ServiceNow-Jira integrations either require a paid subscription (for third-party tools) or a paid add-on on top of your tool license (for the ServiceNow Integration Hub). Unito’s ServiceNow-Jira integration guide covers the options in more detail.
Is there an Atlassian Marketplace app for connecting ServiceNow and Jira?
Yes, there are multiple Atlassian Marketplace apps for connecting ServiceNow and Jira. Exalate, Getint, Unito, OpsHub and ZigiOps all list apps there. Atlassian’s own ServiceNow integration is installed from the ServiceNow Store instead.
Ready to sync?
Get a product demo and see what Unito integrations can do for your workflows.