The Workflow Library

Library / Sales ops / sales-ops-029

Bulk-enroll a static list of contacts into a sequence to kick off a campaign

Sales opsContactSales Hub EnterpriseSimple~15 min to buildFull spec

Outcome. A curated list of contacts, built once (an event list, a re-engagement segment, an imported set), enrolls into a sequence in one pass instead of a rep clicking "enroll" one contact at a time.

Workflow map Enrollment, branches and actions at a glance sales-ops-029
flowchart TD
    A[Contact added to the campaign static list] --> B{In Do not sequence list?}
    B -->|Yes| C[Skip, no enrollment]
    B -->|No| D[Enroll in sequence]
    D --> E[Set Date entered sequence]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it for a one-time push: a conference list import, a segment pulled together for a specific campaign, or a re-engagement batch that does not need ongoing automatic enrollment.
  • UseUse it when every contact on the list shares an owner assignment already, or when the sequence's sender logic (see sales-ops-001's owner-based sending) can resolve a sender for each of them.
  • SkipDo not use it for an ongoing, always-on enrollment need; a static list is a one-time snapshot. If new contacts should keep entering the same sequence as they qualify, use an event-based or active-list-based workflow instead (see sales-ops-001).
  • SkipDo not use it without checking the list for contacts already active in another sequence; those will not enroll (a contact can only be in one sequence at a time), and the workflow does not alert you to the skip on its own.
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.2 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 sales 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.