Outcome. Marketing ops gets warned when the count of active marketing contacts approaches the plan's paid limit, ahead of an automatic overage charge, instead of finding out from a surprise invoice line.
Workflow map
Enrollment, branches and actions at a glance
marketing-ops-029
flowchart TD
A[Scheduled weekly run] --> B[Custom code: count marketing contacts, compare to plan limit]
B --> C{result_code ok?}
C -->|Yes, >=90% used| D[Send high-priority alert]
C -->|Yes, below 90%| E[No notification]
C -->|No| F[Notify: check failed]
When to use it, when not to
- UseUse on any portal billed by marketing contact tier where the count grows through ongoing list imports, reactivations, or inbound form fills without a tight manual gate on every addition.
- UseUse to give marketing ops lead time to review and prune before a tier overage, rather than reacting after the fact.
- SkipDo not use expecting a native workflow trigger tied to account-level marketing contact usage. Usage against your plan's limit is an account setting, not a property on any contact record, so no contact- or deal-based workflow can watch it directly. This fiche uses a scheduled workaround, similar in shape to marketing-ops-023's list hygiene check. (check in your portal: confirm whether your current portal exposes marketing contact usage counts through a documented API endpoint, since this has been added and adjusted across releases)
- SkipDo not use this fiche as a substitute for checking Settings > Marketing Contacts directly during any planned large import; that page is still the authoritative source for current usage and limit.
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.6 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 marketing ops 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.
