How to Use Datasets for Workflow Enrollment in HubSpot

If you’re running into limits with HubSpot workflows, even when your CRM data is clean, you’re not alone. Many teams hit a wall when trying to automate based on calculated values, such as average deal size or engagement rate. The only workaround? Export the data, crunch the numbers manually, then return to HubSpot to act. It’s slow, disconnected, and leaves too much room for error.

That’s where HubSpot datasets come in. With datasets, you can store calculated values, aggregate metrics, and business logic directly inside HubSpot, then use those fields to trigger workflows. It’s a powerful shift: workflows can finally respond to trends rather than just static record properties.

But many teams still aren’t using this feature, either because it’s new or unclear how datasets plug into automation. This guide walks you through it step by step. You’ll learn what datasets are, how enrollment works behind the scenes, how to use them across marketing, sales, and service workflows, and how to track the impact using dashboards.

Utilizing Datasets for Advanced Workflow Segmentation

Think of datasets as custom-built data views that combine CRM records, filters, and formulas in one place. You’ll find them under Operations Hub’s Data Management section, and you’ll need an Operations Hub Enterprise subscription to get started.

Here’s how they work: you select a primary object, like Contacts, Deals, or Companies, apply filters, and create calculated fields like averages or sums. Once published, these datasets become reusable across your account in reports, dashboards, and most importantly, workflow enrollment criteria.

That last part is key. Instead of relying solely on CRM properties (which don’t always capture business logic), workflows can now trigger based on dataset values, such as deal velocity averages, total revenue by company, or ticket backlog growth.

Once live, your datasets act like synced, real-time extensions of your CRM. Workflows can access fields from these datasets just as easily as native properties.

How It Works Under the Hood

Behind the scenes, datasets take raw CRM data and transform it into structured, table-style views using HubSpot’s reporting engine. They don’t create new records; they enrich your existing ones with calculated insights.

Here’s how a dataset is built:

Inputs required:

• CRM objects: Like Contacts, Companies, Deals, Activities
• Filters: Stage, lifecycle, date ranges, team, and other fields
• Calculated fields: Sums, averages, counts, or if/then logic

Outputs generated:

• A formatted dataset view stored natively in HubSpot
• Virtual fields derived from calculations or criteria
• Automatically refreshed metrics as your CRM data updates

When you use these datasets in workflows, they unlock smarter logic. Say you want to enroll companies whose deal velocity has slowed down. Instead of creating a workaround using estimated close dates, the workflow can simply check the “Average deal velocity” field from your dataset.

HubSpot handles this by treating datasets like dynamic filters, similar to CRM properties, but with refreshable views built from multiple data points. It’s CRM data, but with business logic baked in.

Main Uses Inside HubSpot

Dataset enrollment opens doors you couldn’t walk through with plain CRM fields alone. From engagement scoring to pipeline monitoring, here’s how to apply it.

Segmenting contacts by calculated engagement metrics

You’re probably tracking opens and clicks, but isolated actions don’t tell the whole story. Marketing workflows often need to trigger based on deeper engagement patterns.

Example: Build a dataset showing the average engagement rate for each contact across the last 90 days. Then trigger a workflow when that average falls below your threshold, kicking off a re-engagement campaign before a prospect goes cold.

Why it helps: You’re no longer operating off last-touch activity. Datasets let you act on engagement trends, improving timing and relevance without forcing manual calculations outside the CRM.

Enrolling companies based on aggregated deal data

Sales and RevOps teams often need to automate based on totals, not single deals. Dataset enrollment makes that possible.

Example: Aggregate all deals tied to each company from the past 6 months. Once a company’s closed-won revenue tops $100,000, trigger a workflow to notify sales leadership, reassign the account, or adjust its lifecycle stage.

Why it helps: You can now build workflows that respond to performance trends across accounts, not just single deals, keeping key accounts actively managed and aligned with current revenue.

Triggering support workflows from service volume patterns

Support success depends on proactively identifying service breakdowns. Datasets help surface those patterns.

Example: Use a dataset to calculate average ticket resolution times by category. If the average for any category exceeds your SLA threshold for two consecutive weeks, enroll a workflow that flags the service manager and suggests escalation.

Why it helps: Instead of reacting to tickets one at a time, your workflows respond to mounting service pressure, so you can solve issues before they spiral.

Common Setup Errors and Wrong Assumptions

If your dataset-based workflows aren’t firing, you’re likely running into one of a few common pitfalls.

Using unreleased datasets

