Outcome. Every raw usage event landed on a dedicated custom object rolls up automatically into the company's running usage total, instead of someone manually summing event records before a renewal or health-score review.
Workflow map
Enrollment, branches and actions at a glance
renewal-expansion-042
flowchart TD
A[Usage Events record created, not yet processed] --> B[Custom code: add Event Value to company Usage Current Period]
B --> C{Rollup succeeded?}
C -->|Yes| D[Set Processed = true]
C -->|No| E[Notify operations owner: rollup failed]
When to use it, when not to
- UseUse it when raw usage events (logins, feature calls, API hits) already arrive one record at a time on a custom object, typically from an integration or a batch import, and need to become a single rolling company-level number.
- UseUse it as the data-plumbing layer underneath renewal-expansion-004's
churn risk score or renewal-expansion-030's usage spike detection, both
of which expect
Usage Current Periodto already be populated on the company. - SkipDo not use it if usage events can instead be summed with a native rollup or calculation property directly against a standard object; a custom object with a workflow is more moving parts than necessary if the source data already lives on the company or deal record.
- SkipDo not use it to process a very high daily event volume without checking your portal's custom object record and API call allowances first; a workflow enrolling once per raw event does not scale the same way a periodic batch aggregation does.
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.7 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.5 numbered actions
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 renewal and expansion 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.
