10 HubSpot Workflow Automations That Every B2B Company Should Have
The 10 HubSpot workflows that consistently deliver the most value for B2B sales teams — with setup instructions and the logic behind each one.
HubSpot has one of the most powerful workflow automation engines of any CRM on the market. Most businesses use 10–20% of it. This guide covers the 10 workflows that we consistently build for B2B sales teams — ranked roughly by implementation priority and business impact.
All of these are achievable with HubSpot Professional or Enterprise plans. Workflows 7 and 10 require either HubSpot Operations Hub or an external automation tool like n8n connected via webhook.
Before building any workflow, get your contact and deal properties correctly structured. Workflows automating messy data produce messy outputs. Clean your CRM first.
New Lead Assignment & Notification
Trigger: Contact is created or converted from MQL to SQL
Logic: Route to the correct rep based on territory, company size, or source. Create a task with due date. Send Slack notification with lead summary to assigned rep.
Why it matters: Eliminates manual lead distribution and prevents leads from sitting in a queue unassigned.
Deal Rotting Alert
Trigger: Deal hasn't been updated in X days (define your rotting threshold per stage)
Logic: Set the deal as 'rotting' in HubSpot. Create a task for the deal owner. Send them a Slack notification with the deal name and days since last activity.
Why it matters: Stops deals from quietly dying in the pipeline. Most B2B sales teams lose deals not because they lose the deal — but because they stop following up.
Inbound Lead Acknowledgement
Trigger: Contact submits a website form
Logic: Send a personalised acknowledgement email within 60 seconds of form submission. Include expected response time and a link to book a call directly.
Why it matters: Speed-to-lead is one of the most impactful conversion factors. Automated acknowledgement + booking link converts high-intent leads at a significantly higher rate than waiting for a manual response.
Proposal Sent Follow-Up Sequence
Trigger: Deal stage moves to 'Proposal Sent'
Logic: Day 2: Follow-up email asking if they have questions. Day 5: Value-reinforcing email with a relevant case study. Day 9: Final follow-up with a deadline or next step prompt. If no response after Day 9, create a task for the rep to call.
Why it matters: Most proposals are forgotten without follow-up. Automated sequences ensure consistent follow-up without relying on rep discipline.
Closed-Won Handover Automation
Trigger: Deal stage moves to 'Closed Won'
Logic: Create a HubSpot ticket in the onboarding pipeline. Assign to the relevant CSM. Send welcome email to the client. Create a task for kickoff call scheduling. Notify the finance team for invoice creation.
Why it matters: The transition from sales to delivery is where new clients form their first impression of the company. Manual handover processes are inconsistent and slow.
Closed-Lost Re-Engagement
Trigger: Deal is marked Closed-Lost
Logic: Log the loss reason as a CRM property (make this required before the deal can be closed). After 90 days, enrol the contact in a re-engagement sequence — 3 emails referencing the original conversation and offering to reconnect.
Why it matters: Many lost deals are timing-related, not a permanent no. 90-day re-engagement often converts 5–15% of previously lost deals.
Contact Data Enrichment on Creation
Trigger: New contact is created in HubSpot
Logic: Via n8n or Zapier, call Clearbit or Clay to enrich the contact with company size, industry, LinkedIn URL, and tech stack. Write enrichment data back to custom HubSpot properties.
Why it matters: Salespeople shouldn't spend time researching contacts — that research should already be in the CRM by the time the lead is assigned.
Meeting Booked Notification & Preparation
Trigger: Calendly or Cal.com booking webhook fires
Logic: Update the HubSpot contact's lifecycle stage to 'SQL'. Create a deal if none exists. Send the meeting booker a preparation email with questions to answer before the call. Notify the assigned rep with the meeting details and a link to the CRM record.
Why it matters: Meetings booked via calendar tools often don't automatically create the right CRM records. This workflow ensures every booked meeting results in the correct pipeline activity.
Quote/Contract Expiry Alert
Trigger: Custom date property 'Quote Expiry Date' is X days away
Logic: 3 days before expiry: Notify the deal owner. 1 day before: Send an automated email to the prospect reminding them the quote expires tomorrow and offering to extend. Day of expiry: Create a task for the rep to follow up.
Why it matters: Proposals with deadlines convert at higher rates. But manual deadline management creates inconsistency. Automation ensures every expiry is followed up.
Weekly Pipeline Health Report
Trigger: Scheduled — every Monday at 8am
Logic: Via n8n or Operations Hub, pull open deals by stage, weighted pipeline value, deals at risk of rotting, and new deals added last week. Format as a Slack message and send to the sales manager channel.
Why it matters: Sales managers who see their pipeline weekly — not in a 30-minute review meeting, but as a quick Slack summary — catch problems faster and maintain pipeline hygiene more effectively.
Where to Start
If you're building from scratch, implement in this order: workflows 1 (lead assignment), 3 (acknowledgement), and 5 (closed-won handover) first. These three have the most immediate revenue impact and are the quickest to configure. Once those are running cleanly, add 2 (deal rotting), 4 (proposal follow-up), and 8 (meeting booked).
Workflows 7 and 10 require external tooling or Operations Hub — implement them in a second phase once the core sales workflows are stable.
Build workflows one at a time. Test each with real contacts before activating. A broken workflow that sends incorrect emails to prospects is worse than no automation.
The Compounding Effect
The real value of these workflows isn't any single automation — it's the system they form together. Leads are captured, acknowledged, assigned, enriched, followed up, and managed through to closed-won or closed-lost without manual intervention at each step. Sales managers have visibility without chasing updates. Deals don't slip through because someone forgot to follow up.
That's the difference between a CRM and a revenue system. These 10 workflows are where that shift begins.
Want to implement this for your business?
We engineer production AI automation systems. Book a discovery call.
Book a Call →