HubSpot pipeline automation moves deals between stages, creates follow-up tasks, and fires internal alerts based on real deal activity. Instead of relying on reps to update stages manually, workflows handle the mechanics when defined conditions are met.
Each stage should reflect something the buyer did, not just something the rep needs to do. If a stage is called “Send proposal” rather than “Proposal sent”, it is a task, not a milestone. Rename before you automate.
In HubSpot, go to Automation > Workflows > Create workflow > Deal-based. Choose “Deal is active” as the trigger type, then set the enrollment condition: a property change, a meeting booked, or a form submitted by an associated contact.
Use the “Set property value” action, choose “Deal stage” from the property list, and select the destination stage. HubSpot moves the deal when the trigger fires.
After the stage move, add a task creation step for the owner, an internal email notification, or a delay followed by a re-engagement trigger if the deal stays in that stage without activity.
Use the “Test” function in the workflow editor. Pick a real or cloned deal and walk it through. Check the deal record to confirm the stage updated and the task appeared as expected.
What can HubSpot pipeline automation actually do?
The two most useful automations for most sales teams are stale deal alerts and automatic task creation. A stale deal alert fires when a deal has not moved in a set number of days, prompting the owner to act. Automatic task creation drops a follow-up call or email on the rep’s queue the moment a deal enters a new stage.
Beyond those two, teams use pipeline automation for deal routing (assigning deals to the right rep based on company size or industry), high-value deal notifications to sales managers, and sequence enrollment when a deal reaches a specific stage.
Which triggers work best for stage moves?
The most reliable triggers reflect genuine buying behaviour. A meeting booked via HubSpot Meetings is a clean signal that a prospect is engaged. A document opened via HubSpot Documents tells you a proposal is being reviewed. Both are trackable events that map naturally to a stage progression.
Avoid using “deal created” as your only trigger. It tells you a deal exists but says nothing about engagement. Build triggers around the actions your best deals have in common, then apply those as stage-move conditions.
How do I prevent automation from overriding a rep’s judgment?
Use if/then branches in the workflow. Before the stage move action, add a conditional check: if the deal has a specific tag, owner, or custom property value, skip the automated move and route it for manual review instead.
You can also use unenrollment triggers. Set a condition that removes a deal from the workflow the moment a rep manually moves it to a different stage. This ensures automation handles the routine while reps retain control over exceptions.
Can I automate across multiple pipelines?
Yes. Each deal-based workflow can filter by pipeline using an enrollment trigger condition. Build separate workflows for each pipeline, or use a single workflow with branching logic that routes deals differently based on which pipeline they belong to.
For teams that have separate pipelines for new business and renewals, this is the standard approach: one workflow per pipeline, each with its own set of stage-move triggers and notification rules.
How does pipeline automation connect to the broader workflow engine?
Pipeline automation runs on top of HubSpot’s standard workflow engine. Deal-based workflows give you the same branching logic and action library that contact workflows use. The difference is the object: deal properties instead of contact properties.
If you already use contact workflows for lead nurturing, the setup pattern is familiar. Build enrollment triggers and add actions in sequence. Test before activating. A basic stale deal alert takes under 15 minutes to configure once you know your pipeline stages.
What makes a pipeline ready for automation?
Automation works best when the underlying sales pipeline is clean and consistently used. If stages overlap or reps use them inconsistently, automated triggers fire at the wrong times. Before building automation, audit your stages: each should be clearly defined with a measurable entry condition. Agree on a win probability per stage before you build.
Teams that skip this step find that automation surfaces the inconsistency quickly. A stale deal alert firing on deals that were already manually moved is a signal that the pipeline structure needs attention first.
Frequently asked questions
Do I need Sales Hub Pro to use pipeline automation?
Basic deal-based workflows require Sales Hub Professional or above. Features such as sequence enrollment triggered from a workflow require Sales Hub Pro or Enterprise. Free and Starter plans support manual pipeline management only.
What happens if the trigger fires and the deal is already in the target stage?
HubSpot attempts to set the property, but the value does not change. Subsequent actions in the workflow still fire, so test carefully if your workflow does more than move the stage.
Can pipeline automation replace my sales process?
No. Automation handles the mechanical side: stage moves, task creation, follow-up alerts. Conversations and negotiation still require a person. The goal is to free reps from admin so they spend more time on the parts that require judgment.
How many deal-based workflows can I create?
HubSpot does not publish a hard limit, but very large workflow libraries can slow the admin interface. Start with the highest-impact automations and expand from there rather than building every possible rule at once.
An independent informational resource produced by a HubSpot Platinum Partner. HubSpot is a trademark of HubSpot, Inc.
Planning a HubSpot setup or integration in the region?
Contact us