The Workflow Library

Library / Reporting and alerts / reporting-alerts-024

Anomaly alert: daily form submission volume drop vs 7-day average

Reporting and alertsContactData Hub ProfessionalAdvanced~70 min to buildFull spec

Outcome. Each day, an admin gets a Slack alert only when that day's form submission volume drops well below the trailing 7-day average, so a broken form or a tracking outage gets caught the same day instead of at month end.

Workflow map Enrollment, branches and actions at a glance reporting-alerts-024
flowchart TD
    A[Daily schedule: 09:00] --> B[Custom code: fetch submission counts, last 8 days]
    B --> C[Compute average of prior 7 days]
    C --> D{Yesterday below threshold and baseline met?}
    D -->|yes| E[Post Slack alert]
    D -->|no| F[Exit silently, no anomaly]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it on portals with steady daily form traffic, where a sudden drop is a meaningful signal, a form embed breaking, a page going down, or a tracking script failing.
  • UseUse it as an early-warning layer on top of, not instead of, uptime monitoring for the site itself.
  • SkipDo not use it on a portal with naturally spiky or low-volume form traffic, a handful of submissions a day. The 7-day average will be noisy and the alert will fire on ordinary variance.
  • SkipDo not use it as the only signal for a marketing campaign's health. Pair it with the actual campaign performance report for that.
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.