Response rate 9.2% — References to specific events are effectiveProblems that can be solved with automationis. If you design HubSpot's workflow correctly, you can create a system that continues to accurately perform repetitive tasks in sales operations without human judgment, from lead assignments, notifications when stages change, alerts for salted deals, and handoffs to CS. In this chapter, we will systematically explain the automation design of Sales Hub from the perspective of ``what to automate, when to automate, and how to automate it.''
HubSpot's workflow is "Trigger (when to fire) → Condition (to whom it applies) → Action (what to do)"It consists of three elements. By combining these three, you can automate almost any sales operation. It's important to understand this structure accurately before designing your workflow.
| element | role | Representative examples in Sales Hub |
|---|---|---|
| trigger | The “trigger” that starts a workflow. You can change properties, form submissions, page visits, dates, email activity, etc. | Opportunity stage changed to "Consideration" / Lead score exceeded 60 / Quote sent |
| conditions | After the trigger fires, the filter "narrow down further". You can add "if..." branching logic. | Only when the amount is 1 million yen or more / When the person in charge is a member of a specific team / When the industry is SaaS |
| action | Process to be executed when the condition is met. Property updates, task creation, email sending, notifications, Slack sending, sequence enrollment, etc. | Create task for assignee / Notify Slack channel / Update lifecycle stage / Stop sequence |
1:1 Sales Email Trigger (Private Beta, January 2026) and Buyer Intent Signal Trigger (Dec 2025) are the latest additions. especially 1:1 Email triggers will greatly change the concept of sales automationIt has the potential to become a standard component of Sales Hub automation designs once it's generally available. At the moment (March 2026) it is only available to Beta participants.
When an inbound lead comes in, you lose both speed and fairness if you manually decide who to give it to.Lead Rotationis a feature that automatically assigns new leads to sales representatives according to defined rules. In HubSpot, it can be used as a workflow action "Automatically assign leads" in Professional and above.
| Lead attributes | Assigned to | Workflow condition settings |
|---|---|---|
| Number of employees: 500 or more | Enterprise team (round robin) | Number of Employees ≧ 500 → Enterprise team round robin |
| Number of employees: 50-499 | SMB team (round robin) | Number of Employees between 50 and 499 → Round Robin for SMB Teams |
| Referral leads from existing customers | Priority assignment to CS/Sales in charge of existing customers | Original Source = Referral and Referrer Company known → Assign directly to the person in charge of the referring customer |
| Industries outside of ICP | Assign to SDR (Outreach Representative) and check pre-qualification | Industry is not in ICP list → Assigned to SDR team and transferred to AE after qualification confirmation |
| Assignment of person in charge is still incomplete after 24 hours | Escalation notification to manager | Contact Owner is unknown → Waiting for 24 hours → Slack notification to manager |
“How many hours should I make the first contact after the MQL joins?”Lead response time SLA can be automatically tracked and managed. If there is no contact after X hours of assignment, we will send a reminder to the person in charge, then escalate to the manager after X hours. In research100x more contact rate when first contacting a lead within 5 minutes compared to after 30 minutesThere is also data that suggests that. Automated SLA management is an automation with a very high return on investment.
One of the biggest factors putting pressure on the pipeline is "salted deals" - deals that have not moved for a long time and are almost forgotten by the people in charge. This is often overlooked in manual pipeline reviews, butSet up automatic detection and automatic alerts in workflowBy doing so, the system can actively "reveal" potential deals.
| stage | Alert firing days | Escalation days | Recommended remedial action |
|---|---|---|---|
| first contact | 7 days | 14th | Start follow-up sequence. prioritize calls |
| Issue identification | 10 days | Chapter 11: Breeze AI and Sales Hub — Revolutionize sales productivity with AI | Make a call to confirm the next action (proposal schedule) |
| Proposal/Demo | 10 days | Chapter 11: Breeze AI and Sales Hub — Revolutionize sales productivity with AI | Provision of additional materials / Approach email from a different angle / Confirmation with champion |
| comparative study | 14th | 21st | Set up a high-level call with the manager present. Re-presentation of ROI materials and examples |
| contract negotiation | 7 days | 14th | Direct contact to legal and purchasing departments. Use of deadline settings (end of year, etc.) |
Deals whose closing dates are left in the past will greatly distort the forecast.A workflow that runs every Monday with the condition that the closing date is before today and the opportunity is open.Let's set this up and automatically create a task that asks the person in charge to update the expected closing date or process lost orders. For many organizations, this alone can dramatically improve forecast accuracy.
We have organized the "required workflows" that are recommended for all organizations that have introduced Sales Hub into 10 recipes. Indicates each trigger, action, and recommended plan. I would like you to customize it to suit your organization's situation.
The more workflows you have, the more difficult they become to manage. ``I don't understand why this workflow is running,'' ``There are duplicate processes running,'' and ``I introduced a bug in production without testing.'' These are problems caused by poor naming conventions, testing habits, and document management.Establish a foundation for governance before the number of workflows increasesThis is the important work of RevOps.
| anti-pattern | Problem | correct design |
|---|---|---|
| Set to "Can re-enroll all contacts" | The same email is sent to the same person over and over again, or the same task is created twice | Enable re-enrollment only if intentional. Default is set to "Run only once" |
| Enabling production without testing | Risk of sending the wrong email to thousands of contacts at once | Be sure to try one test contact before applying the batch. Apply in stages for large scale cases |
| Workflow chain (spaghetti) | The output of workflow A triggers workflow B, which starts C, and so on, and the chain becomes complicated and becomes untraceable. | Prioritize designs that can be completed in one workflow. When chaining, be sure to document |
| Override properties unconditionally | "Overwrite Owner" action resets existing owner | Be sure to add the condition "Only if property is not set" |
| Set deleted user as approver/notifier | The person in charge who left the company keeps receiving notifications and tasks are left unattended. | Ensure workflow user settings are updated when an employee leaves the company. Incorporate into retirement checklist |
Before automating, organize in Japanese "what happens (trigger)," "for whom (condition)," and "what to do (action)" before implementing it in HubSpot. Automation without design creates spaghetti.
Design a set that automatically assigns personnel based on ICP attributes (scale, industry, source) and automatically tracks response time SLA after assignment. The speed of initial contact is directly linked to the conversion rate.
Alert for 14 days of stagnation, manager escalation for 21 days of stagnation, and automatic extraction on a weekly basis if scheduled closing date is exceeded. Instead of waiting for humans to "notice," the system should be designed to "reveal."
MQL assignments, initial business negotiation tasks, Closed Won processing, nurturing after loss, and 90-day-before-update alerts should be set as top priority. Intent signal triggers will be used as a new feature after December 2025.
Naming rules of "[Object] [Purpose] [Version]", testing required before production, quarterly inventory, and RevOps consolidation of change authority: By thoroughly following these four points, you can maintain the quality and manageability of your workflow.
Consciously eliminate the following five anti-patterns during design: ``Unlimited re-enrollment,'' ``Production application without testing,'' ``Workflow chaining,'' ``Unconditional overwriting of properties,'' and ``Leaving notification settings for retirees.''