Start free
Per-pair page

Intercom + Jira: bug reports from chat to engineering.

Create Jira issues from Intercom conversations tagged "bug" or "feature request"; notify Intercom when the engineering fix ships. Closes the customer-to-code loop.

Connect Jira and IntercomSee reverse direction
Trigger app
Jira as the trigger

Workflows fire when something happens in Jira.

See all 6 triggers →
Action app
Intercom as the action

Workflows do something in Intercom, instantly.

See all 20 actions →
Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

Jira → Intercom

When something happens in Jira, do it in Intercom.

6 Jira triggers wired to 20 Intercom actions. Most-used pairing: Comment Created → Assign Conversation.

Intercom → Jira

Or fire it the other way around.

5 Intercom triggers wired to 17 Jira actions downstream.

See Intercom → Jira →
Popular pairings

Common Jira → Intercom workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 120 combinations
When comment created in Jira, assign conversation in Intercom.

Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.

When comment created in Jira, close conversation in Intercom.

Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.

When comment created in Jira, upsert company in Intercom.

Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.

When comment created in Jira, create contact in Intercom.

Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.

When new issue in Jira, assign conversation in Intercom.

Fires when a new issue is created in Jira. The standard inbound hook for routing, enrichment, auto-labeling, and SLA-aware notifications.

When new issue in Jira, close conversation in Intercom.

Fires when a new issue is created in Jira. The standard inbound hook for routing, enrichment, auto-labeling, and SLA-aware notifications.

When new issue in Jira, upsert company in Intercom.

Fires when a new issue is created in Jira. The standard inbound hook for routing, enrichment, auto-labeling, and SLA-aware notifications.

When new issue in Jira, create contact in Intercom.

Fires when a new issue is created in Jira. The standard inbound hook for routing, enrichment, auto-labeling, and SLA-aware notifications.

When issue deleted in Jira, assign conversation in Intercom.

Fires when an issue is deleted in Jira. Useful for audit/compliance logs and for tearing down related records in other systems.

How it works

Connect Jira and Intercom in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize Jira and Intercom

    Open TinyCommand, authorize Jira and Intercom once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Jira trigger

    Drop the Jira → Comment Created trigger onto the canvas. TinyCommand auto-registers the webhook.

    POST /v1/webhooks/jira.trigger-comment-created
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the Intercom action

    Drop the Intercom → Assign Conversation action below it. Map fields from the Jira payload into the Intercom inputs.

    intercom.assign-conversation
  5. 5
    Publish
    Publish and forget

    Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Jira + Intercom.

How do I create a Jira issue from an Intercom conversation?
Intercom Tag Added "bug" → Jira Create Issue with summary = conversation title, body = full chat history + customer info. Save Jira key to Intercom conversation as a custom attribute.
Can I notify the Intercom user when their reported bug ships?
Yes. Jira Issue Closed → look up Intercom conversation by Jira key → Intercom Add Reply with "Fix shipped in version X. Thanks for the report!". Customer-facing automation closes the loop.
How do I include customer tier in the Jira issue?
Intercom Get Contact returns custom attributes. Pass plan tier into the Jira issue description and as labels (e.g., "tier:enterprise"). Triage prioritizes accordingly.
Can I AI-classify Intercom messages before creating Jira issues?
Yes. Insert Claude/OpenAI step. Classify confirmed bug → Jira. Feature request → Linear/Notion. Account issue → routed differently. Filters non-engineering work out of the engineering tracker.
How do I avoid duplicate Jira issues from one Intercom conversation?
Trigger on tag added (manual support action), not every message. Store the Jira key on the conversation. Filter out conversations with a Jira key already set.
Can I link many Intercom conversations to one Jira issue?
Yes. AI checks new conversation against existing Jira issues. If matched, add the Intercom conversation URL as a Jira comment instead of creating a new issue. Surface "X customers want this fix".
Related

Other apps that pair well with Jira.

+
Jira + Gmail
Email
+
Jira + Slack
Communication
+
Jira + Google Sheets
Spreadsheets & Databases
+
Jira + HubSpot
CRM & Sales
+
Jira + Stripe
Payments
+
Jira + Notion
Productivity