The Workflow Library

Library / Data quality / data-quality-011

Calculated property: days since last activity

Data qualityContactData Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. Every contact carries a current "days since last activity" number, refreshed daily, so lists and reports can sort and segment by recency without a rep doing date math.

Workflow map Enrollment, branches and actions at a glance data-quality-011
flowchart TD
    A[Daily schedule: active list members] --> B[Custom code: compute days since hs_last_activity_date]
    B --> C{Value computed?}
    C -->|yes| D[Set Days since last activity]
    C -->|no| E[Leave unchanged]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when reports, lead-scoring rules, or list segmentation need a numeric recency value instead of a raw timestamp.
  • UseUse it when the portal already has a reliable last-activity timestamp populated by engagement tracking (email opens, form submissions, calls logged, meetings booked).
  • SkipDo not use it expecting a live, real-time counter. This value only updates when the scheduled workflow runs, typically once a day; between runs it is stale by up to that interval.
  • SkipDo not use it as your only churn or engagement signal. Pair it with renewal-expansion category workflows for account-level churn scoring, this fiche is a data-quality building block, not a full churn model.
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.4 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, 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 data quality 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.