The Workflow Library

Library / Marketing ops / marketing-ops-032

Monthly consent-status change compliance export/report

Marketing opsContactData Hub ProfessionalIntermediate~40 min to buildFull spec

Outcome. Marketing ops gets one monthly summary of every consent-status change in the portal, ready to hand to legal or compliance without manually exporting contact history.

Workflow map Enrollment, branches and actions at a glance marketing-ops-032
flowchart TD
    A[Scheduled monthly run] --> B[Custom code: query property history for consent properties]
    B --> C{result_code ok?}
    C -->|Yes, change_count > 0| D[Send monthly compliance summary]
    C -->|Yes, change_count = 0| E[No notification]
    C -->|No| F[Notify: check failed]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse when a GDPR or similar compliance process expects evidence of consent-status changes on a regular cadence, not only on demand.
  • UseUse as a lighter-weight companion to a full audit log tool, for portals that do not have one.
  • SkipDo not use expecting a native workflow trigger that fires "on any property change, portal-wide, summarized." Standard contact-based workflows only see one record at a time; this fiche uses a scheduled, portal-wide check, the same shape as marketing-ops-023 and marketing-ops-029.
  • SkipDo not use this report as your sole legal record of consent. Keep the underlying property history as the authoritative source; this digest is for visibility, not evidence by itself. (check in your portal: whether your legal team accepts this digest as supplementary rather than primary evidence)
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.