AppsPricingBlogTry it
Jira logo
HubSpot logo

Connect Jira to HubSpot

Use 4 documented Jira triggers to run 24 documented HubSpot actions.

4 source triggers
24 target actions
Reverse direction supported

Why Connect Jira & HubSpot?

Start with a Jira event

Choose from 4 documented triggers, including New Event, New Issue Created Event (Instant), New Issue Deleted Event (Instant).

Run a HubSpot action

Send the event into one of 24 documented actions, such as Add Comment, Add Contact to List, Add Note to Contact.

Map and review the workflow

Choose the fields and conditions for the workflow, then test the result before activation.

Available Triggers & Actions

Jira logo

Jira

Triggers (4)

New Event

Emit new event when an event with subscribed event source triggered, See the documentation

webhook
New Issue Created Event (Instant)

Emit new event when an issue is created. Note that Jira supports only one webhook, if more sources are needed please use New Event source and select multiple events.

webhook
New Issue Deleted Event (Instant)

Emit new event when an issue is deleted. Note that Jira supports only one webhook, if more sources are needed please use New Event source and select multiple events.

webhook
New Issue Updated Event (Instant)

Emit new event when an issue is updated. Note that Jira supports only one webhook, if more sources are needed please use New Event source and select multiple events.

webhook

Actions (24)

Add Attachment To Issue

Adds an attachment to an issue. See the documentation

Add Comment To Issue

Adds a new comment to an issue. See the documentation

Add Multiple Attachments To Issue

Adds multiple attachments to an issue. See the documentation

Add Watcher To Issue

Adds a user as a watcher of an issue by passing the account ID of the user, For example, 5b10ac8d82e05b22cc7d4ef5, If no user is specified the calling user is added. See the documentation

Assign Issue

Assigns an issue to a user. See the documentation

Check Issues Against JQL

Checks whether one or more issues would be returned by one or more JQL queries. See the documentation

Count Issues Using JQL

Provide an estimated count of the issues that match the JQL. See the documentation

Create Custom Field Options (Context)

Create a context for custom field options. See the documentation.

Create Future Sprint

Creates a future sprint. See the documentation

Create Issue

Creates an issue or, where the option to create subtasks is enabled in Jira, a subtask. See the documentation

Create Jira Version in Project

Creates a project version. See the documentation

Delete Project

Deletes a project. See the documentation

Get All Projects

Gets metadata on all projects. See the documentation

Get Board

Returns the board for the given board ID. See the documentation

Get Cloud ID

Gets the cloud ID and details of all accessible Jira Cloud sites. See the documentation

Get Current User

Returns the authenticated Jira user's account ID, display name, email, and active status. Call this first when the user says 'my issues', 'assigned to me', or needs their Jira identity. Use the returned accountId with **Search Issues with JQL** (e.g. assignee = '{accountId}') or **Assign Issue**. Requires a Cloud ID to identify the Jira site. See the documentation.

Get Issue

Gets the details for an issue. See the documentation

Get Issue Picker Suggestions

Returns lists of issues matching a query string. See the documentation

Get Issue Types

Gets the available issue types. If a project ID is provided, returns issue types for that project. Otherwise, returns all issue types accessible to the user. See the documentation

Get Sprint

Returns the sprint for a given sprint ID. See the documentation

Get Task

Gets the status of a long-running asynchronous task. See the documentation

Get Transitions

Gets either all transitions or a transition that can be performed by the user on an issue, based on the issue's status. See the documentation

Get User

Gets details of user. See the documentation

Get Users

Gets the details for a list of users. See the documentation

HubSpot logo

HubSpot

Triggers (12)

Deleted Blog Posts

Emit new event for each deleted blog post.

polling
New Company Property Change

Emit new event when a specified property is provided or updated on a company. See the documentation

polling
New Contact Added to List

Emit new event when a contact is added to a HubSpot list. See the documentation

polling
New Contact Property Change

Emit new event when a specified property is provided or updated on a contact. See the documentation

polling
New Custom Object Property Change

Emit new event when a specified property is provided or updated on a custom object.

polling
New Deal In Stage

Emit new event for each new deal in a stage.

polling
New Deal Property Change

Emit new event when a specified property is provided or updated on a deal. See the documentation

polling
New Email Event

Emit new event for each new Hubspot email event.

polling
New Email Subscriptions Timeline

Emit new event when a new email timeline subscription is added for the portal.

polling
New Engagement

Emit new event for each new engagement (call, email, meeting, note, postal mail, or task) created. Per-activity docs: Calls Emails Meetings Notes Postal Mail Tasks See the documentation

polling
New Events

Emit new event for each new Hubspot event. Note: Only available for Marketing Hub Enterprise, Sales Hub Enterprise, Service Hub Enterprise, or CMS Hub Enterprise accounts

polling
New Form Submission

Emit new event for each new submission of a form.

polling

