When to Manually Enroll Contacts in a Workflow (and When to Fix the Trigger)

Manual enrollment is a useful tool, but it is also a signal.

Every time someone adds contacts to a workflow by hand, the automation is either handling a genuine exception or quietly compensating for a trigger that no longer matches reality.

Knowing which situation you are in is what separates a controlled process from one that drifts.

This article covers when manual enrollment makes sense, when it masks a trigger problem, and the documented limitations to check first.

What manual enrollment actually does

In HubSpot, records are most commonly enrolled in workflows automatically based on enrollment triggers.

Manual enrollment is the alternative path: you can enroll records from within a workflow, from an object index page, from a list, or from an individual contact record.

For contact-based workflows, you can enroll contacts from a contact record or a list.

HubSpot documents these enrollment paths along with the permissions each one requires.

The key behavioral difference is that manually enrolled records do not have to meet the enrollment triggers at all.

That is the entire point of the feature, and also the reason it needs guardrails.

You are deliberately bypassing the rule the workflow was built on.

Manual enrollment also has a fixed starting point.

Manually enrolled records always start at the beginning of the workflow.

If records must start later or execute only specific steps, HubSpot recommends cloning a workflow that begins at the desired action.

Enroll records there instead. This is documented behavior, not a workaround you have to invent.

When manual enrollment is the right call

Manual enrollment earns its place in a few specific situations.

In each one, the exception is real, the reason is understood, and the trigger is not the thing that is broken.

Genuine one-off exceptions

Some contacts legitimately fall outside your criteria but still need the workflow's treatment.

A customer success manager may ask for a specific account to receive an onboarding sequence even though the account entered through an unusual channel.

The trigger is fine.

The situation is simply rare enough that writing a rule for it would add more complexity than it removes.

The test is simple: if you would not want a rule that captures this contact automatically, manual enrollment is appropriate.

If you would, the trigger needs updating instead.

Backfilling a known, reviewed group

When a workflow launches, contacts who already met the criteria before the trigger existed may need to be brought in deliberately.

Enrolling a reviewed list by hand gives you a controlled moment to do that.

You choose the list, confirm the count, and enroll.

HubSpot notes that manually enrolling many records, such as from a list, takes time to fully enroll.

Wait a few minutes before checking results. The enrollment history panel shows recent enrollments once records are processed.

The word reviewed matters.

A backfill should be a decision, not a reflex.

If the group is large and recurring, that is a sign the trigger definition is incomplete, not that you need a monthly manual ritual.

Testing before the trigger goes live

Before turning on a new workflow, enrolling a small set of internal or test contacts manually lets you verify the sequence behaves as expected.

Because manual enrollment bypasses the triggers, you can test the actions themselves without waiting for real records to qualify.

This is one of the healthiest uses of the feature, because it happens before the automation touches real customers.

When the trigger is the real problem

Manual enrollment becomes a warning sign when it turns into a pattern.

Watch for these situations.

The same type of contact keeps needing manual help

If a recognizable group of contacts regularly qualifies in your judgment but never meets the trigger, the trigger no longer reflects how leads actually behave.

Perhaps the trigger relies on a form submission, but many qualified contacts now arrive through chat or sales outreach.

Each manual enrollment patches the gap; none of them fixes it.

The fix is to revisit the enrollment triggers and align them with the current path leads take.

Update the trigger, test it against recent contacts who needed manual help, and confirm they would now enroll automatically.

Then stop enrolling that group by hand.

Manual enrollment is compensating for a data gap

Sometimes contacts do not meet triggers because a property is missing or stale, not because the criteria are wrong.

If lifecycle stage, lead source, or a custom field is not being populated reliably, the trigger evaluates incomplete data.

Manual enrollment here hides a data quality problem that will keep producing exceptions elsewhere.

In that case, fix the data pipeline or the process that populates the property.

Manual enrollment should not become the permanent bridge over broken data.

Nobody remembers why contacts were enrolled

Manual enrollment leaves less of an audit trail than a trigger change.

If team members are adding contacts to workflows and the reasoning lives only in their heads or in scattered messages, the process has drifted.

A trigger change, by contrast, is visible and reviewable.

HubSpot's revision history shows what changed in a workflow, when, and by which user, filterable by event type.

That history also supports reverting to a specific revision if a change causes problems.

