The Workflow Library

Library / Marketing ops / marketing-ops-009

Lifecycle stage stuck-in-MQL aging alert to marketing ops

Marketing opsContactMarketing Hub ProfessionalIntermediate~25 min to buildFull spec

Outcome. A contact who sits in Marketing Qualified Lead for longer than an agreed window without moving to Sales Qualified Lead gets flagged to marketing ops, instead of quietly aging out of the funnel unnoticed.

Workflow map Enrollment, branches and actions at a glance marketing-ops-009
flowchart TD
    A[Lifecycle stage set to MQL] --> B[Reset mql_aging_alert_sent to false]
    B --> C[Delay 14 days]
    C --> D{Still MQL and not yet alerted?}
    D -->|Yes| E[Set alert sent = true]
    E --> F[Add to Stale MQLs list]
    F --> G[Notify marketing ops]
    G --> H[Create review task]
    D -->|No| I[No action, exit]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse once marketing-ops-001 (or an equivalent MQL promotion workflow) is live and MQL date is populated reliably.
  • UseUse to catch handoff failures: an MQL sales never picked up, or one sales rejected without logging a reason.
  • SkipDo not use a single aging threshold across very different lead sources if some sources have a naturally slower sales-follow-up cadence (event leads versus demo requests, for example). Segment the threshold if needed.
  • SkipDo not treat this as a replacement for a working MQL-to-SQL handoff process (marketing-ops-002). This is a safety net that catches what the handoff missed, not the handoff itself.
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.8 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.