HubSpot automation: 10 workflows that turn your CRM into a revenue machine

Why Most HubSpot Users Are Leaving Revenue on the Table

HubSpot is one of the most powerful CRM platforms available to growing businesses. It also happens to be one of the most underutilised. In our experience auditing automation stacks across dozens of client HubSpot portals, the average business uses somewhere between 15 and 25 percent of the automation capabilities included in their subscription tier. The remaining 75-85 percent sits dormant while teams manually do work the platform was designed to do for them.

The gap is not ignorance of the platform's existence it is a gap between knowing that HubSpot has workflows and knowing which workflows to build, in what order, with what logic. This guide closes that gap. The 10 workflows below are the ones that consistently generate the highest revenue impact and time savings across our client base. Each workflow includes the trigger, the logic, the specific HubSpot configuration, and where native HubSpot hits its limits how to extend it with n8n or Make via the HubSpot API.

Understanding HubSpot Native Automation vs External Tools

HubSpot's native workflow builder is capable of a wide range of automation without any external tools. It handles contact and deal property updates, email enrolment, task creation, notifications, internal emails, form and meeting-based triggers, deal stage transitions, and sequence enrolment. For the majority of businesses, native HubSpot workflows handle 70-80% of what they need.

The gaps where native HubSpot falls short, and where connecting n8n via the HubSpot API adds significant capability, are:

• Complex data transformations: HubSpot workflows cannot run custom JavaScript logic or complex calculations on contact properties. n8n can.
• Cross-system triggers: if you want a HubSpot workflow to fire based on an event in Stripe, Xero, or a custom database, native HubSpot cannot listen to those events. n8n can.
• Bulk data processing: HubSpot workflows are event-driven. Scheduled batch operations (re-scoring all contacts weekly, generating a weekly report) are better handled externally.
• Custom API integrations: connecting HubSpot to tools without native HubSpot integrations requires an external automation layer.

The rule of thumb: use native HubSpot workflows for CRM-centric automation where the trigger and all required data live within HubSpot. Use n8n + HubSpot API for workflows that cross system boundaries or require logic HubSpot cannot execute natively.

Workflow 1 AI-Powered Lead Scoring

Lead scoring is the practice of assigning a numerical score to each contact based on their profile and behaviour, so that sales can prioritise outreach to the highest-quality leads first. HubSpot supports native lead scoring through its Predictive Lead Scoring feature (Enterprise tier) or manually defined scoring rules (any tier).

Native HubSpot Lead Scoring Setup

In HubSpot, navigate to Contacts > Lead Scoring. Define positive and negative scoring criteria across two dimensions. Demographic fit criteria: job title matching target persona (+15 points), company size in your target range (+10 points), industry matching your ICP (+10 points), company revenue in target range (+8 points). Behavioural engagement criteria: pricing page visit (+20 points), demo request form submission (+40 points), email opened in last 7 days (+5 points), downloaded a case study (+10 points), visited blog more than three times in 30 days (+5 points). Negative scoring criteria: unsubscribed from all emails (-20 points), job title matching student or intern (-15 points), free email domain (Gmail, Yahoo) for B2B targets (-10 points).

Create a contact property called Lead Score Tier (High/Medium/Low) and a HubSpot workflow that sets this tier based on the numerical score: above 60 equals High, 30-60 equals Medium, below 30 equals Low.

Extending Lead Scoring with n8n and Claude

For a more sophisticated scoring layer, use n8n to pass each new contact's LinkedIn URL and company website to a Claude AI node for intent signal analysis. Claude reads the LinkedIn bio, recent posts, and company website to identify buying signals (recent funding, headcount growth, job postings for roles that indicate they need your product) and returns a supplementary intent score. This intent score is written back to a custom HubSpot contact property via the HubSpot API and incorporated into the overall lead score calculation.

This hybrid approach HubSpot for structured demographic and behavioural scoring, n8n and Claude for unstructured signal analysis consistently produces a more accurate score distribution than either approach alone.

Workflow 2 Sequence Enrolment Based on Lead Score and Stage

This workflow automatically enrols contacts into the appropriate HubSpot Sequence based on their Lead Score Tier and current lifecycle stage. It removes the manual step of a salesperson deciding which sequence to assign each lead.

Trigger and Logic

Trigger: contact property Lead Score Tier is updated to High or Medium.

