How to Use Intercom with Atlassian: Setup, Workflows & Tips
How to Use Intercom with Atlassian: Setup, Workflows & Tips
Support teams and engineering teams often work in separate tools, and the handoff between them is where customer issues stall. Intercom handles customer conversations and tickets; Atlassian's Jira tracks the engineering work that fixes the underlying problems. Connecting the two turns a manual copy-paste handoff into a two-way sync, so agents can escalate without leaving the Inbox and engineers can see customer context without switching tools.
This guide covers the two official integration paths, how to set each one up, the workflows they unlock, and the limitations to plan around.
Why connect Intercom with Atlassian?
First viewport screenshot of www.atlassian.com.
Intercom is an AI-first customer service platform built around an omnichannel inbox, AI-powered ticketing, and Fin, its AI Agent. Atlassian's suite—Jira, Confluence, Jira Service Management, Trello, Loom, and Rovo—is built for organizing and completing shared work. The overlap is the handoff point: a customer reports a bug or requests a feature, support triages it, and engineering needs to act.
Without an integration, that handoff looks like this: an agent copies the customer's details into a Jira issue, pastes a link back into the conversation, and then manually checks Jira for status updates. Context gets lost, customers get stale answers, and agents spend time on tool-switching instead of support.
With the integration, the same handoff becomes:
- A ticket in Intercom automatically creates a linked Jira issue, with fields mapped to your project.
- Notes and comments sync in real time, so the agent sees engineering progress inside the Inbox.
- Status changes in Jira flow back to the Intercom ticket, which can trigger an update to the customer.
Atlassian itself runs Intercom for sales and support across products like Opsgenie and Statuspage, using the platform's API to enrich conversation views with data from other tools. That pattern—support tool as the front door, engineering tool as the back office—is exactly what the integration formalizes.
The two integration paths: which one do you need?
There are two official ways to connect the products, and they solve different problems.
| Jira for Tickets app | Jira Cloud app (Intercom for Jira) | |
|---|---|---|
| Primary use | Sync Intercom tickets with Jira issues automatically | Link conversations to Jira work items and see context in Jira |
| Where it lives | Intercom App Store; sidebar in the Inbox | Atlassian Marketplace; panel inside Jira |
| Automation | Basic and Custom automations, including workflow templates | Manual linking plus context display |
| Best for | Support teams that want ticket-to-issue sync at scale | Engineering teams that want conversation context next to their work |
If your goal is automated escalation from support to engineering, start with the Jira for Tickets app. If your goal is giving engineers visibility into customer conversations while they work in Jira, the Marketplace app is the better fit. Many teams install both—but see the troubleshooting section below, because running both can produce duplicate notes.
Setting up the Jira for Tickets app
Step 1: Install and authorize
In Intercom, open the App Store, find the Jira for Tickets app, and select Install now. Authorize access to your Intercom workspace, then review and accept the permissions requested on the Atlassian side. You will need admin rights on both platforms to complete this step.
Step 2: Choose your automation type
The app offers two automation modes:
- Basic automation — a simple toggle that creates a Jira issue whenever a matching Intercom ticket type is created. You pick the Jira project, map Intercom ticket types to Jira issue types (multiple mappings are supported), and optionally enable real-time syncing of ticket notes and Jira comments.
- Custom automation — five prebuilt Jira workflow templates that you can edit in the Workflows builder. Use these when you need conditional logic, such as routing different ticket types to different projects or passing specific attributes into Jira.
Step 3: Map fields and required attributes
In Custom automations, the action step controls what data is sent to Jira. Use the attribute selector to choose fields. Fields marked with an asterisk are required—if they are empty, the Jira issue will fail to create. Some fields accept JSON, which is useful for structured data like labels or custom fields.
Step 4: Test before going live
Set the workflow live, then create a test ticket that matches your trigger conditions. Open the action detail page and check the logs tab. A successful run shows a 200 status and a new issue in your Jira project. If the action did not trigger, confirm the workflow is live and that the audience and branch filters match your test ticket.
Step 5: Pin the sidebar app
In the Inbox, open the right sidebar, click Edit apps, find Jira for Tickets, and pin it. Agents can then create a new Jira issue or link an existing one directly from a ticket, and see the issue key, type, status, and assignee without leaving Intercom.
Setting up the Atlassian Marketplace app
Atlassian product interface.
The Intercom for Jira app from the Atlassian Marketplace takes the opposite approach: it puts Intercom conversation, user, and company details next to Jira work items. Install it from the Marketplace, connect your Intercom workspace, and link conversations to issues from the Jira side. This is the lighter-weight option when your engineers live in Jira and mainly need context, not automated ticket creation.
Practical workflows the combination solves
First viewport screenshot of www.atlassian.com.
Bug escalation with a two-way status loop
A customer reports a checkout error in the Messenger. The agent converts the conversation to a ticket, and Basic automation creates a Jira issue in the payments project. As engineering moves the issue through review and QA, each status change writes a note back to the Intercom ticket. When the fix ships, the agent sees the update in the Inbox and replies to the customer with a specific answer instead of a generic "we're looking into it."
Tracker tickets for widespread incidents
When many customers report the same outage, a tracker ticket acts as a parent record. Link many customer tickets to one tracker ticket, link the tracker to a single Jira issue, and bulk-update all linked customer tickets from one place when the Jira issue changes. This avoids dozens of duplicate Jira issues for one root cause.
Back-office tickets for cross-team work
A back-office ticket is an internal Intercom ticket customers cannot see. Use it to coordinate between internal teams: a customer ticket can link to several back-office tickets, each linked to its own Jira issue. When a back-office ticket's status changes, the customer ticket updates too—giving you a clean chain from customer conversation to internal work to engineering fix.
Routing and handover
Atlassian's own support team used Intercom views and teams to build a first-responder queue and region-specific views, which helped them sustain a first-response time of two to three minutes across time zones. The same pattern works alongside Jira: route incoming tickets by type, auto-assign them, and only escalate to Jira when engineering action is genuinely required.
Limitations and troubleshooting
Plan for these known constraints before you roll the integration out broadly:
- Conversations are not tickets. The Jira for Tickets app cannot create issues directly from conversations. Convert the conversation to a ticket first, or use the Jira Cloud app instead.
- Email routing needs a ticket. Emails forwarded into Intercom will not trigger issue creation until they become tickets.
- Duplicate notes. If both the Jira Cloud app and the Jira for Tickets app are installed, you may see duplicate notes tagged
[jira for intercom tickets]. Uninstall one, weighing which capability you need more. - Attachments do not sync reliably. Images in Intercom notes are not copied to Jira, and Intercom file links are secured and time-limited. Upload files directly in Jira or host them at a public URL.
- Priority defaults. If Jira issues default to Medium priority regardless of Intercom settings, check your field mapping in the automation action.
- Reauthorization. The connection may require reauthorization after 365 days; put a calendar reminder in place so syncs do not silently fail.
For a broader look at how shared inboxes support this kind of routing discipline, see our guide to the shared team inbox.
How to decide whether the integration is worth it
First viewport screenshot of www.atlassian.com.
The combination pays off when support and engineering share a recurring handoff—bugs, feature requests, or incidents—and the cost of that handoff is visible in response times or customer satisfaction. It pays off less when escalations are rare or when engineering already works inside Jira Service Management and receives requests there.
If you are still evaluating your support platform, our comparison of Intercom vs Zendesk AI Agents covers how AI resolution and helpdesk integration differ, and our roundup of the top AI agent platforms for customer support puts the options side by side.
Related reading
- Intercom vs Capacity vs Hesk: CX Automation Platform Showdown - Compare Intercom, Capacity CX Automation Platform, and Hesk on AI, pricing, and ticketing. Find the best fit for your support team.
- Intercom vs Olark: AI Agent vs Live Chat for Marketing Funnels - Compare Intercom's AI-first customer service platform with Olark's live chat and chatbot. See which fits your support and marketing funnel needs.
- eesel AI Review 2026: Pricing, Fit & Real Trade-offs - Evidence-based eesel AI review covering ideal users, use cases, strengths, limitations, pricing signals, setup effort, and decision criteria for 2026.
Sources and further reading
- Jira for Tickets app - Use this article to install the Jira for Tickets app, configure automated syncing between Intercom tickets and Jira issues, create or link Jira issues from the Inbox, and troubleshoot common issues.
- Atlassian powers sales and support at scale with Intercom - With Intercom powering Atlassian's sales and support, the team is empowered to create delightful experiences for its 200,000+ customers and drive growth across all areas of the business.
FAQ
Does Intercom integrate natively with Jira?
Yes. Intercom offers a Jira for Tickets app inside its App Store for ticket-to-issue syncing, and Atlassian lists an Intercom for Jira app on its Marketplace for linking conversations to Jira work items. Both are official integrations.
Can I create a Jira issue directly from an Intercom conversation?
Not with the Jira for Tickets app, which requires a ticket. Convert the conversation to a ticket first, or use the Jira Cloud app, which supports creating issues from conversations.
Do Jira comments sync back to Intercom?
Yes, if you enable real-time syncing of Intercom ticket notes and Jira issue comments in the automation settings. Status updates from Jira also add a note to the Intercom ticket.
What is a tracker ticket in Intercom?
A tracker ticket is a parent record that groups multiple related customer tickets under one issue. It lets you link many customer tickets to a single Jira issue and bulk-update them when the issue changes.
How much does the integration cost?
The apps themselves are free to install. You pay for your Intercom plan—seats range from $19 to $132 per seat per month depending on tier, with Fin AI Agent priced per outcome at $0.99—plus your existing Atlassian subscription. Intercom offers a 14-day cardless free trial.
Conclusion
Intercom and Atlassian solve different halves of the same problem: Intercom owns the customer conversation, and Atlassian owns the work that resolves it. The Jira for Tickets app closes the loop with automated ticket-to-issue sync and two-way notes; the Marketplace app gives engineers conversation context inside Jira. Start with one path, test it on a single ticket type, and expand once the sync is reliable. The result is fewer manual handoffs, faster answers to customers, and a support team that can see exactly where every escalation stands.