Skip to content

Monthly consent-status change compliance export/report

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Data Hub Professional.

Contact6 stepsUpdated for HubSpot seat pricing
OutcomeMarketing 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 mapmarketing-ops-032
Scheduled monthly run leads to Custom code: query property history for consent properties. Custom code: query property history for consent properties leads to result_code ok?. result_code ok? leads to Yes, change_count > 0: Send monthly compliance summary; Yes, change_count = 0: No notification; No: Notify: check failed. Yes, change_count > 0 Yes, change_count = 0 No Scheduled monthly run Custom code: query property history for consent properties result_code ok? Send monthly compliance summary No notification Notify: check failed
Scheduled monthly run leads to Custom code: query property history for consent properties. Custom code: query property history for consent properties leads to result_code ok?. result_code ok? leads to Yes, change_count > 0: Send monthly compliance summary; Yes, change_count = 0: No notification; No: Notify: check failed. Scheduled monthly run Custom code: query property history for consent properties result_code ok? Yes, change_count > 0 Send monthly compliance summary Yes, change_count = 0 No notification No Notify: check failed

When to use it, when not to

Use it

  • Use when a GDPR or similar compliance process expects evidence of consent-status changes on a regular cadence, not only on demand.
  • Use as a lighter-weight companion to a full audit log tool, for portals that do not have one.
Read more on when to use itShow less

Skip it

  • Do 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.
  • Do 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)
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 4 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 6 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 4 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV, code

The properties JSON creates the fields in one call. The workflow JSON documents the build. The custom coded action ships as a ready-to-paste .js file.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Marketing ops spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library