HubSpot Workflows: Types, Setup and 10 Practical Examples

HubSpot workflows automate actions when CRM records meet enrollment criteria. Start with four useful jobs: route an incoming lead, update its lifecycle stage, catch missing owners and flag overdue follow-up. Define who should enter, what should happen and when a record should leave before building the automation.

Need HubSpot workflows built, fixed or documented? I set up and clean up workflow automation for small and growing teams. See automation services or book a 30-minute call.

What HubSpot workflow automation is actually for

The point of HubSpot workflow automation isn't to automate everything that can be automated. It's to remove the specific manual steps that are slow, error-prone, or easy to forget when a human is doing them under time pressure: routing a lead to the right owner, updating a lifecycle stage when a deal moves, nudging a rep when a hot lead goes quiet for three days.

Anything beyond that, automation aimed at persuading rather than routing, starts crossing into marketing automation territory, which has its own rules about not annoying the person on the other end.

Types of HubSpot workflows

A HubSpot workflow is a set of automated actions that runs when a record meets the enrollment rules you define. The workflow type is decided by the kind of record it enrolls:

• Contact-based workflows enroll people. They handle most marketing and lead management work: welcome emails, lead routing, lifecycle stage updates and follow-up tasks.
• Company-based workflows enroll organisations. Use them for account ownership, account-level scoring or alerts when a target account shows activity.
• Deal-based workflows enroll deals. Use them to create tasks when a deal changes stage, notify managers about large or stalled deals and keep deal properties up to date.
• Ticket-based workflows enroll support tickets. Use them to route tickets, set priorities and remind the team before a response is overdue.

Depending on your subscription, you may also see workflows for other objects such as quotes, conversations or custom objects. Start with the record the work is really about: if the action concerns a person, use a contact workflow; if it concerns a sale, use a deal workflow.

HubSpot workflows vs sequences: which should you use?

Choose a workflow for a CRM process; choose a sequence for a rep's personal follow-up. Both automate steps, but the record, sender and stopping rule matter more than the fact that an email is involved.

Sources: HubSpot's workflow action reference and sequence setup and unenrollment guide. Sequence access requires an assigned Sales or Service seat with an eligible Professional or Enterprise subscription.

Workflows can also enroll contacts into sequences, but the general Enroll in a sequence workflow action requires Sales or Service Hub Enterprise. Professional accounts can use the sequence tool's embedded automation for supported triggers. Check HubSpot's automation requirements before designing that connection.

The HubSpot CRM lead management workflows worth building first

Before anything fancy, HubSpot CRM lead management needs four workflows that most portals are missing at least one of: lead routing by territory or source the moment a form submits, lifecycle stage updates that fire off real behavior instead of being set by hand, an owner-assignment fallback so leads don't sit unassigned over a weekend, and a stale-lead alert that flags anything untouched for a set number of days. For a seller-acquisition application, use the speed to lead for motivated sellers guide to define response ownership and escalation.

Use these as design examples, then adapt the rules to your own lead definitions and the actions available in your subscription.

For example, write the routing rule as: new sales enquiry + territory known + owner missing → assign the territory owner and create one follow-up task. Send missing-territory cases to a review queue. This is an illustrative operating rule, not a claim about a client result or a ready-to-import template.

A complete illustrative HubSpot lead-routing build

This hypothetical build expands the routing example above. It assigns an unowned sales enquiry to a territory rep or a backup, then creates one internal task. It sends no prospect email and makes no claim about client results. The custom property names and operating deadlines below are illustrative, not HubSpot defaults.

Object and prerequisites

Create a contact-based workflow named Sales | Contact | Enquiry routing | v1. Choose the actual users who will act as the North rep, South rep and backup. Assign a named sales-operations owner and a review date in the workflow description.

• Sales enquiry: the specific form to monitor. Map its territory field to a custom contact dropdown named Sales territory, with North, South and Other options. A blank value must remain eligible for fallback review.
• Routing eligibility: a custom dropdown with Eligible and Excluded values. The agreed lead process must populate it before routing; customers, closed enquiries and disqualified contacts are Excluded. A blank value needs human review and does not qualify.
• Internal/test record: a custom Yes/No field populated by the intake process. Production records must explicitly be No. A missing value does not qualify, and the form must not overwrite exclusion flags on existing contacts.
• Contact owner: use the existing owner property. Inventory other workflows and integrations that write it. Give this routing job one writer rather than allowing competing assignments.

Enrollment, exclusions and repeat rules