Workflows only recognize datasets marked as “Published.” Draft or private datasets won’t appear in your enrollment settings.
Fix: Check the dataset’s publishing status and user permissions before building workflows.

Expecting real-time data updates

Datasets don’t update continuously. There’s a short delay between CRM changes and dataset refreshes.
Fix: Align your refresh schedule with workflow needs. Combine with native triggers if timing is critical.

Mismatched data relationships

HubSpot follows strict schema logic. Datasets that join unrelated objects will return inaccurate results.
Fix: Stick with HubSpot-supported relationships and preview results before publishing.

Treating dataset fields like permanent properties

Dataset fields look like CRM properties but behave differently; they’re dynamic and recalculated.
Fix: Use dataset fields when you need aggregated logic. Stick to native properties for static values or identity fields.

Step-by-step Setup or Use Guide

You’ll need Operations Hub Enterprise, plus permissions to create datasets and workflows. Here’s a clear setup path to get everything working.

• Define your dataset’s purpose
  
  What should the workflow respond to? Examples could include “total deal volume,” “monthly churn rate,” or “average support load.”
• Create a dataset
  
  Go to Operations Hub > Data Management > Datasets. Choose a primary object (like Deals or Contacts), then click “Create dataset.”
• Select your data sources
  
  Add linked objects as needed and apply filters to narrow down the dataset (e.g., “Deal Stage = Closed Won”).
• Add calculated fields
  
  Use options such as SUM, AVG, COUNT, and CASE to build calculated metrics. Example: “AVG(Deal velocity in days).”
• Preview your data
  
  Before publishing, confirm your dataset outputs the expected values. Double-check formatting and field labels.
• Publish your dataset
  
  Only published datasets can be referenced in workflow enrollment. Once finalized, hit “Publish.”
• Start your workflow
  
  Go to Automation > Workflows > Create Workflow. Choose the same object type used in your dataset (e.g., Company).
• Set dataset-based enrollment
  
  Switch enrollment to “based on dataset,” and choose your published dataset. Define conditions like “Average revenue > $5K.”
• Add workflow actions and test
  
  Set actions like internal notifications, contact updates, or email sends. Run test enrollments using seeded records from your dataset.
• Monitor and adjust
  
  Watch performance data inside the workflow tool and ensure your dataset refresh aligns with automation timing.

Measuring Results in HubSpot

Once everything is running, you’ll want to ensure these new workflows deliver real value. HubSpot gives you the tools to track it.

What to track:

• Enrollment volume over time
• Success rates by dataset condition
• Conversion outcomes tied to filtered records

Where to find it:

• Custom Reports: Use workflow-based filters tied to your dataset
• Dashboard Widgets: Add performance tiles for dataset refresh cycles
• Workflow Tool: Examine who enrolled, how often, and what outcomes triggered

Use this simple review checklist:

1. Are dataset refreshes happening on schedule?
2. Do enrollment counts match what you expect to see from your dataset?
3. Is there a visible change in conversion or task outcomes tied to your workflow?
4. Are calculated fields behaving reliably over time, or do they need logic revisions?

Consistency here ensures your workflows are acting on real, meaningful data, not stale or misaligned metrics.

Short Example That Ties It Together

Let’s say you’re trying to keep pipeline velocity healthy by flagging stagnating accounts.

Here’s how you’d set that up:

1. Build a dataset pulling Deal data and associating it with Companies
2. Add a calculated field for average deal velocity per Company
3. Filter only for Companies with at least one open deal
4. Publish the dataset
5. Create a workflow on the Company object
6. Set enrollment to trigger when average deal velocity crosses 45 days
7. Use the workflow to alert the owner, reassign the account, or adjust the lifecycle stage
8. Use dashboards to track how often this happens and whether post-reassignment velocity improves

This kind of automation isn’t just reactive; it helps you enforce strategic momentum across sales with zero manual effort.

How INSIDEA Helps

If you want automation that reflects the real state of your business, you’ll need more than a few clever formulas; you’ll need clean data, a mapped CRM structure, and workflows that make sense to both humans and systems.

That’s where INSIDEA comes in. We specialize in helping teams build scalable, intelligent HubSpot systems by using every tool to its fullest, including datasets.

With INSIDEA, you can:

• Launch HubSpot with trusted data and correctly designed workflows
• Maintain a healthy CRM and keep automations humming
• Build workflows that reflect true business logic, not default settings
• Align reporting and automation so your sales, marketing, and service teams actually see the same picture

Need strategic support or tactical help? Talk to INSIDEA’s HubSpot experts or explore our consulting services.