The Workflow Library

Library / Marketing ops / marketing-ops-016

Marketing contact reactivation approval workflow (cost gate)

Marketing opsContactMarketing Hub ProfessionalAdvanced~45 min to buildFull spec

Outcome. A request to bring a contact back to marketing contact status waits for a named approver before the status actually changes, so a reactivation that raises the marketing contacts bill never happens on one person's unchecked click.

Workflow map Enrollment, branches and actions at a glance marketing-ops-016
flowchart TD
    A[Reactivation request status = Requested] --> B[Create approval task]
    B --> C[Notify approver]
    C --> D{Wait until Approved/Denied, expire 5 biz days}
    D -->|Expired| E[Set status = Expired, notify requester]
    D -->|Approved| F[Set marketing contact status = Marketing contact]
    F --> G[Set reactivation_approved_date]
    G --> H[Notify requester: approved]
    D -->|Denied| I[Notify requester: denied, no change]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse when your plan is billed per marketing contact tier and more than one person can flip a contact back to marketing status.
  • UseUse when you need an audit trail of who requested a reactivation and who approved it.
  • SkipDo not use if a single admin already controls every marketing status change and volume is low. A shared checklist may be enough.
  • SkipDo not expect this workflow to physically block a direct edit to marketing contact status outside this request path. It governs one path, not the underlying field permission. See Known pitfalls.
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.11 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.