Logic: if Lead Score Tier equals High AND Lifecycle Stage equals Lead, enrol in the High-Intent Demo Sequence (a 5-touch sequence focused on booking a demo within 7 days). If Lead Score Tier equals Medium AND Lifecycle Stage equals Lead, enrol in the Medium-Intent Nurture Sequence (a 10-touch sequence over 21 days focused on education before a demo ask). If Lead Score Tier equals High AND Lifecycle Stage equals Marketing Qualified Lead, enrol in the Sales Fast-Track Sequence (a 3-touch sequence focused on a same-week call booking).

Add a delay gate between sequence enrolments: do not enrol a contact in a new sequence if they were enroled in any sequence within the last 14 days. This prevents sequence overlap that creates confusing recipient experiences.

Sequence Content Framework

High-Intent Demo Sequence (5 touches over 7 days): email 1 (day 0) personalised intro referencing the specific page they visited or content they downloaded. Email 2 (day 2) relevant case study for their industry. Email 3 (day 3) a specific question about their current situation designed to elicit a reply. LinkedIn connection request (day 4). Email 4 (day 6) direct demo booking link with a specific time slot suggestion. Each email should be under 150 words and written in plain text format rather than HTML template design.

Workflow 3 Deal Rotation and Assignment by Territory

Manual deal assignment is one of the most consistently broken processes in growing sales teams. Deals sit unassigned for hours. Territories are not respected. Senior reps cherry-pick high-value deals. This workflow automates deal assignment the moment a deal is created, based on rules that are transparently defined and consistently enforced.

HubSpot Deal Rotation Setup

Create a HubSpot workflow triggered by deal creation. Use HubSpot's native round-robin assignment feature to assign to the appropriate team queue first, then apply territory rules via branch logic. Branch on the Deal > Associated Company > Country/Region property: if United Kingdom, assign to the UK Sales queue. If DACH region, assign to the DACH queue. If no region is detected (common for inbound leads with incomplete company data), assign to the next rep in the inbound round-robin rotation.

After assignment, create a task for the assigned rep with a due date of same day if the deal was created before 3pm, or next business morning if created after 3pm. Set the task priority to High. Send an internal email to the rep and a Slack notification via HubSpot's Slack integration.

Extending with n8n for Complex Territory Logic

If your territory rules are too complex for HubSpot's native branch logic (for example, splitting territories by postcode prefix, account revenue tier, and product line simultaneously), build the assignment logic in n8n. Use a HubSpot webhook trigger on deal.creation, pass the deal and company data to n8n, run the territory assignment logic in a JavaScript code node, and write the assigned owner back to HubSpot via the Owners API.

Workflow 4 Automated Task Creation by Deal Stage

Every deal stage transition should trigger a defined set of tasks for the assigned rep. This workflow eliminates the need for reps to remember what to do next and ensures process consistency across the entire team.

Task Creation Logic

Trigger: deal stage is updated.

When deal moves to Demo Scheduled: create task for rep "Send pre-demo research brief to prospect" (due date: 24 hours before meeting). Create task "Send demo confirmation and agenda email" (due same day as stage change). Create task "Prepare personalised demo environment with prospect's company name and sample data" (due 4 hours before meeting).

When deal moves to Proposal Sent: create task "Follow up on proposal status" (due date: 3 days after stage change). Create task "Send relevant case study matching prospect's industry" (due same day). Create task "Set 7-day deal activity alert" (due 7 days after stage change).

When deal moves to Negotiating: create task "Review deal discount approval against pricing guidelines" (due same day). Create task "Schedule executive sponsor call if deal value above £10,000" (due 2 days). Create task "Prepare contract draft and send for legal review" (due same day).

This task cascade ensures every rep follows the same process at every stage without needing to remember it.

Workflow 5 Automated Contract Sending via PandaDoc

This workflow fires when a deal reaches Verbal Agreement stage and automatically generates and sends a contract from the correct template, pre-filled with the deal data stored in HubSpot.

Architecture

HubSpot native workflows cannot send PandaDoc contracts directly, but n8n handles this elegantly. Create a HubSpot workflow triggered by deal stage change to Verbal Agreement. Add an action that sends a webhook to an n8n workflow endpoint. The n8n workflow receives the deal ID, queries the HubSpot Deals API for full deal properties (value, term length, product selection, associated contact and company), maps those properties to the appropriate PandaDoc template fields using a template ID lookup table, calls the PandaDoc API to create and send the document, and writes the PandaDoc document ID back to a custom HubSpot deal property for tracking.

When the contract is signed, PandaDoc fires a webhook to a second n8n workflow that updates the HubSpot deal stage to Contract Signed and creates an onboarding task for the customer success team.

The time from verbal agreement to contract in the prospect's inbox drops from the typical 2-4 hours (manual process) to under 3 minutes.

