The Workflow Library

Library / Reporting and alerts / reporting-alerts-030

Monthly digest: net new vs churned contacts (database volume health report)

Reporting and alertsContactData Hub ProfessionalIntermediate~45 min to buildFull spec

Outcome. Once a month, an admin gets a message showing how many contacts were newly created that month against how many were marked churned, so database growth is visible as a net figure, not just a raw creation count.

Workflow map Enrollment, branches and actions at a glance reporting-alerts-030
flowchart TD
    A[Monthly schedule: 1st of month, 09:00] --> B[Report A: new contacts count, previous month]
    A --> C[Report B: churned contacts count, previous month]
    B --> D[Both reports on Monthly Database Health dashboard]
    C --> D
    D --> E[Email sent to Slack channel inbound address]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it on any portal that wants a recurring, high-level read on whether the contact database is actually growing, shrinking, or holding steady month over month.
  • UseUse it as a companion to marketing's new-contact reporting, reporting-alerts-010, which shows growth alone without a churn side.
  • SkipDo not use it if this portal has no defined way to mark a contact as churned. This fiche needs a churn signal to exist first, see Prerequisites. Building the digest without one just shows new contacts against a permanently empty churned column.
  • SkipDo not use it as the single source of truth for subscriber or customer counts if a separate billing or subscription system already tracks that number authoritatively. Treat this as a directional database-health check.
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.3 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.2 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 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.PDF, Markdown, JSON
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.