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 HubSpot and Jira See reverse direction

Trigger app

HubSpot as the trigger

Workflows fire when something happens in HubSpot.

See all 18 triggers →

Action app

Jira as the action

Workflows do something in Jira, instantly.

See all 17 actions →

Both directions

Pick the way that fits your stack.

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

HubSpot → Jira

When something happens in HubSpot, do it in Jira.

18 HubSpot triggers wired to 17 Jira actions. Most-used pairing: New Company → Add Comment.

Jira → HubSpot

Or fire it the other way around.

6 Jira triggers wired to 23 HubSpot actions downstream.

See Jira → HubSpot →

Popular pairings

Common HubSpot → Jira workflows.

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

Showing 9 of 306 combinations

When new company in HubSpot, add comment in Jira.

Fires when a new company is created in HubSpot. Use to enrich the company with firmographic data, mirror to your data warehouse, or run account-matching against parent records.

When new company in HubSpot, add watcher in Jira.

Fires when a new company is created in HubSpot. Use to enrich the company with firmographic data, mirror to your data warehouse, or run account-matching against parent records.

When new company in HubSpot, assign issue in Jira.

Fires when a new company is created in HubSpot. Use to enrich the company with firmographic data, mirror to your data warehouse, or run account-matching against parent records.

When new company in HubSpot, create issue in Jira.

Fires when a new company is created in HubSpot. Use to enrich the company with firmographic data, mirror to your data warehouse, or run account-matching against parent records.

When company deleted in HubSpot, add comment in Jira.

Fires when a company is deleted in HubSpot. Useful for audit logs or for tearing down related records in other systems.

When company deleted in HubSpot, add watcher in Jira.

Fires when a company is deleted in HubSpot. Useful for audit logs or for tearing down related records in other systems.

When company deleted in HubSpot, assign issue in Jira.

Fires when a company is deleted in HubSpot. Useful for audit logs or for tearing down related records in other systems.

When company deleted in HubSpot, create issue in Jira.

Fires when a company is deleted in HubSpot. Useful for audit logs or for tearing down related records in other systems.

When company property changed in HubSpot, add comment in Jira.

Fires when a specific company property changes in HubSpot. Use a property filter to react only on changes you care about (e.g. lifecycle stage).

How it works

Connect HubSpot and Jira in five steps.

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

1
Connect
Authorize HubSpot and Jira
Open Tiny Command, authorize HubSpot and Jira once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a HubSpot trigger
Drop the HubSpot → New Company trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/hubspot.trigger-company-created
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
Action
Add the Jira action
Drop the Jira → Add Comment action below it. Map fields from the HubSpot payload into the Jira inputs.
jira.add-comment
5
Publish
Publish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about HubSpot + Jira.

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.

Other apps that pair well with HubSpot.

HubSpot + Gmail

HubSpot + Slack

Communication

HubSpot + Google Sheets

Spreadsheets & Databases

Spreadsheets & Databases

Wire HubSpot to Jira in 2 minutes.

Free tier available. No credit card. No onboarding call.

Try for free Request a demo

HubSpot + Jira: customer requests into engineering tickets.

Pick the way that fits your stack.

When something happens in HubSpot, do it in Jira.

Or fire it the other way around.

Common HubSpot → Jira workflows.

Connect HubSpot and Jira in five steps.

Questions about HubSpot + Jira.

Other apps that pair well with HubSpot.

Wire HubSpot to Jira in 2 minutes.

Be the first to know what's next.