Salesforce-Jira Connector: 6 Ways to Connect the Two, Compared

• Unito home /
• Blog /
• Salesforce-Jira Connector: 6 Ways to Connect the Two, Compared

Published in Software Development on 19/10/2026.

A Salesforce-Jira connector turns Salesforce cases, opportunities, or accounts into Jira work items, sending status updates and comments back. Six connector types cover most of the integration market for this pairing. This guide compares them side by side.

If you need a breakdown of the specifics of integrating Salesforce and Jira (e.g., use cases and what can actually be synced between them), check out Unito’s Jira-Salesforce integration guide.

Salesforce-Jira connectors compared

Connector	Direction	Who configures it	Real-time or batch	Field and comment mapping	When a field has no counterpart	Security review	Pricing model	Who owns maintenance
Exalate	One-way or two-way	A Jira or Salesforce admin	Real-time	Standard and custom fields, comments and attachments, scripted transformations	You write a script that converts the value or drops it	ISO 27001:2022 certified; app installed on both Jira and Salesforce	Per item in sync; Salesforce integrations only available with Pro and Enterprise plans	Exalate updates its connectors; your admin rewrites any Groovy scripts an API change breaks
MuleSoft Composer	One-way	A Salesforce admin	Polling triggers, as often as every 15 seconds	Standard fields, most custom fields	Unsupported fields can’t be mapped	Runs on the Salesforce platform under your Salesforce agreement	Per task and per connector	Salesforce updates the Jira connector; your Salesforce admin repairs each flow that stops working
Unito	Two-way by default, customizable per field	Anyone	Near-real-time	Standard and custom fields, comments, attachments, and hierarchies	Map it to a custom or text field, or leave it out of the flow	SOC 2 Type 2, GDPR and CCPA; no data stored by Unito	Per item in sync	Unito’s developers, who update the Jira and Salesforce connectors when either API changes
Zapier	One-way	Anyone	Trigger-based, intervals vary per plan	Standard fields, some custom fields, no comment or attachment support	Skip the field	Your Salesforce admin approves Zapier as an External Client App	Per task; the Salesforce app requires a paid plan	Zapier updates its app integrations; whoever built the Zaps fixes the ones that break
Peeklogic	Two-way	A Salesforce admin, with a companion app on the Jira side	Real-time	Field coverage depends on pricing tier	The field stays outside the configured mapping	Listed on AppExchange, which requires Salesforce’s security review	Per user	Peeklogic, which updates both the Salesforce package and the Jira app
Custom build	Custom to your build	Your engineers	Whatever you build	Anything both APIs expose	Your code decides	Your own security review, every release	Engineering time for the build, hosting, and maintenance costs	Your engineers, every time Jira or Salesforce changes its API

The 6 best Salesforce-Jira connectors

Exalate

Exalate is a two-way sync platform that pushes data back and forth between tools, with Salesforce-Jira is one of its most popular pairings. Setting up Exalate is simple: you install the app on each side, start the connection in one system, and approve it in the other. It can sync standard and custom Salesforce objects, comment threads, and user mentions.

Exalate allows more advanced users to write and deploy Groovy scripts that can execute almost any rule. Convert a Salesforce picklist into a Jira select list, choose Jira projects from a case field in Salesforce, restrict syncing to internal comments, and more. Exalate also offers an AI assistant, Aida, which can draft scripts from a plain-language description. Exalate is ISO 27001:2022 certified and can run on the cloud, on Docker, or on premises.

Exalate’s scripts are strong, but they’re code someone needs to maintain. Scripts require either the technical skill to write them yourself or the know-how to manage AI tools when the AI does the writing. That usually means only a few people on your team know how to manage and troubleshoot your Exalate integrations.

Pricing for Exalate has two main variables: items in sync and available integrations. The Starter and Scale plans have an items-in-sync limit of 25 and 100, respectively. The Pro plan has custom items-in-sync limits, while Enterprise plans have no limit. Additionally, not all integrations are available with all plans. Jira can be integrated with any plan, but Salesforce is only available with Pro and Enterprise plans.

Best for: Integration teams with admins who can code in Groovy or manage AI tools that do.

