Outcome. Once 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 map
Enrollment, branches and actions at a glance
reporting-alerts-007
flowchart TD
A[Scheduled trigger: monthly, day 1, 08:00] --> B[Custom code: list all enabled flows]
B --> C[Custom code: fetch full definition per flow]
C --> D[Build comparison key: object type + normalized trigger criteria]
D --> E[Group flows by key]
E --> F{Any group has 2+ flows?}
F -->|yes| G[Format duplicate groups list]
F -->|no| H[Format fallback: no duplicate triggers found]
G --> I[Send message to Slack]
H --> I
When to use it, when not to
- UseUse it on portals maintained by more than one admin over time, where a new workflow can duplicate an older one nobody remembers still exists.
- UseUse it after a merger of two HubSpot portals, an agency handoff, or any event that combines automation built by different people.
- SkipDo 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).
- SkipDo 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.
The preview ends here. Six sections are in the library.
counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.4 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.1 numbered action
Known pitfallsTraps seen in production, each with what breaks and what to do instead.5 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library,
149 EUR
or the reporting and alerts pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.
