Outcome. Once a week, the admin team gets one Slack message listing which workflows had errors in the past week, so a broken action gets caught during a routine check instead of only when someone complains a record was missed.
Workflow map
Enrollment, branches and actions at a glance
reporting-alerts-033
flowchart TD
A[Scheduled trigger: Monday 08:00] --> B[Custom code: fetch all flows]
B --> C{Per-flow error signal available?}
C -->|yes| D[Sort by error count, keep errors > 0]
C -->|no| E[Fallback: list flows, flag stats unavailable]
D --> F{Any flows with errors?}
F -->|yes| G[Format error list]
F -->|no| H[Format: no workflow errors this week]
G --> I[Post to Slack]
H --> I
E --> I
When to use it, when not to
- UseUse it on a portal with more than a handful of active workflows, where nobody has time to open each one's History tab weekly.
- UseUse it as a companion to reporting-alerts-006 (disabled workflow inventory) and reporting-alerts-007 (duplicate trigger detection) for a fuller monthly-plus-weekly automation hygiene routine.
- SkipDo not treat the error counts here as a full incident report. This digest tells admins WHICH workflows had errors, not the individual failed record or the root cause; both still need a manual look in that workflow's own History.
- SkipDo not use it if the portal's error rate is already visible another way, for example an existing BI pipeline exporting workflow execution logs.
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.