Workflow 6 Renewal Alert and Re-engagement Sequence

For businesses with recurring contracts or subscriptions, the renewal workflow is one of the highest-revenue automations available. A missed renewal conversation is a missed retention opportunity. This workflow ensures no renewal is ever approached without a structured engagement sequence.

Setup

Store the contract renewal date as a custom contact or deal property (Renewal Date). Create a HubSpot workflow with a date-based trigger: enrol contact when Renewal Date equals 90 days from now.

90 days before renewal: send an internal notification to the account owner "Renewal due in 90 days for [Contact Name] £[Contract Value]. Start renewal conversation." Create a task to schedule a Quarterly Business Review.

60 days before renewal: enrol contact in a Renewal Nurture sequence an external-facing email sequence that shares recent product updates, new case studies, and an invitation to a renewal review call.

30 days before renewal: if the deal stage has not moved to Renewal In Progress, send an alert to the sales manager. Create a high-priority task for the account owner and send an SMS (via n8n + Twilio) if the contract value exceeds £5,000.

14 days before renewal: if no renewal deal is created in HubSpot, escalate to the Head of Sales with an automated email summary of the account status.

Workflow 7 NPS Survey Trigger and Response Routing

NPS (Net Promoter Score) surveys are most effective when triggered at the right moment in the customer journey rather than batch-sent to all customers simultaneously. This workflow triggers NPS surveys at the optimal moment and routes responses to the right team action.

Trigger Logic

Trigger NPS surveys at three points in the customer lifecycle: at 30 days post-onboarding (first impressions), at 90 days post-onboarding (after first full delivery cycle), and annually on the contract anniversary date.

