HubSpot workflows for sales teams: five to build, and what to leave alone

Which HubSpot workflows a sales team needs

Automate the steps that get forgotten in a busy week, and leave the selling to people. These five jobs cover most of what a B2B sales team needs. Each one is built below with its trigger, branches and actions.

Before you build a workflow, check two things. Does HubSpot already do the job, such as setting the close date when a deal is won? Then build nothing. Is the job one action on a stage change? Then a pipeline automation is enough.

When a HubSpot pipeline automation is enough

A pipeline automation runs one or more actions when a deal enters a stage: create a task, send an internal email, or edit a record. You set it up in the pipeline settings, it works from Sales Hub Starter, and it doesn’t count towards your workflow limit. For a task after a stage change, the pipeline automation is the better tool.

1. Step 01

   Open the pipeline’s automations

   Go to Settings > Data Management > Objects > Deals, tab Pipelines, choose the pipeline and open Automate. Each stage has its own column.
2. Step 02

   Add the task to the stage

   Under “Create workflows from scratch”, click Create workflow under the stage, choose Create task and set the title, the due date and the owner. In our example a deal that reaches Presentation scheduled gives the deal owner a task for the next working day: send the summary and the next steps.

   

3. Step 03

   Keep the close date automation on

   In the same tab, under Templated automations, HubSpot sets the close date to today when a deal moves to a closed stage. Leave it on and don’t build a workflow for it. A second switch clears the close date when a deal is reopened.

   

Workflow 1: create a deal from a quote request form

When someone fills in your quote request form, the workflow creates a deal in the right stage, gives it to the contact’s owner and creates a call-back task. If the contact already has a deal, it creates no second deal and gives the owner a task to check the open one.

1. Step 01

   Trigger: the form, with re-enrollment on

   Create a contact-based workflow with the trigger “Form submission” and pick your form. Turn re-enrollment on, so a customer who asks for a second quote next year is enrolled again.
2. Step 02

   Wait five minutes

   Add a delay of five minutes. Other workflows, such as the owner workflow below, start on the same new contact at the same moment, and neither waits for the other. The delay lets the owner be set before the deal is created.
3. Step 03

   Branch: does the contact have a deal?

   Add a branch on “Number of Associated Deals is greater than 0”. Name the branches so anyone can read them: “Already has a deal” and “No deal yet”.

   

4. Step 04

   Create the deal

   In the “No deal yet” branch add Create record, type Deal. Assign it to the contact owner, name it “Quote request:” plus the company name, choose the pipeline and stage, and set a close date 30 days out, so it never lands at the end of the month by default. The new deal is linked to the contact and its company.

   

5. Step 05

   Create the call-back task

   After the deal, add Create task: “Call back about the quote request”, due the next working day, assigned to the contact owner, priority high. In the other branch, a task “check the open deal” goes to the same person.

Create deals at a real buying signal, such as a quote request or a qualified meeting, and never on every download. Deals created too early fill the pipeline with records nobody works. How to set up the stages themselves is in our guide to the deal pipeline.

Workflow 2: assign owners by account manager or round robin

A new contact from a customer should go to the person who looks after that customer. A new contact from a new company should go to the next salesperson in turn. One workflow does both.

1. Step 01

   Trigger: contact owner is unknown

   Create a contact-based workflow with the filter “Contact owner is unknown”. The filter catches contacts from forms, imports and integrations alike, and never touches contacts someone already owns.
2. Step 02

   Wait five minutes

   HubSpot links a new contact to its company from the email domain. The delay gives that link time, so the branch can see the company.
3. Step 03

   Branch on the company, not the contact

   Add a branch “Existing customer”: the contact is associated with a company whose lifecycle stage is Customer. Everything else goes to “New customer”.

   

4. Step 04

   Existing customer: copy the company owner

   Add Edit record and set Contact owner to the company owner. The account manager now owns the new contact too.
5. Step 05

   New customer: rotate within the team

   Add Rotate record to owner and pick the sales team. HubSpot shares the contacts evenly among the team’s main members with a paid Sales or Service seat. Leave “Overwrite if contact has an existing owner” off.

   

   

Round robin in HubSpot is even, not smart: the rotation doesn’t know who is on holiday, who already spoke to the company, or who closes which kind of deal. If territories, languages or products decide who gets a lead, add branches for them before the rotation, and keep the rotation for what is left. Which stage counts as a customer is explained in lifecycle stages, lead status and deal stages.

Workflow 3: catch deals whose close date has passed

An open deal with a close date in the past is either late or lost, and either way the forecast is wrong. HubSpot sets the close date when a deal is closed, but HubSpot doesn’t warn about open deals that overrun. The workflow below does.

1. Step 01

   Trigger: open stage and close date before today

   Create a deal-based workflow with two filters: the deal stage is one of the open stages of the pipeline, and the close date is before today. Turn re-enrollment on, so a deal is caught again if the new date passes too.

   

