The Workflow Library

Library / Marketing ops / marketing-ops-049

Time-bound list membership (auto-remove after N days)

Marketing opsContactMarketing Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. Contacts added to a time-sensitive static list, a promotion, a limited campaign window, a temporary suppression, get removed automatically after a set number of days, so the list stays an accurate current snapshot instead of a growing pile nobody remembers to clean up.

Workflow map Enrollment, branches and actions at a glance marketing-ops-049
flowchart TD
    A[Contact added to time-bound list] --> B[Set list_expiry_date = today + window]
    B --> C[Wait until today = list_expiry_date]
    C --> D[Remove from the time-bound list]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse for any static list whose membership is only supposed to be meaningful for a fixed window, for example a 30-day promotion audience, a 14-day temporary suppression during an issue, or a 90-day trial-follow-up window.
  • UseUse to avoid the common failure mode where a temporary list becomes a permanent one because removal was never automated.
  • SkipDo not use for lists meant to be permanent records. A list of "webinar attendees, Q3 2026" should stay as a historical record, not auto-clear.
  • SkipDo not use on active lists. Active lists already auto-manage membership based on their own criteria and do not accept manual add/remove workflow actions the way static lists do.
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.2 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.3 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.