Use HubSpot workflows to enrol contacts at each of these milestones and send the survey via your NPS platform (Delighted, SurveyMonkey, or Typeform). Store the NPS score and verbatim feedback as custom HubSpot contact properties when the survey is completed (via n8n webhook receiving the survey platform's completion event).

Response Routing

When NPS score is received: if score is 0-6 (Detractor), create an immediate high-priority task for the account manager "Detractor NPS response call within 24 hours." Send internal Slack alert to customer success channel. Enrol contact in a Detractor Recovery sequence a personal outreach from a senior team member offering to discuss their feedback.

If score is 7-8 (Passive), create a task to send a personalised follow-up email acknowledging the feedback and sharing recent improvements. Do not immediately ask for a referral.

If score is 9-10 (Promoter), enrol in a Promoter Referral sequence a personalised thank you email that invites them to refer a colleague or leave a review on G2, Capterra, or Google Business Profile.

Workflow 8 Customer Health Scoring

Customer health scoring goes beyond lead scoring to measure the ongoing engagement and satisfaction of existing customers predicting which accounts are at risk of churning before they give explicit churn signals.

Health Score Components

Product usage signals (if your product provides usage data via API): login frequency, feature adoption depth, number of active users versus licences purchased, and trend direction (increasing, stable, or declining usage). Engagement signals available in HubSpot: email open rate trend over last 60 days, response rate to account manager outreach, NPS score trend, and support ticket volume. Relationship signals: time since last QBR, time since last proactive contact from account manager, number of stakeholders in HubSpot contact list for the account.

Implementation

Because HubSpot cannot natively calculate complex composite scores from external data sources, build the health score calculation in n8n. A weekly scheduled n8n workflow queries HubSpot for all customer contacts and associated company data, queries your product usage API for engagement metrics, calculates a composite health score per account (weighted average of the above components), and writes the score back to a custom HubSpot company property (Customer Health Score) and a directional property (Health Trend: Improving / Stable / Declining).

A HubSpot workflow triggered by Customer Health Score falling below 60, or Health Trend changing to Declining, creates an immediate task for the account manager and sends an alert to the CS team Slack channel.

Workflow 9 Churn Prediction and Early Intervention

Churn prediction takes health scoring one step further: rather than measuring current health, it models the probability of churn within the next 90 days based on historical patterns in churned accounts.

Churn Prediction with Claude AI

Build a monthly n8n workflow that queries HubSpot for all customer accounts with their health score history, support ticket history, contract terms, and engagement data. Pass each account's data to Claude with a prompt that includes: a description of the patterns observed in accounts that churned in the previous 12 months, and a request to assess the current account's similarity to those patterns and output a churn risk score from 0 to 100 with a brief rationale.

Write the churn risk score and rationale back to HubSpot as custom properties. Create a HubSpot workflow triggered by Churn Risk Score exceeding 70 that: assigns a high-priority Intervention task to the account manager and their manager, enrols the contact in a personalised re-engagement sequence, and creates a deal in a special Renewal Risk pipeline for executive visibility.

The Claude-generated rationale stored in HubSpot gives account managers specific context for their intervention call rather than just a number.

Workflow 10 Upsell Trigger Based on Usage and Engagement Signals

The most overlooked revenue opportunity in most CRMs is expansion revenue from existing customers. This workflow identifies the right moment to introduce an upsell conversation based on product usage signals and engagement patterns that correlate with readiness to expand.

Upsell Signal Detection

Define the signals that historically precede successful upsells in your business. Common signals include: approaching the limit of their current plan tier (usage at 80%+ of plan limit), adding multiple new users in a short period (indicating team growth), accessing a premium feature in trial mode more than 5 times, and NPS score of 9 or 10 combined with high recent engagement.

A weekly n8n workflow checks each customer account against these criteria. When two or more criteria are met simultaneously, the workflow creates a custom HubSpot deal in an Upsell pipeline with the account name, current contract value, and suggested upsell tier populated automatically. It creates a task for the account manager with the specific signals that triggered the flag, and sends a Slack notification with the context.

The account manager receives the Upsell opportunity with full context not just a flag, but the reason the signal fired which makes the outreach conversation natural and well-timed rather than random.

When Native HubSpot Is Enough

Native HubSpot automation handles these scenarios well without external tools: lifecycle stage management, sequence enrolment on form submissions or meeting bookings, email send actions based on contact property changes, deal task creation on stage transitions, internal notifications and reminders, and basic lead rotation within a defined team.

Move to n8n + HubSpot API when you need: cross-system triggers (payment events, usage data, support ticket signals), AI-powered enrichment or scoring, complex calculation logic, scheduled batch operations on all contacts or deals, or integration with tools that do not have a native HubSpot connector.

HubSpot API + n8n: The Technical Setup

To connect n8n to HubSpot, create a Private App in HubSpot Settings > Integrations > Private Apps. Grant the required scopes for the operations you need: crm.objects.contacts.read and crm.objects.contacts.write for contact operations, crm.objects.deals.read and crm.objects.deals.write for deal operations, and sales-email-read for sequence data. Copy the Private App access token and add it to n8n as a Header Auth credential.

For incoming webhooks from HubSpot (receiving deal stage changes or contact property updates in n8n), create a HubSpot workflow that uses the Webhook action type, pointing to your n8n webhook URL with a custom payload containing the object ID and event type. n8n receives this payload and uses the object ID to query the full object data via the HubSpot API before processing.

For further integration patterns and workflow architecture, our CRM automation complete guide covers the full self-running sales pipeline architecture that these HubSpot workflows form the foundation of.

Measuring Automation Impact in HubSpot

Every automation should have a defined success metric measured before and after deployment. For the 10 workflows above, the primary metrics are:

Workflow 1 and 2 (Lead Scoring and Sequence Enrolment): contact-to-MQL conversion rate, time from lead creation to first rep outreach, and sequence reply rate by tier.

Workflow 3 (Deal Rotation): time from deal creation to first rep activity, percentage of deals uncontacted after 4 hours (should trend to zero).

Workflow 4 (Task Creation): task completion rate by stage (are reps completing the auto-created tasks), and deal stage progression velocity.

Workflow 5 (Contract Sending): time from verbal agreement to contract sent, contract open rate, time from contract sent to signature.

Workflow 6 (Renewal): renewal conversion rate, average days between first renewal outreach and renewal signature, percentage of renewals where renewal sequence was completed.

Workflow 7 (NPS): NPS response rate, Detractor outreach completion rate within 24 hours, Promoter referral conversion rate.

Workflows 8 and 9 (Health and Churn): churn rate of accounts flagged as at-risk versus not flagged, account manager task completion rate for intervention tasks.

Workflow 10 (Upsell): upsell pipeline deal creation rate, upsell conversion rate, expansion MRR as a percentage of total MRR.

HubSpot's native reporting can measure most of these metrics with deal and contact reports. For the cross-system metrics (health score trends, churn prediction accuracy), build a supplementary dashboard in Google Looker Studio connected to HubSpot and your product usage data source.

The gap between a CRM that your sales team ignores and one that actively drives revenue is not a gap in tools it is a gap in automation. Every manual step between a signal (a lead scores highly, a contract expires, an NPS response arrives) and a response (an email, a task, a Slack alert) is a gap where deals slow down, churn accelerates, or revenue escapes. Automate the gap.