Skip to content

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

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
OutcomeEach 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 mapreporting-alerts-024
Daily schedule: 09:00 leads to Custom code: fetch submission counts, last 8 days. Custom code: fetch submission counts, last 8 days leads to Compute average of prior 7 days. Compute average of prior 7 days leads to Yesterday below threshold and baseline met?. Yesterday below threshold and baseline met? leads to yes: Post Slack alert; no: Exit silently, no anomaly. yes no Daily schedule: 09:00 Custom code: fetch submission counts, last 8 days Compute average of prior 7 days Yesterday below threshold and baseline met? Post Slack alert Exit silently, no anomaly
Daily schedule: 09:00 leads to Custom code: fetch submission counts, last 8 days. Custom code: fetch submission counts, last 8 days leads to Compute average of prior 7 days. Compute average of prior 7 days leads to Yesterday below threshold and baseline met?. Yesterday below threshold and baseline met? leads to yes: Post Slack alert; no: Exit silently, no anomaly. yes no Daily schedule: 09:00 Custom code: fetch submission counts, last 8 days Compute average of prior 7 days Yesterday below threshold and baseline met? Post Slack alert Exit silently, no anomaly

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

When to use it, when not to

Use it

  • Use 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.
  • Use it as an early-warning layer on top of, not instead of, uptime monitoring for the site itself.
Read more on when to use itShow less

Skip it

  • Do 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.
  • Do not use it as the only signal for a marketing campaign's health. Pair it with the actual campaign performance report for that.
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

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