If manual enrollment is frequent enough that you need this kind of traceability, that is another argument for encoding the decision in the trigger instead.

Limitations to check before enrolling manually

Manual enrollment fails quietly in several documented situations.

Before enrolling, verify the following.

• The workflow must be on. You cannot manually enroll records into a workflow that is turned off. HubSpot states this directly.
• Previously enrolled contacts need re-enrollment enabled. If a record has already gone through the workflow and re-enrollment triggers are not turned on, it will not enroll again. The enrollment history will show the record as not enrolled because re-enrollment is not enabled. This also applies to bulk enrollment from a list or index page: previously enrolled records are skipped.
• Active records cannot be enrolled. Contacts currently active in the workflow cannot be manually enrolled into it.
• Suppression and unenrollment rules apply. Records on the workflow's suppression list, or records meeting the workflow's unenrollment triggers, cannot be manually enrolled. Contacts also cannot be manually enrolled if the workflow is set to remove contacts when they no longer meet the enrollment conditions.
• Permissions matter. Super Admin or Workflows permissions are required to use the workflows tool. Users with Enroll permission only can enroll from CRM cards or record index pages. Enrolling directly from within a workflow requires View and Edit permissions. A user with Edit but no Enroll permission cannot enroll records, even while editing the workflow.

One more prerequisite is easy to miss.

The option to enroll records that currently meet the enrollment criteria will not appear after editing a trigger or when turning on a workflow.

If you expect that prompt and it is missing, check whether you have just changed the trigger or the workflow's on state.

A worked example of the decision

Consider a re-engagement workflow triggered by a contact's lead status changing to a specific value.

A sales rep reports that a contact who went quiet for months never entered the sequence, and asks for manual enrollment.

First, check the state.

The contact's lead status was updated, but the workflow was briefly off during a recent edit, so the trigger never fired.

The workflow is now on, the contact is not active in it, has never been enrolled before, and is not on the suppression list.

Manual enrollment is safe and appropriate here: the miss was a timing gap, not a criteria mismatch, and it is a single contact.

Now imagine the opposite pattern.

Over several weeks, multiple reps manually enroll contacts whose lead status was changed by a different integration than the one the trigger watches.

The criteria are not wrong; the data source feeding the property is inconsistent.

Here the right move is to fix the integration behavior or broaden the trigger to the actual source of the status change, then confirm new contacts enroll automatically.

Continuing to enroll manually would leave the root cause in place.

The decision rule in both cases: manual enrollment for isolated, understood exceptions; trigger repair for repeating patterns.

Keeping the workflow honest after manual enrollment

Manual enrollment is not a set-and-forget action.

A few habits keep it from eroding your automation.

• Log the reason. Whether in the contact record, an internal note, or a shared log, record why the contact was enrolled manually. Future audits will thank you.
• Review manual enrollments periodically. Look for repeated patterns that suggest a trigger change is overdue.
• Use revision history when triggers change. If you adjust enrollment triggers to absorb a manual-enrollment pattern, the revision history lets you see what changed, when, and by whom, and to revert if the change misfires. Note that reverts are not supported for workflows containing webhook or custom code actions; in that case, use the read-only revision as a reference to update the current workflow manually. HubSpot documents these constraints.
• Remember the starting point. Because manually enrolled records always begin at step one, do not use manual enrollment to drop contacts into the middle of a sequence. Clone a workflow that starts at the desired action instead.

Choosing between the two paths

The choice comes down to one question: is this contact an exception, or is this contact evidence?

An exception is rare, understood, and not worth writing a rule for.

Evidence is a pattern: the same kind of contact keeps missing the workflow, or the data feeding the trigger is unreliable.

In that case, fix the trigger or the data, verify with the workflow's revision history and enrollment history, and let automation do its job.

Operators who treat every manual enrollment as a prompt to ask that question end up with triggers that match reality and exception lists that stay short.

Operators who do not end up running their automation partly by hand, without realizing it.

For a broader view of how automation fits into your revenue operations, see the automation glossary entry and how automation and data sync work together across your existing tools.

How Meshline can help. Connect automation, Organic Marketing (demand generation), and customer lifecycle management (Revenue Intelligence).

Bring topic planning, content publishing and performance feedback into the conversation about your workflow. Book a Meshline demo.