Skip to content

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

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Enterprise

Seat pricing: Enterprise edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Sales Hub Enterprise.

Contact2 stepsUpdated for HubSpot seat pricing
OutcomeA 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 mapsales-ops-029
Contact added to the campaign static list leads to In Do not sequence list?. In Do not sequence list? leads to Yes: Skip, no enrollment; No: Enroll in sequence. Enroll in sequence leads to Set Date entered sequence. Yes No Contact added to the campaign static list In Do not sequence list? Skip, no enrollment Enroll in sequence Set Date entered sequence
Contact added to the campaign static list leads to In Do not sequence list?. In Do not sequence list? leads to Yes: Skip, no enrollment; No: Enroll in sequence. Enroll in sequence leads to Set Date entered sequence. Yes No Contact added to the campaign static list In Do not sequence list? Skip, no enrollment Enroll in sequence Set Date entered sequence

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

When to use it, when not to

Use it

  • Use 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.
  • Use 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.
Read more on when to use itShow less

Skip it

  • Do 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).
  • Do 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.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 4 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 2 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 2 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Sales ops spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library