MuleSoft Composer

MuleSoft Composer is Salesforce’s no-code integration builder, built right into the Salesforce interface. Its Jira connector lets an admin build trigger-based flows like “when a Salesforce case status changes, create a Jira work item” or “when a Jira work item moves to Done, update the matching Salesforce case.”

Every MuleSoft Composer flow moves data in one direction, checking the source tool for the parameters outlined in the trigger and pushing updates to the destination tool. You can build two-way integrations between Salesforce and Jira, but that requires building a separate one-way flow for each direction. This approach involves more maintenance and troubleshooting than dedicated two-way sync platforms.

MuleSoft Composer can be bought through your Salesforce contract, but pricing isn’t made publicly available. Two editions are available, each capping the number of tasks that can be automated. Starter limits your integrations to 250,000 tasks across three connectors. The Plus edition is limited to 2,500,000 tasks but supports unlimited connectors.

Best for: Salesforce-centric organizations with a Salesforce admin who wants event-driven flows pushing data between Salesforce and Jira.

Unito

Unito is a no-code, bidirectional sync platform with 60+ integrations for tools like Jira, Salesforce, Trello, ServiceNow, and more. You can build a flow that connects one type of Jira work item with one type of Salesforce object, set rules for which items sync, and map fields. After launch, Unito keeps paired items up to date as you work. The Salesforce-Jira integration page lists every supported object and field type.

Two-way sync is the default for Unito, but you can also build one-way flows or set each field to two-way or one-way. Unito supports standard and custom fields, comments, attachments, and hierarchies (e.g., Jira epics, tasks, and sub-tasks). It works with Jira Cloud, Data Center, Server, and Service Management. A business user can set it up with no coding knowledge.

Unito has fewer integration options than most connectors on this list. Each flow can only pair one object type from each tool. To sync Jira work items with both Salesforce cases and opportunities, for example, you’d need two separate flows.

Best for: Workflows that require seamless collaboration between Salesforce and Jira with integrations that can be built by anyone.

Zapier

Zapier is a one-way automation platform that supports thousands of integrations, including Jira and Salesforce. With this platform, you build Zaps, which have a trigger in one tool and one (or more) actions in the other tool. For example, a Zap could create a Jira epic, named after the account, when an opportunity closes in Salesforce.

Anyone can build a Zap in minutes, and Zapier offers several templates that cover common Salesforce-Jira handoffs. Each Zap does one job, like creating one type of work item or updating one field when a specific trigger fires. That simplicity means building Zaps is faster than just about any other integration option out there.

Because each Zap can only run in one direction, keeping existing cases and issues moving in step with each other requires separate Zaps for item creation, updates, and comments in each direction. Not only does that involve a longer setup time, but it also adds significant maintenance and troubleshooting to prevent infinite loops and conflicts.

Zapier pricing scales according to the number of tasks you need, with the most affordable pricing plan starting at $29.99 for up to 750 tasks a month and scaling up to $5,099 for up to 2,000,000 tasks a month.

Best for: Simple handoffs that don’t require regular back-and-forth or complex builds.

Peeklogic

Peeklogic’s Salesforce-Jira connector, available on Salesforce’s AgentExchange marketplace, is a real-time, two-way sync platform that syncs status changes, comments, and field updates. It supports Salesforce cases, opportunities, accounts, and custom objects, showing the connected Jira issue in a panel on each record.

It’s the closest thing you can get to a native integration, allowing users to stay in a Salesforce record as they work. An admin can choose which Jira projects they connect to Salesforce and which Salesforce users can make edits to Jira data.

Peeklogic has user-based pricing, starting at $3,600 a year for the first 10 users. Larger teams pay more for Peeklogic than they would for other connectors, even with low usage.

Best for: Support agents who need Jira visibility in their Salesforce cases.

Custom build

Both Salesforce and Jira have REST APIs, meaning that software developers and engineers can build integrations between them from scratch or with any service that can access these APIs. With a custom build, you’re in full control of what your integration can do and where your data is hosted. It can match your workflows exactly, instead of forcing you to change them to fit a platform.

