The “Find HubSpot Object and Unlink” automation rule in HubSpot for Jira lets you automatically remove a specific connection between a Jira work item and a HubSpot record – without deleting anything in either system. In this article, we walk through exactly what this rule does, a practical onboarding use case, and the complete two-part setup process so you can keep your linked records clean and focused on active work.
This is Episode 4 of our HubSpot for Jira automation rules series, where we break down each available rule end-to-end to help teams get the most out of their CRM and project tracker integration.
Watch our full walkthrough of this rule in under 4 minutes:
What the “Find HubSpot Object and Unlink” Rule Does
When something happens in Jira, such as a status change – this rule finds a specific HubSpot object (a contact, company, deal, or ticket) and removes the link between it and the Jira work item. The key distinction here is that both records stay completely intact in their respective systems. Nothing is deleted, and nothing is changed inside HubSpot or Jira itself. Only the connection between the two records is removed.
This is particularly useful for teams that want to maintain clean, relevant timelines in HubSpot without losing any historical data in either platform. The rule targets one specific linked object based on the criteria you define – it does not unlink all connected objects, just the one it finds matching your field mappings.
The Rule Name Decoded
The name “Find HubSpot Object and Unlink” has two important parts worth understanding individually:
- “Find” means the rule locates a specific HubSpot object based on the criteria you set. It’s not unlinking everything – just the one it finds.
- “Unlink” means it only breaks the connection. Nothing is deleted. Nothing is changed inside HubSpot or Jira. Both records continue to exist on their own; they just stop being connected.
This precision is what makes the rule so valuable for data hygiene – you can surgically remove outdated connections without any risk of data loss.
Real-World Use Case: Customer Onboarding Projects
To make this practical, imagine your team uses Jira to manage onboarding projects for new customers. Each onboarding project is linked to the customer’s company record in HubSpot. While onboarding is in progress, this link is valuable – it gives your team context and visibility across both systems.
But once onboarding wraps up and the Jira work item moves to a status like “Completed” or “Archived,” you probably don’t want that finished project cluttering up the customer’s HubSpot timeline anymore. This rule handles that scenario automatically. The moment the status changes, the link is removed, and the HubSpot record stays focused on active, relevant work.
This approach is especially helpful for teams that handle high volumes of projects tied to CRM records – without this automation, team members would need to manually unlink completed work items one by one, which is tedious and error-prone.
Full Setup: Two-Part Configuration
Setting up this rule follows the same two-part flow used across HubSpot for Jira automation rules. You’ll configure the rule first inside the HubSpot for Jira app, then wire it up inside Jira Global Automation.
Part 1: Setup Inside the HubSpot for Jira App
Start by opening the HubSpot for Jira configuration and navigating to the automation screen. From there, follow these steps:
- Click to create a new automation rule.
- Give your rule a descriptive name – something like “Unlink HubSpot Company When Onboarding Completes.” Keep this name handy because you’ll need it again in Part 2.
- Select that this is a Jira to HubSpot automation.
- Select the action: Find HubSpot Object and Unlink.
- Select the Jira space the rule should apply to.
- Choose the HubSpot object type to find – contact, company, deal, or ticket.
- Set up your field mappings. These mappings tell the rule how to locate the right HubSpot object to unlink. For example, you might match on a company name or domain so the rule knows exactly which connection to remove.
- Save the rule.
The field mappings are a critical step – they ensure the rule targets the correct specific record rather than unlinking the wrong object. Take care to map fields that uniquely identify the HubSpot record you want to disconnect.
Part 2: Setup in Jira Global Automation
Now jump over to Jira Global Automation and create a new automation flow:
- Pick your trigger. For this rule, status changes like “Completed” or “Archived” tend to be especially useful.
- Add an action and from the list, find HubSpot CRM for Jira.
- From the HubSpot CRM for Jira actions, choose “Find HubSpot Object and Unlink.”
- Select the specific rule you built by the name you gave it in Part 1.
- Save and enable your automation.
Once enabled, the rule will quietly run in the background, automatically removing links whenever your specified trigger conditions are met.
When to Pair This Rule With a Status-Change Trigger
While you can use various triggers for this automation, status-change triggers are the most common and practical choice. They align perfectly with natural workflow milestones – when a project is done, the link is no longer needed. Some effective trigger scenarios include:
- A Jira issue moves to “Done” or “Completed”
- A work item is transitioned to an “Archived” status
- A support ticket is moved to “Closed” after resolution
By tying the unlink action to meaningful status changes, you ensure your HubSpot records always reflect current, active relationships with Jira work items.
Important Note About the Automations Experience
This walkthrough showcases the upcoming HubSpot for Jira Automations experience, which allows you to configure your saved automation rules directly in Jira Global Automations without using web request URLs. The automation logic, use cases, and overall setup process remain largely the same as in the current version of the app. The primary difference is that the new experience simplifies configuration by eliminating the need to create and manage web request URLs.
If you’re using the current version of the app, some of the steps shown may look different and require web request URLs to achieve the same outcome. For guidance on setting up automations in the current version, please refer to the official documentation.
About HubSpot for Jira
HubSpot for Jira is built by resolution Reichert Network Solutions GmbH, a Platinum Atlassian Marketplace Partner. The app keeps your CRM and engineering tracker perfectly in sync – link issues to HubSpot records, push data both ways, automate object creation, and give every team the context they need without leaving their tool. You can install it from the Atlassian Marketplace to get started.
What’s Next in the Series
Now that you understand how to unlink a single specific HubSpot object, the next episode in the series covers “Unlink All HubSpot Objects” – a rule designed for scenarios where you need to remove every connection from a Jira work item at once rather than targeting just one.