2. Step 02

   Task for the deal owner

   Add Create task: “Close date has passed: set a new date or close the deal”, assigned to the deal owner, due within a few working days. The owner either moves the date with a reason or closes the deal as lost.

Don’t let the workflow change the close date itself. A date the workflow pushes back every month makes the forecast look healthy while nothing moves. The deal owner decides.

Workflow 4: get alerted when a deal stalls

A stalled deal is one where nothing has happened for longer than your sales cycle allows. The workflow reminds the owner first and tells the sales lead only if nothing changes.

1. Step 01

   Trigger: no activity for 14 days

   Create a deal-based workflow: the deal is in an open stage and “Last activity date” is more than 14 days ago. Pick the number from your own sales cycle; for long project sales 21 or 30 days fit better. Turn re-enrollment on.

   

2. Step 02

   Task for the owner

   Add a task: “No activity for 14 days: plan the next step or close the deal”, assigned to the deal owner, high priority, due the next working day.
3. Step 03

   Wait a week, then check again

   Add a delay of seven days and a branch: is the last activity date now more than 21 days ago? If so, send an internal email to the sales lead with the deal name, so it comes up in the next pipeline review. If the owner logged something, the workflow ends.

   

Don’t close stalled deals as lost automatically. A rep may be waiting for a budget decision without logging it, and a deal closed by a workflow hides that conversation from the report on lost reasons.

What not to automate with HubSpot workflows

How HubSpot workflows conflict, and what stops it

A workflow can look right on its own and still break the system. These are the problems we see most often in portals with more than a few dozen workflows, and what stops each one.

When something did go wrong, open View > Revision history in the workflow. The revision history lists every change with date and user, and you can revert to an earlier version. Reverting doesn't change any records. On Enterprise, a Super Admin can restore the property values one workflow changed in the last 14 days, from the workflow's Enrollment history. Changes made by custom code actions aren't restored. Older changes, and every change on Professional, you fix with a list and a bulk edit. Imports and integrations that trigger workflows often create duplicates too; the fixes are in duplicates in HubSpot.

Keep workflows findable: names, folders, owners

After two years, a portal often has a hundred workflows and nobody knows which ones still matter. Four habits prevent that, and none of them costs more than a minute per workflow. For a portal that already has the problem, start with the workflow part of our portal audit checklist.

1. Step 01

   A name that says team, object and job

   Use one pattern for every workflow: team · object · what it does, such as “Sales · Deal · Stalled deal alert”. The object tells you where it enrolls, the job tells you what it changes.
2. Step 02

   A description with trigger and effect

   Write in one or two sentences what starts the workflow, what it changes and who to ask before editing it. HubSpot writes a description with AI if you leave it empty; replace it with your own.
3. Step 03

   A folder per team

   Under Automation > Workflows, tab Folders, create one folder per team and move the workflows in. Filters by object type, creator and action type find the rest.

   

4. Step 04

   A review every quarter

   Check the tabs Needs review (workflows with errors in the last seven days) and Unused (off, or no actions in 90 days). Delete what nobody needs; deleted workflows can be restored for 90 days.

Give the right to edit and publish workflows to the few people who own sales operations. Everyone else suggests changes to them.

Which HubSpot edition you need for sales workflows

In July 2026 HubSpot added a second workflow builder in Agent Hub, still a public beta in October 2026. Converting a workflow there can’t be undone and starts its version history again. For sales workflows like the ones above, the classic workflows tool is all you need.

What’s different in Germany, Austria and Switzerland

• Time zone and working hours. Set the account time zone first; without one, workflow timing falls back to US Eastern time. Then let workflows run actions on working days and hours only, so no task lands at 3 a.m.
• Public holidays. Holidays differ by country and by German state or Swiss canton. Add them as pause dates in the workflow settings, set to repeat each year.
• Works councils. Alerts that report a rep’s inactivity to the manager can count as a system that monitors performance. In Germany (§ 87 BetrVG) and Austria (§ 96 ArbVG) the works council has a say in such systems. Talk to the works council before you turn on the stalled deal alert.
• One language for names. Teams that work in German and English should agree on one language for workflow, property and folder names. Mixed names make a workflow list unreadable within a year.

How we set up sales automation

In most portals we look at, the problem isn’t a missing workflow. It’s twenty old ones that nobody dares to switch off. So we start with what exists.

1. Step 01

   Audit

   We list every workflow and pipeline automation, what triggers it and which properties it writes. You see which ones conflict, which do nothing and which nobody owns.
2. Step 02

   Plan

   Together with sales we decide which jobs to automate, which to leave to people, and who owns which property. You get a plan with an order and a fixed price.
3. Step 03

   Build and test

   We build each workflow with a clear name and description, test it on sample records and switch it on during working hours, with the old one off.
4. Step 04

   Hand over

   Your team gets the folder structure, the naming pattern and a short routine for the quarterly review, so the portal stays readable after we leave.

Frequently asked questions