Skip to content
Notis

Record HubSpot feedback from every new Jira issue

Bugs and requests carry signal about what customers actually want. Notis takes each new Jira issue and files it as a feedback submission in HubSpot, so the voice of the customer stays connected to the account rather than trapped in a ticket queue.

Trigger

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

Action

Create batch of feedback submissions

Creates a batch of feedback submissions in hubspot, ideal for bulk imports; all property names, `associationtypeid`s, and association `to id`s must reference existing entities in hubspot.

Why this helps

Customer pain is filed in Jira and never surfaces in HubSpot, so success and marketing never see the patterns.

  • Customer pain becomes visible to teams outside engineering
  • Feedback patterns build up in one place automatically
  • You avoid re-entering the same reports into two systems
  • Success conversations are grounded in real reported issues

Setup

Build it in a few focused steps.

  • 1Connect Jira and HubSpot to Notis once through the portal.
  • 2Grab your portal link from Notis and choose New Automation.
  • 3State the outcome: when a new Jira issue is created, log it as a feedback submission in HubSpot.
  • 4Choose the New Issue trigger and set the channel where Notis confirms runs.
  • 5Add a test issue and verify the feedback submission in HubSpot.

Questions about this workflow

What counts as a new issue here?

Only issues freshly created in the Jira project you configure. Edits and comments on older issues do not trigger it.

Is any manual field setup involved?

None. Notis reads the issue and creates the feedback submission from your one-line instruction.

Can several issues be logged at once?

Yes, Notis can batch feedback submissions when a burst of issues comes in, keeping everything in sync.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Jira to Hubspot. A trigger fires from one place; an action lands in another.

Jira triggers

Hubspot actions

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Add asset association

Associates an existing asset ('form', 'object list', or 'external web url') with a specified hubspot marketing campaign.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Add token to event template

Adds a new custom data token to an existing event template for a specified hubspot application, optionally populating a crm object property if objectpropertyname is provided.

ActionInstant

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

TriggerInstant

Archive email

Archives the hubspot email specified by `emailid` by moving it to the recycling bin, making it inaccessible unless restored.

ActionInstant

Archive a batch of emails by ID

Archives multiple hubspot crm emails by id; ids must exist as archiving is irreversible.

ActionInstant

Archive a batch of quotes by id

Archives a batch of existing, non-archived quotes by their ids; this action is irreversible and useful for managing outdated or irrelevant quotes.

ActionInstant

Archive batch of companies by id

Archives a batch of companies by their unique ids; targeted companies must exist, not be previously archived, and this api operation is irreversible.

ActionInstant

Archive batch of contacts by id

Archives a batch of existing contacts by their hubspot crm ids, rendering them inactive; this action is irreversible via the api and requires manual restoration or a separate unarchive endpoint.

ActionInstant

Archive batch of deals by id

Archives a batch of existing deals by their unique hubspot ids, removing them from active views and reports (soft delete); archived deals may be restorable.

ActionInstant

Connect any two apps with Notis in the middle.

Not just Jira and Hubspot. Any combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7 days free trial with 20$ free usage included.
No card. Works with personal or business Hubspot.