20 HubSpot Workflow Examples That Save Hours Every Week

Workflows Are Where HubSpot Pays for Itself

HubSpot workflows automate repetitive tasks that humans currently do manually: assigning leads, sending follow-ups, updating records, creating tasks, and routing tickets. Each workflow that replaces a manual process saves time every day – and the savings compound across your entire team. These 20 workflow examples are the highest-impact automations that most B2B companies should implement.

Marketing Workflows (1-7)

Sales Workflows (8-14)

Service Workflows (15-20)

15. Ticket routing: Auto-assign tickets by category to the right team. 16. SLA tracking: Alert if ticket not responded to within SLA window. 17. CSAT survey: Send satisfaction survey after ticket close. 18. Escalation: Auto-escalate tickets open more than 48 hours. 19. Knowledge base suggestion: Auto-reply with relevant KB articles for common issues. 20. Renewal reminder: 90-day advance notification for contract renewals.

Conclusion

Start with the 5 workflows that address your biggest time wasters. For most companies, these are: lead assignment (#8), MQL notification (#3), deal stage tasks (#10), stale deal alerts (#11), and closed-won onboarding (#12). Each workflow saves 2-5 hours per week. Five workflows can save 10-25 hours weekly across your team – that is the ROI of automation.

Need workflow automation? Talk to Widelly about building HubSpot workflows that automate your highest-impact processes.

20 HubSpot Workflow Examples That Save Hours Every Week

Workflow 1 – New lead assignment: when a new contact is created with a lead source of “website form,” assign to the next rep in rotation and create a follow-up task due within 4 hours. Workflow 2 – MQL notification: when a contact’s lead score reaches the MQL threshold, notify the assigned rep with a task and send an internal Slack message. Workflow 3 – Deal stage change notification: when a deal moves to “Proposal Submitted,” notify the sales manager with a summary of the deal. Workflow 4 – Closed won onboarding: when a deal closes, create a Service Hub onboarding ticket and send the customer a welcome email. Workflow 5 – Meeting no-show follow-up: when a meeting is created but no “Call Outcome = Connected” activity is logged within 30 minutes of the scheduled time, create a re-scheduling task. Workflow 6 – Proposal follow-up: when a deal enters “Proposal Submitted,” start a 3-step follow-up sequence if no reply is received. Workflow 7 – Data quality standardisation: daily workflow that formats all phone numbers to E.164 format and standardises company name capitalisation. Workflow 8 – Renewal deal creation: 90 days before a customer’s contract end date, create a renewal deal and assign to the account owner. Workflow 9 – NPS survey trigger: 90 days after a customer’s onboarding close date, send an NPS survey. Workflow 10 – Stale deal alert: when a deal has had no activity for 10 business days, create a task for the deal owner and notify the manager.

HubSpot Workflow Examples 11-20

• Workflow 11: when a contact visits the pricing page 3+ times, create a high-priority sales task.
• Workflow 12: when a deal is marked Closed Lost, require a loss reason selection before allowing the deal to close.
• Workflow 13: when a new contact is created without a company association, create a data quality task for the admin.
• Workflow 14: when a sequence reply is received, unenroll from the sequence and create a personal follow-up task.
• Workflow 15: when a support ticket reaches “Resolved,” send a satisfaction survey 24 hours later.
• Workflow 16: when a promoter NPS response is received (score 9-10), create a referral request task for the account manager.
• Workflow 17: when a new deal is created without a close date or deal value, send the rep a reminder to complete the required fields.
• Workflow 18: on a contact’s first visit to a blog post in a specific topic cluster, add them to the related lead nurture sequence.
• Workflow 19: when an integration sync error occurs, send an immediate alert email to the HubSpot admin.
• Workflow 20: monthly data enrichment workflow that triggers Breeze Intelligence enrichment on all contacts created in the past 30 days.

Frequently Asked Questions

Building a Workflow Library: HubSpot Best Practices for Teams

A workflow library is a curated collection of reusable workflow templates that the HubSpot admin team maintains and deploys as standard building blocks for common automation needs. Instead of each workflow being built from scratch, the library provides pre-tested, documented templates for: standard lead routing (assign to rep by territory, create task, start nurture sequence), deal stage notifications (internal Slack/email alert with deal context), data quality corrections (phone format, email validation, company association check), and customer lifecycle events (onboarding trigger, NPS survey, renewal pipeline creation). Benefits: new workflows are built faster using templates as a starting point, the team avoids repeating common configuration mistakes, and the library serves as living documentation of the automation patterns the portal relies on.

Advanced HubSpot Workflow Design: Branch Logic and Delay Patterns

Advanced workflow design uses branch logic and delays to create more sophisticated automation than simple trigger-action sequences. Delay + re-check pattern: instead of “if property equals X, do Y,” build “wait 1 day, then check if property still equals X, if yes do Y, if no exit.” This prevents erroneous automations from firing on transient data states. Branch logic for personalisation: “if company size is 200+, enrol in enterprise sequence; if company size is 50-199, enrol in mid-market sequence; otherwise enrol in SMB sequence.” Loop prevention: add a “workflow completion goal” property that is set to true when a workflow completes, and include this property as an exclusion criterion in the enrollment trigger to prevent re-enrolment. Timed branching: use delay-then-check branches to detect if a contact has replied to a sequence within 5 business days, and if not, create an escalation task for the account manager.

HubSpot Workflow Governance: Preventing the “Workflow Graveyard”

Every HubSpot portal that has been running for 12+ months accumulates what practitioners call a “workflow graveyard” – active workflows that are no longer serving their original purpose but have not been deactivated because no one is sure if something still depends on them. Common graveyards: post-campaign workflows from marketing campaigns that ended 12 months ago, which still enrol any contact who downloads an archived content asset. Onboarding workflows from a previous process that was redesigned 6 months ago but whose old version was never turned off. Lead scoring workflows that update a property that was replaced by a different scoring system. The consequence: contacts being enrolled in conflicting workflows, receiving emails from inactive campaigns, or having properties updated by multiple competing automation sequences. Prevention: when any workflow is created, document its business purpose, its planned duration, and its deactivation criteria. Review all active workflows quarterly with deactivation as a permitted outcome.

HubSpot Workflow Naming Convention That Prevents Confusion

• Format: [TEAM] – [PURPOSE] – [DATE CREATED] – [STATUS]
• Example: MKT – Lead Nurture SaaS Trial – 2025-09 – ACTIVE
• Example: SLS – Deal Stage Alert VP – 2024-11 – ACTIVE
• Example: OPS – Phone Standardisation – 2024-07 – ACTIVE
• Example: MKT – Q1 2025 Campaign Follow-up – 2025-03 – ARCHIVE (deactivated but kept for reference)
• This naming convention allows any admin to identify the team, purpose, age, and status of every workflow in 5 seconds without opening the workflow details.

HubSpot Workflow Audit: Finding Workflows That Are Hurting You

Not all active workflows help your business. The workflow audit identifies three categories of harmful automation. First, conflicting workflows: two workflows update the same property with different values when different triggers fire for the same contact – the outcome is unpredictable. Second, over-broad enrollment workflows: a workflow enrolled in 90% of all contacts is likely catching contacts it was not intended for – check whether trigger criteria are as specific as the business logic requires. Third, orphaned workflows: workflows whose trigger property is no longer being populated, meaning no contacts ever enroll, yet the workflow remains active and creates confusion for any admin trying to understand the portal’s configuration.