Start free
Per-pair page

HubSpot + Jira: customer requests into engineering tickets.

Create Jira issues from HubSpot tickets or feature-requested deals; notify HubSpot when a customer-tagged Jira issue closes.

Connect Jira to HubSpot — start free See reverse direction
Trigger app
Jira as the trigger

Workflows fire when something happens in Jira.

See all 6 triggers →
Action app
HubSpot as the action

Workflows do something in HubSpot, instantly.

See all 23 actions →
Connect Jira to HubSpot — start free
Both directions

Pick the way that fits your stack.

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

Jira → HubSpot

When something happens in Jira, do it in HubSpot.

6 Jira triggers wired to 23 HubSpot actions. Most-used pairing: Comment Created → Create Company.

HubSpot → Jira

Or fire it the other way around.

18 HubSpot triggers wired to 17 Jira actions downstream.

See HubSpot → Jira →
Popular pairings

Common Jira → HubSpot workflows.

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

Showing 9 of 138 combinations
When comment created in Jira, create company in HubSpot.

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 HubSpot.

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 deal in HubSpot.

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 note in HubSpot.

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, create company in HubSpot.

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 HubSpot.

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 deal in HubSpot.

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 note in HubSpot.

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, create company in HubSpot.

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 HubSpot in five steps.

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

  1. 1
    Connect
    Authorize Jira and HubSpot

    Open TinyCommand, authorize Jira and HubSpot 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 HubSpot action

    Drop the HubSpot → Create Company action below it. Map fields from the Jira payload into the HubSpot inputs.

    hubspot.create-company
  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 + HubSpot.

How do I create a Jira issue from a HubSpot ticket?
HubSpot Ticket Created tagged "needs-eng" → Jira Create Issue with summary = ticket subject, description = ticket body + customer context. Save Jira key to a HubSpot custom field.
Can I notify HubSpot when a Jira issue closes?
Yes. Jira Issue Closed → look up HubSpot ticket by Jira key → HubSpot Update Ticket with status = "fixed" + Create Note on the linked contact. Customer-success automation closes the loop.
How do I push HubSpot customer tier into the Jira issue?
HubSpot Get Contact returns custom properties. Pass plan tier into Jira issue body and as labels (e.g., "tier:enterprise"). Triage prioritizes by customer impact.
Can I create Jira issues from HubSpot feature-request deals?
Yes. HubSpot Deal with custom "Feature Request" field set → Jira Create Issue in product backlog with description = request + linked HubSpot deal URL.
How do I avoid duplicate Jira issues from HubSpot?
Store the Jira key in a HubSpot custom field on the ticket/deal. Filter the trigger to only fire when the Jira key is empty. Existing tickets update their linked Jira issue instead.
Can I aggregate HubSpot deals by linked Jira issue?
Yes. Jira issue can be linked to many HubSpot deals/tickets. Track in a separate Sheet/Airtable. Surface as "X customers want this feature" for product prioritization conversations.
Related

Other apps that pair well with Jira.

+
Jira + Gmail
Email
+
Jira + Slack
Communication
+
Jira + Google Sheets
Spreadsheets & Databases
+
Jira + Stripe
Payments
+
Jira + Notion
Productivity
+
Jira + Airtable
Spreadsheets & Databases
Connect Jira to HubSpot — start free