Use filter-based enrollment with one AND group: the contact has submitted the specific Sales enquiry form on any page AND Routing eligibility is Eligible AND Internal/test record is No. Do not require a territory or a missing owner in enrollment; the branches handle those cases.

Add a suppression segment for Routing eligibility = Excluded OR Internal/test record = Yes. For this filter-based build, enable removal when a contact no longer meets eligibility conditions. Keep automatic re-enrollment off. These controls follow HubSpot's contact unenrollment settings.

At activation, select future qualifying records only. Audit old submissions separately before any manual enrollment. A repeat enquiry from the same contact is a new request for the existing owner to review, not permission to run this first-assignment workflow again.

Branches and actions, in order

1. Allow form data to settle. Add a five-minute delay before evaluating territory. HubSpot recommends this buffer when a branch depends on a property update from a form. Recheck eligibility = Eligible and Internal/test record = No after the delay; otherwise end the path.
2. Preserve ownership. Branch on Contact owner is known. End that path without reassignment or a new task. Only the owner-missing path continues.
3. Route by territory. Add an AND/OR branch: Sales territory = North, then South, then None met. In each path, use Edit record to set Contact owner to the selected North rep, South rep or backup respectively. The fallback covers Other and blank territory.
4. Create the handoff. In each assigned path, check that Contact owner is known. If it is, use Create task, associate it with the enrolled contact and assign it to that owner. Use the title Review sales enquiry, or Review sales enquiry and confirm territory for fallback, with an illustrative due date of one day after creation. If the owner is still missing, send an internal notification to the named operations owner and end without creating an unassigned task.
5. Finish and inspect. End after the task. Check the task action's actual result and the created task's association, assignee and due date. A later property change must not be treated as proof that task creation succeeded.

Builder references: branches and form-update timing, Edit record configuration, task fields, and workflow task and notification actions. Repeat the task configuration under each territory path. An owner check cannot protect against a competing update between steps, so resolve other owner-writing automations before launch.

Expected test outcomes

Use previews first, then verify execution with controlled test records in an isolated copy. Inspect the first real enrollments after launch. If an action fails, repair only the missing work after checking history; manually rerunning the entire workflow can repeat earlier actions. Use the marketing automation workflow troubleshooting guide to work through broader failure patterns.

6 more HubSpot workflow examples by team

Once the four lead management workflows are stable, these illustrative design examples are common next steps. Each one should have a clear owner and a way to measure whether it helped.

• Marketing: new subscriber welcome. A contact joins the newsletter list, receives one welcome email with the most useful resource, and is tagged with the topic they signed up for.
• Marketing: content follow-up. A contact downloads a guide. After an illustrative three-day delay, branch on a confirmed booking: if booked, stop; otherwise send one related resource only if the contact is eligible for that marketing email. Recheck subscription and consent requirements immediately before sending. A download is not evidence of permission or qualification.
• Sales: meeting booked handoff. A meeting is booked, the owner receives a task with the form answers and recent page views, and the lifecycle stage moves forward only when the meeting is held.
• Sales: deal stage tasks. A deal enters a stage such as proposal sent, and the owner gets a dated follow-up task so no proposal sits without a next step.
• Sales: closed lost nurture. A deal is marked closed lost for a timing reason, and the contact is added to a low-frequency nurture with a check-in task months later.
• Service: ticket response reminder. A high-priority ticket enters a delay matching the agreed response deadline. Then branch: if the required human response is recorded or the ticket is closed, stop; otherwise notify the ticket owner and team lead once. Use a defined response field or event, not unrelated contact activity, as the stopping condition.

Before any marketing-email action in these examples, check HubSpot's recipient requirements, including marketing contact status, subscription and applicable communication consent. Meeting attendance and qualification need explicit evidence before any stage change.

How to set up automation workflows in HubSpot

1. Check access. The full workflows tool requires an eligible subscription and appropriate permissions. Available actions vary by plan.
2. Open Automation → Workflows. Choose Create workflow, then start from scratch or select a compatible template.
3. Choose the records and enrollment criteria. Specify the event or conditions that should start the workflow.
4. Set exit and repeat rules. Review unenrollment and re-enrollment before adding actions.
5. Add the actions. Configure the assignment, task, notification or property update required by your rule.
6. Review activation. Decide whether existing matching records should enter when you turn it on.

These steps follow HubSpot's workflow creation guide. Check that guide for current permissions and subscription requirements.

Verify access before specifying the build

• Hub and subscription: record the actual Hub and tier in your portal. The creation guide lists eligible Professional and Enterprise subscriptions; it does not promise every action on every plan.
• Permissions: confirm workflow Edit permission for the builder and Publish permission for whoever activates it.
• Actions: check that the selected object, property edits, task assignments and email actions are available and unlocked. Treat any missing access as a blocker until it is confirmed.

