What This Update Actually Is
HubSpot updated the Create Association workflow action on April 13, 2026. Before this change, the action could only create an association between the enrolled record itself and another object type.
Now it goes one layer deeper. You can tell the action to operate on the records already associated with the enrolled object. HubSpot gives you six targeting options to control exactly which related records get selected.
Those six options are:
- All associated records (up to the 100 most recently associated)
- Most recently updated
- Most recently created
- First created
- Most recently associated
- First associated
- Associated records with a specific label
This works inside every workflow type where the Create Association action already exists. No new workflow types were added; the existing action just got a lot smarter.
Why HubSpot Shipped This
The old version of this action treated each enrolled record as an island. You could connect the enrolled record outward, but you couldn't reach through it to connect records that already lived in its web of relationships.
That gap forced revenue teams to build workarounds. We've seen portals where admins used multi-step workflows, custom properties as temporary flags, and even manual data imports just to connect a ticket's contacts to a deal. It was slow, fragile, and hard to audit.
The internal frustration was real. Humans who knew the relationship existed in the CRM still had to take manual action to make the system reflect that reality. This update closes that gap.
How to Use It Step by Step
HubSpot's setup is straightforward. Here's how to configure it:
- Open or create a workflow that supports the Create Association action (ticket-based, contact-based, deal-based, etc.).
- Add or edit the Create Association action inside the workflow.
- Find the "Objects to associate from" field. Click "More data" to expand all available options.
- Select your targeting option: all associated records, a specific recency filter, or records with a specific association label.
- Choose the matching property HubSpot will use to identify which records to connect to the target object.
- Save and test with a known record before enabling enrollment at scale.
HubSpot's own release notes walk through the full UI path at the source URL cited below this article. Always test on a small batch before opening the floodgates to re-enrollment.
What It Touches in Your HubSpot Strategy
This isn't a cosmetic tweak. It changes the surface area of what's automatable across your entire portal.
Service Hub teams can now auto-associate escalated ticket contacts to open deals, keeping sales and service aligned without a daily manual sync. Sales Hub teams can use deal-based workflows to pull in all contacts associated with a company and connect them to a new deal the moment it's created. Marketing Hub teams running campaign-based segmentation can use association labels to ensure only the right contacts get tied to specific campaign objects.
Key Takeaway
Association labels are now a first-class automation trigger. If your portal doesn't use labeled associations yet, this update is a strong reason to start. Labels let you target specific relationship types instead of grabbing every associated record indiscriminately.
This update also has quiet implications for data quality. We regularly see portals where related records exist but aren't formally connected, which means reports miss revenue attribution, lifecycle stage automation misfires, and humans fall through the cracks. Automating association creation based on existing relationships is one of the cleanest ways to fix that without a full data migration.
If you're not sure how many disconnected records are living in your portal right now, the HubSpot portal audit checklist is a good place to start. Association gaps show up repeatedly as a root cause of broken reporting and misfiring automations.
Key Takeaway
The 100-record cap on "all associated records" is the one hard limit here. If a single enrolled record has more than 100 associated records of the target type, only the 100 most recently associated will be processed. Design your enrollment criteria and targeting logic with that ceiling in mind.
This update is a concrete example of what shared CRM data can actually do when it's wired correctly. If you want the strategic framing for why this matters beyond individual workflows, this article on shared data as a HubSpot superpower explains the bigger picture.
Who Should Care Most
Not every update is for everyone. This one has a clear target audience.
- RevOps leads and HubSpot admins who manage multi-object workflows and are tired of patching association gaps manually.
- Service teams running ticket-based workflows where escalations need to automatically surface related deal or contact data.
- Sales ops leaders building deal-based automation that needs to pull in contacts from a parent company or a related object at deal creation.
- Growing companies on Smart CRM Professional or Enterprise who are starting to use association labels and want to make them do real automation work.
- Marketing ops humans using campaign objects who need contacts associated to campaigns automatically based on existing relationships, not manual list pulls.
If your portal runs mostly single-object workflows with simple enrollment criteria, this update won't change your day-to-day much. If you're managing complex, cross-hub automations, it's a meaningful unlock.
George's Take
I've audited hundreds of HubSpot portals over the years, and one of the most consistent problems I see is what I call "relationship debt": records that are logically connected in the real world but structurally disconnected inside the CRM. That disconnect doesn't just create messy data. It causes broken reports, missed handoffs, and frustrated humans who can't figure out why their automation isn't working. This update from HubSpot is a direct answer to that problem. It lets your workflows reflect the relationships that already exist, instead of forcing your team to manually close a gap the system should have closed automatically. If you're not already using association labels strategically, this is your sign to start. The combination of labels plus this new targeting option is one of the most powerful workflow configurations HubSpot has shipped in a while.
“Relationship debt is one of the most expensive problems in a HubSpot portal. This update lets your workflows pay it down automatically.”
This update fits into a broader pattern of HubSpot making the CRM object model do more work automatically. If you want the full picture of what HubSpot shipped in April 2026 and how the pieces connect, check out our April 2026 update roundup.
If you want help mapping this action into your existing workflows, or if you're not sure where your association gaps live, let's talk. A focused strategy session with the Sidekick team can surface exactly where this update pays off in your portal. Book a strategy call at sidekickstrategies.com and we'll dig in together.
Frequently Asked Questions
What does the updated Create Association workflow action do in HubSpot?
The updated Create Association action lets you target records already associated with the enrolled object, not just the enrolled record itself. You can select which associated records to act on using filters like most recently created, first associated, or a specific association label, giving you far more control over multi-object relationship automation.
Which HubSpot hubs and tiers include this association workflow update?
This update is available in Marketing Hub, Sales Hub, Service Hub, Data Hub, and Smart CRM, all at Professional and Enterprise tiers. It works in every workflow type where the Create Association action was previously available.
What's the limit on how many associated records this action can process?
When you select "All associated records," HubSpot processes up to the 100 most recently associated records. If an enrolled record has more than 100 associated records of the target type, only the 100 most recent will be included. Design your targeting logic with this ceiling in mind.
Can I use association labels to filter which records the workflow targets?
Yes. One of the six targeting options is "Associated records with a specific label." This lets you narrow the action to only records carrying a particular association label, which is useful when you need to distinguish between relationship types, like a primary contact versus a billing contact on a deal.
What's a practical example of how to use this workflow action?
A common use case is a ticket-based workflow. When a support ticket is escalated, the workflow finds all contacts associated with that ticket and automatically associates them to a related deal using a matching property. This keeps sales and service aligned without any manual record linking.
Do I need to rebuild existing workflows to take advantage of this update?
You don't need to rebuild from scratch. The new targeting options appear inside the existing Create Association action. Open any workflow using that action, click into the action settings, expand the "Objects to associate from" field with "More data," and you'll see the new options available to configure.
