Overlapping enrollment triggers
Two or more workflows set to enroll contacts based on the same trigger. Same form submission. Same lifecycle stage change. Same list membership. They will both fire.
All tools01 02 03 04 05 06 07 08 09 10 More questions? See the FAQ
Tool Story
HubSpot Workflow Conflict Checker
Find out how many workflows are about to hit the same contact at once.
The problem
Someone filled out one form. They got 12 emails in their inbox within seconds.
Not because anyone wanted that to happen. Because CRO built a workflow. Growth built a workflow. Content built a workflow. Someone ran a holiday campaign and forgot to turn it off. And buried on page 8 of the workflow list was something nobody remembered creating — possibly from 2014 — still on, still firing, still enrolling contacts into emails that make no sense anymore.
HubSpot shows you your workflows in a list. It does not show you what a contact actually experiences across all of them at once.
That's the problem this tool solves.
What it does
Two things:
The Conflict Report — without needing a specific contact, scan your entire active workflow library and surface every place where two or more workflows could fire emails at the same contact within 24 hours of each other based on overlapping enrollment triggers.
The Rogue Workflow Detector — flag the workflows that are active but probably shouldn't be. The ones from three years ago nobody turned off. The holiday campaign that ran past its end date. The workflow created by someone who left the company. The ones on page 8 that everyone forgot existed.
What it flags
Conflict detection
Email collision within 24 hours
Multiple workflows sending emails to the same contact within 24 hours of enrollment. Your contact didn't sign up for a dozen emails. They filled out one form.
Same form trigger
Multiple active workflows triggered by the same form submission. Every time someone fills out that form they're enrolling in all of them simultaneously.
Same lifecycle stage trigger
Multiple workflows triggered when a contact reaches the same lifecycle stage. One stage change. Multiple workflows. Multiple email sequences. Zero coordination.
Same list membership trigger
Multiple workflows that enroll contacts when they join the same list. If the list is used across teams this is almost certainly firing more than intended.
Rogue workflow detection
Last edited over 12 months ago
Active workflows nobody has touched in over a year. The product changed. The messaging changed. The workflow didn't.
Zero enrollments in 90 days
Active workflows that haven't enrolled anyone recently. Either the trigger is broken or the workflow is orphaned. Either way it shouldn't be quietly sitting there.
Created by someone no longer in the portal
Workflows built by users who have since left the company. Nobody owns them. Nobody is monitoring them. Nobody knows what they do.
No suppression or re-enrollment limits
Active workflows with no contact suppression lists and unlimited re-enrollment. These will fire on every qualifying contact every time the trigger condition is met with nothing to stop them.
Buried workflows — page 4 or beyond
If a workflow is so far down the list that nobody ever scrolls to it it's not being actively managed. These are the 2014 workflows. These are the landmines.
Why it’s helpful
One prevented email disaster is worth more than the time it takes to run this check. Contacts who get 12 emails in two days unsubscribe. Deliverability tanks. Someone gets a very awkward reply from a prospect saying “please stop.”
This tool finds the problem before your contacts do.
On privacy and trust
Your API key is used once, per request, through a stateless proxy that logs nothing. Workflow data is analyzed in your browser and never stored on our servers. When you close the tab it’s gone.
See it
Check My Workflows — FreeUnder the hood
Next.js 14, HubSpot Workflows API, stateless server proxy, deployed as part of chelsiehodgkiss.com on Railway.
Frequently asked questions
What counts as a "rogue" workflow?
A workflow flagged on two or more signals at once: last edited over 12 months ago, no recent enrollments, buried deep in your workflow list, or created by a user no longer in your portal. Single-signal workflows are listed separately as "worth reviewing" to avoid false alarms on evergreen operational workflows.
What is a workflow conflict?
Two or more active workflows that share an enrollment trigger and could send emails to the same contact within a short window — the reason a contact sometimes gets a flood of emails from one action.
Does it turn off or edit workflows?
No. It's read-only and surfaces problems for you to review. It links you to each workflow in HubSpot so you can decide what to do.