The Workflow Library

Library / Reporting and alerts / reporting-alerts-006

Disabled workflow inventory and owner nudge (automation hygiene)

Reporting and alertsContactOperations Hub ProfessionalIntermediate~45 min to buildFull spec

Outcome. Once a month, an admin gets a message listing every disabled workflow in the portal, so forgotten or paused automation gets reviewed instead of sitting disabled indefinitely.

Workflow map Enrollment, branches and actions at a glance reporting-alerts-006
flowchart TD
    A[Scheduled trigger: monthly, day 1, 08:00] --> B[Custom code: GET automation v4 flows, all pages]
    B --> C[Filter isEnabled = false]
    C --> D{Any disabled flows found?}
    D -->|yes| E[Format list sorted by last-updated, oldest first]
    D -->|no| F[Format fallback: no disabled workflows this month]
    E --> G[Send message to Slack or email]
    F --> G
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it on portals with a large or multi-team workflow library, where disabled workflows accumulate and nobody owns cleanup.
  • UseUse it before a HubSpot audit, a data migration, or a permission review, to know what automation actually exists versus what is live.
  • SkipDo not use it on small portals with fewer than about 15 workflows. A quick manual look at Automation > Workflows, sorted by status, covers the same ground faster. See Variants for the no-code version.
  • SkipDo not treat "disabled" as "safe to delete." Some workflows are disabled deliberately (seasonal campaigns, one-time migrations) and this fiche only surfaces them, it does not judge intent.
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.6 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.