The main problem with this approach is resource spend. Building the integration requires time and effort from engineers, whether in-house or hired from a third party. This is often more expensive than expected and takes away resources that could have gone to other projects. Not only that, but when an integration breaks, you have to fix it. With pre-built integrations, vendors maintain and update integrations when APIs, rate limits, and authentication requirements change. Those fixes add up over time.

Best for: Organizations with a dedicated integration team and a requirement no vendor meets.

Which connector to pick for your situation

Choosing the right connector depends largely on the job it does and the sync direction you need.

Job to be done	Best sync direction	Start with	Watch out for
Support escalation: Turning Salesforce cases into Jira work items	Two-way: The Salesforce case goes to Jira, and status and questions come back	A two-way sync tool	Comment privacy; decide which comments engineering shouldn’t see on the customer side
Deal-to-delivery: A closed-won opportunity becomes a Jira epic	Mostly Salesforce to Jira, with delivery status syncing back to Salesforce	A two-way sync tool with per-field sync direction	Opportunity stages rarely match Jira statuses exactly
IT service requests: Teams ask for internal development or tech support help	Salesforce to Jira Service Management, with status updates back	A two-way sync tool that supports Jira Service Management fields	Request types and SLA fields have thinner support than standard fields
One-off migration: Moving historical records once	One way, one time	A one-way importing tool (e.g., Salesforce Data Loader or Jira’s CSV import)	Workflows that overlap both systems as you migrate

The true cost of a custom connector

“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

Most teams know that a custom connector will cost a significant amount of time, effort, and money to build. But that build isn’t the only cost you’ll incur.

For one, custom connectors require maintenance and troubleshooting. When you use a pre-built connector from a software vendor, API changes, new rate limits, and similar issues are the vendor’s to handle. Similarly, new fields, custom objects, and more are for the vendor to address. This kind of maintenance is usually done after hours, meaning it won’t impact your work or your budget. Troubleshooting is another cost the vendor takes on, both by offering customer support and by managing system-wide issues. With custom connectors, you’re the one taking on both of these tasks.

There’s another hidden cost that comes with every custom connector: what happens when the engineer who built it leaves. A custom Salesforce-Jira connector won’t fail the exact day that engineer leaves. It might take weeks or months. Something changes in Salesforce or Jira, breaking the integration. An authentication token expires and no one knows how to replace it. No matter what fails or how, the result is still the same. Jira statuses stop reaching Salesforce, and customer success only finds 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 can change a single line. Meanwhile, support agents are back to manually copying updates between Salesforce 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: Salesforce-Jira connectors

Is a Salesforce-Jira connector bidirectional?

Only some are. Exalate and Unito can both sync updates back and forth between Salesforce and Jira. MuleSoft Composer and Zapier move data one way per flow or Zap, meaning you have to manually build and pair them in each direction, which creates the risk of infinite loops and other conflicts. Other platforms tend to only push data in one direction.

Is a Jira to Salesforce connector different from a Salesforce to Jira integration?

With two-way sync platforms, there isn’t much of a difference: the terms are interchangeable. With one-way options, the main difference is where data starts and where it ends up. Some of these connectors might only be able to handle one type of pairing, so this is worth researching before you choose a platform.

Does it work with Salesforce Service Cloud and Sales Cloud?

Yes, Salesforce-Jira connectors typically work with Salesforce objects rather than product names. Cases come from Service Cloud, opportunities and leads come from Sales Cloud, and accounts and contacts are shared by both products. When researching an integration tool, check that it can support the type of object you need to sync.

Can a Salesforce-Jira connector sync comments and attachments?

This depends on the platform you use. Both Exalate and Unito can support comments and attachments. MuleSoft Composer can attach files and post comments as individual flow actions. Zapier doesn’t typically support comments or attachments.

What does a Salesforce-Jira connector cost to run per month?

This depends more on the pricing model a connector uses than anything else. Small teams will pay less for connectors that use a per-user model, while large teams with relatively low data needs will pay less with a per-task model.

The actual cost you pay can range from $29.99 a month (for Zapier’s cheapest plan) to thousands of dollars a month (for a contract with MuleSoft Composer).