Actions (24)

Add Comment

Adds a comment to a thread. See the documentation

Add Contact to List

Adds a contact to a specific static list. See the documentation

Add Note to Contact

MCP and AI agents: **Prefer this action** when the user wants to **leave a note on a HubSpot contact** using a **contact ID** and note text. Exposes only hubspot, contactId, and noteBody (no engagement-type step, no reloadProps, no dynamic HubSpot schema fields). Do **not** use **Create Engagement** for this workflow. For every writable note property or non-contact associations, use **Create Note** instead. See the documentation

Archive Thread

Archives a thread (soft delete). The thread is hidden from active views but can be restored via the HubSpot UI or by listing archived threads. See the documentation

Batch Create Companies

Create a batch of companies in Hubspot. See the documentation

Batch Create or Update Contact

Create or update a batch of contacts by its ID or email. See the documentation

Batch Update Companies

Update a batch of companies in Hubspot. See the documentation

Batch Upsert Companies

Upsert a batch of companies in Hubspot. See the documentation

Clone Marketing Email

Clone a marketing email in HubSpot. See the documentation

Clone Site Page

Clone a site page in Hubspot. See the documentation

Create a New Workflow

Create a new workflow. See the documentation

Create Association

Create an association (link) between two CRM records. For example, associate a contact with a company, a deal with a contact, or a ticket with a company. Common association type IDs: contact→company (1), company→contact (2), deal→contact (3), contact→deal (4), deal→company (5), company→deal (6), ticket→contact (15), contact→ticket (16), ticket→company (26), company→ticket (25). See the documentation

Create Associations

Create associations between objects. See the documentation

Create Blog Post

Creates a new blog post in HubSpot. See the documentation

Create Communication

Create a WhatsApp, LinkedIn, or SMS message. See the documentation

Create Company

Create a company in Hubspot. See the documentation

Create Contact Workflow

Create a contact workflow in Hubspot. See the documentation

Create CRM Object

Create a new CRM record (contact, company, deal, ticket, etc.). Pass property values as a JSON object in the properties parameter. Use **Search Properties** to discover available fields for the object type, **Get Properties** to find valid enum values (e.g. lifecyclestage, dealstage), and **List Pipelines and Stages** to find valid pipeline/stage IDs for deals and tickets. Use **List Owners** to find valid hubspot_owner_id values. See the documentation

Create Custom Object

Create a new custom object in Hubspot. See the documentation

Create Deal

Create a deal in Hubspot. See the documentation

Create Engagement

Create a **task, meeting, email, call, or note** engagement with optional associations. Set **Engagement Type** and pass engagement fields in **Object Properties** (HubSpot property names, e.g. hs_note_body for notes). No reloadProps step and no **CONFIGURE_COMPONENT** requirement: association fields accept raw HubSpot IDs (use **Search CRM** or the Associations API to resolve associationType when needed). For **only** a note on a contact by ID, **Add Note to Contact** (hubspot-add-note-to-contact) is still simpler. See the documentation

Create Form

Create a form in HubSpot. See the documentation

Create Landing Page

Create a landing page in Hubspot. See the documentation

Create Lead

Create a lead in Hubspot. See the documentation

Integration Features

4 documented Jira triggers
24 documented HubSpot actions
Configurable field mapping
Conditional workflow steps
Execution monitoring
A supported HubSpot to Jira direction

Capability Examples

Jira trigger → HubSpot action

Catalog example
JiraJira

New Event

HubSpotHubSpot

Add Comment

HubSpot trigger → Jira action

Reverse direction
HubSpotHubSpot

Deleted Blog Posts

JiraJira

Add Attachment To Issue

How It Works

1

Connect Apps

Authenticate your Jira and HubSpot accounts

2

Choose a Trigger

Select a documented Jira event

3

Choose an Action

Select the documented HubSpot operation to run

Test and Review

Verify field mapping and provider responses before activation

Frequently Asked Questions

Integration Benefits

Trigger-driven Workflows

Start the supported direction from one of 4 documented Jira triggers.

Automated Actions

Run one of 24 documented HubSpot actions after the selected trigger fires.

Provider Authentication

Review the authentication requirements published by each provider before activating the workflow.

Guided Configuration

Select a documented trigger, choose a target action, and map the fields required by the workflow.

Field Mapping

Map the fields exposed by the selected trigger and action, then review the required provider inputs.

Execution Review

Test the workflow and review provider responses before relying on it in production.

HubSpot logoJira logo

Reverse Integration Available

Also connect HubSpot to Jira for bidirectional automation

View Integration
Jira logo

All Jira Integrations

Explore all available Jira connections

View All Integrations
HubSpot logo

All HubSpot Integrations

Explore all available HubSpot connections

View All Integrations

Ready to Connect Jira & HubSpot?

Build this supported workflow in Mazaal AI and test it with your own provider accounts.

Get Started Free