Skip to content
The Workflow Library
Get the full library

Duplicate trigger detection across workflows (automation hygiene)

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Data Hub Professional.

Contact1 stepUpdated for HubSpot seat pricing
OutcomeOnce a month, an admin gets a report of workflows that enroll on the same object type with the same trigger property and condition, so overlapping automation gets reviewed before two workflows fight over the same record.
Workflow mapreporting-alerts-007
Scheduled trigger: monthly, day 1, 08:00 leads to Custom code: list all enabled flows. Custom code: list all enabled flows leads to Custom code: fetch full definition per flow. Custom code: fetch full definition per flow leads to Build comparison key: object type + normalized trigger criteria. Build comparison key: object type + normalized trigger criteria leads to Group flows by key. Group flows by key leads to Any group has 2+ flows?. Any group has 2+ flows? leads to yes: Format duplicate groups list; no: Format fallback: no duplicate triggers found. Format duplicate groups list leads to Send message to Slack. Format fallback: no duplicate triggers found leads to Send message to Slack. yes no Scheduled trigger: monthly, day 1, 08:00 Custom code: list all enabled flows Custom code: fetch full definition per flow Build comparison key: object type + normalized trigger criteria Group flows by key Any group has 2+ flows? Format duplicate groups list Format fallback: no duplicate triggers found Send message to Slack
Scheduled trigger: monthly, day 1, 08:00 leads to Custom code: list all enabled flows. Custom code: list all enabled flows leads to Custom code: fetch full definition per flow. Custom code: fetch full definition per flow leads to Build comparison key: object type + normalized trigger criteria. Build comparison key: object type + normalized trigger criteria leads to Group flows by key. Group flows by key leads to Any group has 2+ flows?. Any group has 2+ flows? leads to yes: Format duplicate groups list; no: Format fallback: no duplicate triggers found. Format duplicate groups list leads to Send message to Slack. Format fallback: no duplicate triggers found leads to Send message to Slack. yes no Scheduled trigger: monthly, day 1, 08:00 Custom code: list all enabled flows Custom code: fetch full definition per flow Build comparison key: object type + normalized trigger criteria Group flows by key Any group has 2+ flows? Format duplicate groups list Format fallback: no duplicate triggers found Send message to Slack

When to use it, when not to

Use it

  • Use it on portals maintained by more than one admin over time, where a new workflow can duplicate an older one nobody remembers still exists.
  • Use it after a merger of two HubSpot portals, an agency handoff, or any event that combines automation built by different people.
Read more on when to use itShow less

Skip it

  • Do not expect this to catch every kind of conflict. It flags workflows sharing the same enrollment property and condition; it does not simulate execution order or detect action-level conflicts (for example two workflows both trying to set the same property to different values).
  • Do not run this as a substitute for reading workflow logic during a real audit. Treat matches as a shortlist to review manually, not a final verdict.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 4 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 1 numbered action

Each action in order with its parameters, branches and delays.

Known pitfalls · 5

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 2 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV, code

The properties JSON creates the fields in one call. The workflow JSON documents the build. The custom coded action ships as a ready-to-paste .js file.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Reporting and alerts spec

Not the workflow you needed?

More in Reporting and alerts

50 specs in this section

See all 50 This category, 39 EUR
FreeSlack alert: deal marked Closed Won (revenue milestone notification)Deal4 steps Disabled workflow inventory and owner nudge (automation hygiene)Contact1 step Stage-entry timestamp properties for pipeline velocity reportingDeal5 steps Timeline note logging on critical property change (audit visibility)Deal2 steps

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library