Skip to content
Notis

Record HubSpot feedback when a Jira issue is reopened

A reopened issue is a warning sign. Notis picks up the change in Jira and records it as feedback in HubSpot, so repeat problems build a visible history on the account and your team can step in before frustration turns into churn.

Trigger

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.

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

Issues get reopened in Jira while the customer record stays clean, so nobody notices an account heading for trouble.

  • Recurring problems become visible against the right account
  • Success sees churn risk building before it is too late
  • No manual note-taking to connect Jira churn signals to HubSpot
  • You catch dropped balls that used to go unnoticed

Setup

Build it in a few focused steps.

  • 1Connect Jira and HubSpot to Notis once in the portal.
  • 2Ask Notis for your portal link and choose New Automation.
  • 3Describe it plainly: when a Jira issue is reopened or changed, log it as feedback in HubSpot.
  • 4Select the Updated Issue trigger and pick your run-report channel.
  • 5Reopen a test issue and confirm the feedback submission in HubSpot.

Questions about this workflow

Can I limit this to reopened issues only?

Yes. Describe the change you care about in your instruction and Notis will interpret the update that way.

Does editing a comment trigger it?

No. Comment activity is excluded. The trigger fires on field changes to the issue.

Is field mapping required?

No. Notis creates the feedback submission from your single plain-language instruction.

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.