Outcome. Every new contact gets routed into the right legal-basis review path based on how they entered HubSpot, so form signups, list imports, and integration syncs each get the documentation treatment they actually need instead of one blanket rule.
Workflow map
Enrollment, branches and actions at a glance
marketing-ops-007
flowchart TD
A[Contact created, legal basis blank] --> B{Original source?}
B -->|Form submission| C[No action, see marketing-ops-005]
B -->|Offline sources / import| D[Flag pending review, task, add to import queue list]
B -->|Integration / API| E[Flag pending review, notify with connector name]
B -->|Other/unknown| F[Flag pending review, notify for manual triage]
When to use it, when not to
- UseUse when contacts enter your portal through more than one channel (forms, CSV imports, a synced integration such as an ecommerce platform or event tool) and each channel has a different, real answer to "where did consent come from."
- UseUse as a routing and flagging layer, not as the thing that creates a lawful basis. A workflow cannot manufacture consent that was never collected; it can only sort contacts into the right review queue and hold the ones with no defensible basis.
- SkipDo not use this as a substitute for marketing-ops-005 if your primary concern is the EU/GDPR form-submission gate specifically. This fiche is broader: it also covers offline imports and integration-sourced contacts that marketing-ops-005 does not address.
- SkipDo not build this without first confirming which of your import and integration channels you can realistically document. If a channel truly has no consent record anywhere, this workflow will correctly flag it forever, that is expected, not a bug.
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.6 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.14 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.
