Automate deal stages

Your deal pipeline tells you where each deal sits. Deal stage automation tells HubSpot what to do when a deal moves. This is where your pipeline goes from a visual tracker to an active system that assigns tasks, notifies stakeholders, rotates ownership, and keeps deals moving without manual intervention.

HubSpot offers two levels of deal automation: embedded pipeline automation (quick mini-workflows you build right in the pipeline settings) and full workflows (more complex automations with multi-step logic). Most teams start with the embedded option because it's fast to set up and covers the most common use cases. Full workflows come in when you need conditional logic or cross-object actions.

Embedded pipeline automation

These are mini-workflows you configure directly in your pipeline settings. Go to Settings > Data Management > Objects > Deals > Pipelines tab, then click the "Automate" section.

Each deal stage gets its own automation trigger. When a deal enters that stage, the automation fires. You can add multiple actions per stage.

The most common embedded automations:

Rotate deal ownership. When a deal enters the first stage (e.g. "Appointment scheduled"), automatically assign it to a sales rep using round-robin rotation. Select the reps you want in the rotation, and HubSpot distributes new deals evenly.

Create tasks. When a deal moves to "Package selected", create a task for the deal owner to add line items. When it moves to "Contract sent", create a task to follow up in three days. This ensures every deal stage has a clear next action.

Send internal email notifications. When a deal hits "Closed won", send an email to the sales manager (or the whole team) with the deal name, amount, owner, and close date. Use personalisation tokens to pull the data automatically. This turns closed deals into instant celebrations and keeps leadership informed without them checking the pipeline manually.

How to build an embedded automation

In the Automate section of your pipeline settings, click the plus icon next to any deal stage. You'll see action categories:

CRM actions: Rotate record to owner, set a property value, create a task.

Communication actions: Send internal email notification, send in-app notification.

For each action, configure the details (who gets notified, what the task says, which reps are in the rotation) and save. The automation is live immediately.

Full workflows for complex automation

When you need logic that goes beyond "deal enters stage, do this", build a standalone workflow. Go to Automations > Workflows > "Create workflow" > Deal-based.

Common workflow-based deal automations:

Stale deal notification. Trigger: deal close date is in the past AND deal is not closed won or lost. Action: send an internal email to the deal owner saying "This deal's close date has passed. Update the close date or move it to closed lost." Add unenrollment criteria so deals already in closed won or closed lost don't trigger the workflow.

This is one of the most valuable automations you can build. Stale deals pollute your pipeline data, inflate your forecast, and hide the fact that a deal is dead. An automated reminder forces reps to either re-engage or close it out.

High-value deal alert. Trigger: deal amount is greater than a threshold (e.g. $5,000) AND deal is in your target pipeline. Action: send an in-app notification to sales leadership with the deal name, amount, and owner. This ensures leadership knows about big deals early enough to provide support.

Sales-to-services handoff. Trigger: deal stage is Closed won in your pipeline. Action: send an internal email to the services team with the deal details and customer information. This bridges the gap between closing a deal and onboarding the customer, so the customer doesn't sit in silence for a week after signing.

Closed-lost reason reminder. Trigger: deal stage is Closed lost AND closed-lost reason is unknown. Action: create a task for the deal owner to update the closed-lost reason. This catches deals that were moved to lost without the conditional property being filled in (which can happen with bulk updates or API changes).

Best practices for deal automation

Start with embedded automation. Cover the basics (task creation, notifications, owner rotation) before building complex workflows.

Name everything clearly. Every workflow, every task, every notification needs a name that tells you what it does without opening it. "Stale deal notification workflow" is clear. "Workflow 47" is not.

Test with yourself. Create a test deal and walk it through every pipeline stage. Verify that each automation fires correctly before your team relies on it.

Set unenrollment criteria. Every workflow should have exit conditions. For deal workflows, the most common unenrollment criteria are: deal is closed won or deal is closed lost.

Deal stage automation transforms your pipeline from passive tracking into active deal management. Start with embedded automations for task creation and notifications, then layer in workflows for stale deal reminders, high-value alerts, and handoff emails. Every automation you build is one less manual step your reps forget to do.