Access references checked October 12, 2026: the creation guide above and HubSpot's action-specific requirements.

Test the workflow before turning it on

Use HubSpot's enrollment test and record preview to check who qualifies and which route they take. A preview is not proof that every live action will succeed: HubSpot documents differences between testing and live execution.

• Normal case: a new eligible enquiry reaches the intended owner.
• Missing information: an enquiry without a territory reaches the fallback.
• Existing owner: the workflow preserves the current assignment.
• Repeat submission: the same person does not receive duplicate tasks or unwanted messages.
• Closed record: a disqualified or completed lead stays outside follow-up alerts.

Record the expected result for each case. After activation, inspect the first real enrollments and action outcomes, assign someone to review exceptions, and revisit the rules when your process changes.

Where HubSpot automation workflows commonly go wrong

Three failure patterns show up constantly. First, repeat enrollment is enabled without checking whether a contact should still qualify. HubSpot normally enrolls records once; repeat entry depends on the configured re-enrollment rules or manual enrollment. Review those rules alongside exclusions and exit criteria. See HubSpot's re-enrollment documentation. Second, two workflows silently compete for the same contact, one sets a field the other one re-triggers on, and the portal loops or double-sends.

Third, and most common, a workflow gets built once and never revisited, so it's still running the same logic against a company that has since changed its lead sources, sales process, or ICP. None of these are HubSpot problems; they're maintenance problems that automation makes easy to ignore until they're expensive.

Debug the symptom before changing the rule

Start with one affected record and the relevant timestamp. Use the workflow's Enrollment history and Action logs to distinguish a record that never entered from an action that failed, was skipped or is still waiting.

Official references: enrollment troubleshooting, email and execution-window errors, and workflow timing settings. Duplicate tasks and conflicting writes are diagnostic possibilities to investigate, not proof of a HubSpot defect.

A HubSpot automation checklist before you build anything

Before building a new workflow, confirm four things: what specific manual step it replaces, what triggers it (and what should explicitly not re-trigger it), who gets notified if it fails silently, and when it gets reviewed next. That last one matters most. Automation spend is an ROI question, and a workflow with no review date is a workflow that will quietly drift out of date and keep running anyway.

Safe activation and changes to a running workflow

A change is ready when someone owns both the intended result and the exceptions. Use this checklist for a new build and for edits to an existing one.

1. Name an accountable owner. Put the actual person's name, purpose and next review date in the description. Use a consistent name such as Team | Object | Purpose | Version. A team label alone is not an exception owner.
2. Record the current behavior. Note the triggers, exclusions, repeat rules, action windows and connected assets. Use revision history to identify what changed, when and by whom.
3. Test a copy first. Clone the workflow, label the copy TEST and keep it off until its triggers and recipients are isolated. Use controlled records and internal recipients; check every branch and abnormal case before release.
4. Account for records already enrolled. Inspect their current paths, delays and scheduled actions. Write down which should finish, be unenrolled or receive a targeted repair. Avoid moving the same population into a replacement while the original can still perform the same work.
5. Choose the activation population. For a new workflow or replacement, decide explicitly whether existing matches enter. Review their previous tasks and messages before allowing a backlog to run.
6. Plan interruption and recovery. Turning a workflow off stops new enrollment, but does not freeze existing records at their current step. Delays and branches can continue, other actions can be skipped, and turning it back on does not replay skipped actions. Review HubSpot's off-state behavior before using the toggle during maintenance. Inspect each affected record before any manual rerun.
7. Verify the first live outcomes. The owner checks action logs, resulting records and exceptions after activation, then records the next review date. If the behavior is wrong, stop further affected work and reconcile completed actions before trying again.

A short workflow outcome-review template

For each review period, record the workflow name/version, named owner, date range and next review date. Keep these measures separate:

• Enrollment: unique records entered, plus repeat enrollments counted separately.
• Execution: assignments, tasks or messages actually completed, checked against action logs and the resulting records.
• Exceptions: suppressed records, failed or skipped actions, missing owners and duplicates, each with a responsible person and next action.
• Business outcome: for routing, time from the enquiry to the first recorded human response. Report bookings, attended meetings and qualified opportunities separately. A booked meeting proves neither attendance nor qualification; without evidence, leave that outcome unrecorded.

The review should produce a decision: keep the rule, repair a specific exception or change the process with an owner and date. More enrollments alone do not establish that the workflow improved the handoff.

FAQ

Read next