HubSpot workflows are the backbone of marketing automation, sales enablement, and operational processes for thousands of organizations. They run silently in the background — routing leads, sending follow-up emails, updating properties, and triggering notifications. When they work, nobody thinks about them. When they break, the consequences can go unnoticed for weeks.
A broken lead-routing workflow means sales reps never receive new leads. A failing nurture sequence means prospects drop out of your funnel without explanation. A misconfigured deal-stage automation means your pipeline reports lie to you every morning.
This guide walks you through a systematic HubSpot workflow audit, from building your initial inventory to diagnosing specific failure points to implementing ongoing monitoring. If you are conducting a broader review, this pairs directly with our ultimate HubSpot portal audit checklist.
Building Your Workflow Inventory
Before you can fix anything, you need to see everything. Most HubSpot portals accumulate workflows faster than anyone expects. A portal that has been active for two years commonly has 50-200+ workflows, and the people who built many of them may no longer be on the team.
Catalog Every Workflow
Navigate to Automation > Workflows and set the view to show all workflows. Record the following for each:
| Field | What to Record | Why It Matters |
|---|---|---|
| Name & description | Is the name descriptive enough to understand purpose at a glance? | Undocumented workflows become orphans fast |
| Status | Active, inactive, or draft | Inactive workflows may still be needed |
| Type | Contact-, company-, deal-, ticket-, or custom object-based | Determines audit scope per object |
| Created date & creator | Who built this and when? | Identifies ownership gaps when people leave |
| Last enrollment date | When did this workflow last process a record? | Stale workflows waste resources |
| Error count | Any errors in the last 30 days? | Errors above 5% need immediate diagnosis |
Identify Quick Wins
Sort your inventory to surface immediate action items:
Flag Inactive Workflows (6+ Months)
If a workflow has been off for 6+ months and nobody has asked about it, document it and mark it for deletion.
Investigate Zero-Enrollment Active Workflows
Active workflows with zero enrollments in 90 days are consuming resources but doing nothing. The enrollment trigger may be too narrow, or the workflow's purpose has expired.
Diagnose High-Error Workflows
Any workflow showing errors above 5% of total enrollments needs immediate diagnosis and remediation.
Naming Convention Cleanup
While inventorying, establish or enforce a naming convention. A workflow named “New workflow (1)” tells you nothing.
- New workflow (1)
- test workflow
- Copy of Lead nurture
- DONT DELETE
- Sarah's workflow
- [Marketing] Lead Nurture — Post-Demo Request — Email Sequence
- [Sales] Deal Stage — SQL to Opportunity — Property Update
- [Ops] Integration Sync — Salesforce Contact — Bidirectional
- [Support] Ticket Routing — Enterprise Tier — Assignment
- [Marketing] Re-engagement — 90-Day Inactive — Email Series
Use the pattern: [Department] Purpose — Trigger — Action Type. Rename workflows during the audit. Your future self — and everyone else on your team — will thank you.
Diagnosing Common Workflow Failure Points
Workflows break for predictable reasons. Once you know the patterns, diagnosing issues becomes straightforward.
| Failure Type | Healthy State | Broken State | Impact |
|---|---|---|---|
| List references | All triggers/branches reference active lists | Deleted or modified lists cause zero enrollments | High |
| Property references | All actions use current property names/values | Renamed or deleted properties cause silent failures | High |
| Integration actions | Connected apps authenticated and syncing | Disconnected apps return HTTP 4xx/5xx errors | High |
| Re-enrollment config | Re-enrollment enabled for recurring processes | Contacts only process once despite business need | Medium |
| Email actions | Templates published and current | Archived/unpublished templates cause send failures | High |
| Delay timing | Delays match current business SLAs | Outdated delays create lag in customer experience | Medium |
Deleted or Modified Lists
One of the most common failure points is enrollment triggers or branch logic that reference lists which have been deleted or significantly modified.
Lead Nurture Workflow Stops Enrolling
A marketing manager deletes a "Webinar Registrants Q3" list that was the enrollment trigger for a lead nurture workflow. The workflow remains active but enrolls zero new contacts. Sales notices a pipeline drop three weeks later.
Diagnosis: Open the workflow and check every enrollment trigger and if/then branch. Look for references highlighted in red or marked with warning icons. Cross-reference list IDs against your active lists.
Fix: Replace deleted list references with active equivalents. If the original list criteria are unknown, check with the team member who built the workflow or reconstruct based on the workflow’s documented purpose.
Changed or Deleted Properties
Property changes are the second most frequent cause of workflow failure. When a team member renames a property, changes dropdown options, or deletes a property entirely, every workflow referencing that property is affected.
Lead Scoring Breaks After Property Rename
An ops manager renames "Lead Source" to "Original Lead Source" for clarity. Twelve workflows that branch on "Lead Source" now evaluate incorrectly — all contacts route to the "None met" path. Lead routing, scoring, and attribution are silently broken.
Diagnosis: Review the workflow’s action log for specific error messages. In Settings > Properties, search for recently modified properties and cross-reference against workflow dependencies.
Fix: Update workflow actions to reference the current property name and values. If a property was deleted, determine whether it should be recreated or whether the workflow logic should be restructured. Understanding workflow dependencies is critical here.
Disabled or Disconnected Integrations
Workflows that trigger actions in external systems — sending data to Slack, creating records in Salesforce, triggering webhooks — fail when the integration is disconnected.
Slack Notifications Stop for New Deals
The Slack integration OAuth token expires. A deal-stage workflow that notifies the sales channel on every new opportunity silently fails. The sales team stops receiving real-time alerts and misses time-sensitive follow-ups for two weeks.
Diagnosis: Navigate to Settings > Integrations > Connected Apps and verify the status of every app referenced in your workflows. Check webhook URLs by testing them with a tool like Postman or curl.
Fix: Reconnect disconnected apps. Re-authenticate expired OAuth tokens. For webhook failures, confirm that the receiving endpoint is still active and accepting requests. If a third-party service has been discontinued, remove the workflow action and replace it with an alternative.
Enrollment and Re-enrollment Issues
Workflows that should process contacts repeatedly often fail because re-enrollment is not configured correctly.
- ✗Contacts only go through the workflow once despite recurring business needs
- ✗"Contact has already been enrolled" appears in enrollment logs
- ✗Expected follow-up actions never fire for returning customers
By default, HubSpot does not re-enroll contacts. If your workflow needs to fire multiple times per contact (e.g., post-purchase follow-up for repeat buyers), re-enrollment must be explicitly enabled. Be cautious — enabling re-enrollment on all criteria for high-volume workflows can cause contact fatigue.
Performance Metrics to Monitor
A workflow that is technically functional may still be underperforming. During your audit, evaluate these metrics for every active workflow.
Enrollment Rate
Compare contacts enrolled against those who meet criteria. A large gap suggests overly restrictive triggers, excessive suppression, or premature goal completion.
Completion Rate
Percentage of enrolled contacts reaching the final action. Low rates indicate unenrollment by other workflows, early goal completion, mid-sequence bounces, or excessive delays.
Error Rate
Aim for below 1% of total enrollments. Common sources: email send failures, property update issues, integration timeouts, and deleted asset references.
Time to Completion
Average time from enrollment to final action. Compare against business SLAs — a lead-routing workflow taking 48 hours defeats real-time response goals.
Workflow Health Scorecard
| Metric | Healthy | Warning | Critical |
|---|---|---|---|
| Error rate | <1% | 1-5% | 5%+ |
| Completion rate | >80% | 50-80% | <50% |
| Enrollment gap | <10% | 10-30% | 30%+ |
| Time to completion vs. SLA | Within SLA | 1-2x SLA | 2x+ SLA |
| Zero-enrollment days | 0 | 1-7 | 7+ |
Optimization Opportunities
An audit is not just about fixing what is broken. It is about finding opportunities to make your automation smarter, faster, and more efficient.
Consolidate Overlapping Workflows
Many portals have multiple workflows that do similar things for slightly different segments. If workflows follow the same structure with different content, consolidate them into a single workflow using branching logic. This reduces maintenance overhead and makes reporting cleaner.
Consolidating 5 Nurture Workflows Into 1
Instead of maintaining separate "Lead Nurture — Ebook", "Lead Nurture — Webinar", "Lead Nurture — Blog", "Lead Nurture — Demo", and "Lead Nurture — Trial" workflows, create a single workflow with branch logic based on lead source. Maintenance drops from 5 workflows to 1, and reporting shows the complete nurture picture.
Replace Workarounds with Native Features
HubSpot’s feature set evolves faster than most teams realize. Workflows built as workarounds for missing features may now have native alternatives:
- ✓Custom-coded actions (Data Hub) replace many webhook-based workarounds
- ✓Workflow extensions allow direct integration with external tools without webhooks
- ✓Calculated properties replace copy-and-set-property chains
- ✓Programmable automation handles complex conditional logic previously requiring multiple branching workflows
Add Goal Criteria
Every workflow with a conversion objective should have goal criteria defined. When a contact meets the goal (e.g., becomes a customer), they exit the workflow automatically. This prevents post-conversion contacts from receiving irrelevant nurture emails and keeps your engagement metrics accurate.
Implement Workflow Folders and Documentation
Workflow Documentation Checklist
Add internal notes to each workflow explaining: what the workflow does and why it exists, who owns it and who to contact with questions, when it was last reviewed, and any known dependencies or edge cases. Organize workflows into folders by department, campaign, or business process.
Building a Workflow Monitoring System
The most effective audit is one you never have to repeat manually. Set up ongoing monitoring to catch issues before they compound.
Weekly Error Reports
Create a recurring task to review the workflow error log every week. HubSpot does not send proactive alerts for most failure types. A 5-minute weekly scan prevents small issues from becoming big ones.
Enrollment Anomaly Detection
Establish baseline enrollment numbers for critical workflows. If a lead-routing workflow typically enrolls 50 contacts per day and drops to zero, something is wrong. Set calendar reminders to check enrollment trends monthly.
Quarterly Workflow Reviews
Revisit your workflow inventory each quarter. Check for undocumented new workflows, unexplained deactivations, and opportunities to adopt new HubSpot features.
Automate With Jetstack
For complex automation environments, Jetstack's workflow audit tools continuously scan for broken automations, orphaned dependencies, and performance degradation with automated alerting.
If your portal has more than 50 active workflows, or if your team does not have a dedicated HubSpot administrator, automated monitoring is worth evaluating. Visit our marketplace to explore audit toolkits, or contact us for a custom assessment.
Workflow Audit for Pre-Migration Scenarios
If you are auditing workflows because you plan to migrate them to another portal, the audit serves a dual purpose: fix what is broken now, and identify what is worth migrating.
- Active workflows with consistent enrollments
- Revenue-critical automations (lead routing, deal progression)
- Workflows with documented dependencies and owners
- Automations aligned with current business processes
- Workflows for expired campaigns or discontinued products
- Workarounds now replaced by native HubSpot features
- Duplicate workflows that can be consolidated
- Undocumented workflows nobody can explain
A clean source portal produces a clean destination portal. For migration-specific workflow considerations, review our HubSpot workflow migration checklist and our guide on cloning workflows within vs. cross-portal.
Pre-migration audits are one of the highest-ROI activities you can perform. Our post on how pre-migration audits save thousands breaks down the numbers.
Frequently Asked Questions
How do I find all broken workflows in HubSpot at once?
HubSpot does not have a single “show all broken workflows” view, but you can filter workflows by error status. Go to Automation > Workflows, and look for workflows with warning icons or error badges. You can also sort by error count if you export workflow data. For a comprehensive scan, Jetstack’s audit tools automatically identify all workflows with errors, orphaned references, and performance issues in a single report.
What causes a HubSpot workflow to stop enrolling contacts?
The most common causes are: the enrollment trigger references a deleted list or changed property, the workflow was accidentally turned off, a suppression list is filtering all eligible contacts, or the workflow’s goal criteria is being met before enrollment. Check each of these in order when troubleshooting enrollment drops.
Should I delete old workflows or just deactivate them?
Deactivate first, delete later. When you deactivate a workflow, its configuration and enrollment history are preserved. Set a 90-day review period — if no one needs the workflow during that time, it is safe to delete. Always document the workflow’s purpose before deleting, in case you need to recreate similar logic later.
How many workflows is too many for a HubSpot portal?
There is no hard rule, but portals with more than 100 active workflows typically benefit from consolidation. The issue is not the count itself but the maintainability. If your team cannot explain what every active workflow does and why it exists, you have too many. Focus on reducing redundancy through branching and consolidation rather than hitting an arbitrary number.
Can broken workflows affect my HubSpot email deliverability?
Indirectly, yes. Workflows that send emails to bounced contacts, disengaged segments, or incorrectly enrolled records increase your bounce and spam complaint rates. Over time, this damages your sending reputation and reduces inbox placement for all your HubSpot emails. Fixing broken email-sending workflows is a deliverability priority.
How often should I audit HubSpot workflows specifically?
Workflow-specific audits should happen quarterly at minimum. High-volume portals with 50+ active workflows benefit from monthly spot checks of error rates and enrollment trends. Any time you modify properties, delete lists, or change integrations, check dependent workflows immediately. For a full audit cadence recommendation, see our guide on how often to audit your HubSpot portal.