Find HubSpot Object and Unlink

Extended Use Case

Remove CRM visibility when issue becomes irrelevant

Sometimes a Jira work item:

• No longer applicable

• Is marked Duplicate

• Turns out to be internal-only

• Was logged incorrectly

• Should not be customer-visible anymore

If it remains linked:

• Sales may escalate unnecessarily

• Customers may see irrelevant activity

• CRM becomes noisy

This rule safely removes the association when a defined condition is met.

About this rule

The keyword here is Unlink, not delete. This rule removes the association between one HubSpot object and the work item. The HubSpot record itself stays exactly where it is.

Video walkthrough

A short walkthrough of the Find HubSpot Object and Unlink rule, covering both the setup in the app and the flow in Jira.

Part one: inside the HubSpot for Jira app

Open the HubSpot for Jira Configuration, go to the Automation screen, and create a new automation rule.

1. Give your rule a name. Make it descriptive. You will need to find it again by name when you build the Jira flow, so make it easy to recognise.

2. Select that this is a Jira to HubSpot Automation.

3. Select the action, in this case Find HubSpot Object and Unlink.

4. Select the Jira space the rule should apply to.

5. Choose the HubSpot object type to unlink: Contact, Company, Deal or Ticket.

6. Set up your identifier mapping. This is how the rule finds the right record, so it matters. Under Find the HubSpot <object> where these field values match, choose the Jira source field and the HubSpot unique field to match it against. The list offers the object’s default unique property – Email for Contact, and the object name for Company, Deal and Ticket – plus any HubSpot property marked as requiring unique values. See below.

7. Save the rule.

Choosing which HubSpot property the rule matches on

Every object type has a default unique property: Email for Contact, and the object name for Company, Deal and Ticket – Company Name, Deal Name and Ticket Name. The default is no longer the only choice.

Any HubSpot property can be offered to the rule by marking it as unique in HubSpot. When you create or edit a property, tick Require unique values for this property. HubSpot allows up to ten unique properties per object type.

In HubSpot, tick Require unique values for this property when creating or editing the property.

The property then appears in the rule’s HubSpot unique field list alongside the default. Under Find the HubSpot object where these field values match, choose the Jira source field to take the value from, and the HubSpot unique field to match it against.

The HubSpot unique field list shows the default identifier plus any property marked as requiring unique values.

Part two: inside Jira Global Automation

1. Go to Jira Global Automation and create a new automation flow.

2. Pick your trigger, for example Status changed, for example to Done.

3. Add an action and, from the list, find HubSpot CRM for Jira.

4. From the HubSpot CRM for Jira actions, choose Find HubSpot Object and Unlink.

5. Select the specific rule you just built, by the name you gave it earlier.

6. Save and enable your automation.

Outcome

• The Jira work item disappears from the HubSpot timeline.

• CRM remains clean.

• Revenue teams only see relevant engineering activity.