The Workflow Library

Library / Marketing ops / marketing-ops-030

Offline/imported contact consent capture and legal basis backfill

Marketing opsContactMarketing Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. Contacts who enter the database through an import or an offline channel with no recorded legal basis get queued for a manual backfill review instead of being marketed to on an unexamined assumption of consent.

Workflow map Enrollment, branches and actions at a glance marketing-ops-030
flowchart TD
    A[Contact created via Import or Manual entry, legal_basis_type blank] --> B[Set legal_basis_backfill_status = Pending review]
    B --> C[Add to backfill queue list]
    C --> D[Create review task]
    D --> E[Notify compliance reviewer]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse whenever contacts can be created through a list import, a trade show scan, a spreadsheet upload, or a manual entry, any path that bypasses a form's own consent capture.
  • UseUse to make sure "we imported this list a while ago" never becomes the entire answer to "what is our legal basis for marketing to this contact."
  • SkipDo not use this fiche as the compliance decision itself. It only queues the review; a person with the relevant legal knowledge still decides what basis, if any, applies to each backfilled contact.
  • SkipDo not use if every contact in your portal is created exclusively through forms that already capture consent at submission. This fiche is specific to the offline and import creation paths.
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.5 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.PDF, Markdown, JSON
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.