Outcome. A contact manages email, SMS, and WhatsApp opt-in status from one preference form, and the workflow catches the cases the form alone cannot: a channel opt-in with no usable phone number behind it, and a single audit trail across all three channels.
Workflow map
Enrollment, branches and actions at a glance
marketing-ops-006
flowchart TD
A[Preference center form submitted] --> B[Set preference_center_last_submitted]
B --> C{SMS opted-in and no phone number?}
C -->|Yes| D[Notify marketing ops, create task]
B --> E{WhatsApp opted-in and no phone number?}
E -->|Yes| F[Notify marketing ops, create task]
B --> G{Any subscription type changed?}
G -->|Yes| H[Add to recent-changes list]
When to use it, when not to
- UseUse when you run marketing sends on at least two of the three channels (email, SMS, WhatsApp) and want one preference page instead of three separate unsubscribe flows.
- UseUse when SMS and WhatsApp are already connected as marketing channels in your portal, not as a way to set them up for the first time.
- SkipDo not use this if you only send marketing email. The native one-click email unsubscribe already covers that case with no workflow needed.
- SkipDo not assume WhatsApp is available on every portal. It depends on a connected WhatsApp Business Account and is limited by region and hub tier. (check in your portal: confirm WhatsApp marketing channel availability and country coverage for your account before building the WhatsApp branch)
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.10 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.
