HubSpot Workflows: 9 Examples That Drive Revenue

HubSpot Workflows: 9 Examples That Drive Revenue

Most HubSpot portals use workflows for one or two things - usually a welcome email and a lead notification. The rest of the automation capability sits unused while the sales team manually assigns leads, marketing manually segments lists, and RevOps manually chases data quality issues that a workflow could fix in seconds. RevBlack builds workflow architecture for PE-backed B2B SaaS companies where automation is not a nice-to-have - it is the operational layer that makes the revenue engine run without constant human intervention. These nine examples cover the highest-impact uses of HubSpot Workflows, from sales automation to Salesforce integration to data hygiene.

What Are HubSpot Workflows?

HubSpot Workflows is an automation builder that enrolls contacts, companies, deals, leads, tickets, and custom objects in a series of automated actions - sending emails, updating property values, creating tasks, routing records, and triggering actions in connected tools.

Workflows live under the Automation tab in the HubSpot portal. They run on enrollment triggers - a form submission, a property change, a lifecycle stage transition, a score threshold, a date - and execute a defined sequence of actions against the enrolled record. They connect to Salesforce, Slack, Asana, Microsoft, and dozens of other tools via native integrations, turning HubSpot into the automation layer for the full GTM stack.

The workflows described in this guide use HubSpot Marketing Hub, Sales Hub, and Operations Hub depending on the use case. Hub tier requirements are noted for each example where relevant.

Why Do HubSpot Workflows Matter for Revenue Operations?

HubSpot Workflows are the operational infrastructure that converts manual RevOps work into systematic, repeatable processes.

Without automation, every handoff between marketing and sales is a manual task. Every lead assignment requires someone to decide. Every data quality issue requires someone to find and fix it. Every sequence enrollment requires a rep to remember. At small scale, these manual steps are manageable. As pipeline volume grows, they become the bottleneck - the reason leads sit without follow-up, data degrades faster than it gets cleaned, and the revenue engine produces inconsistent output regardless of how good the strategy is.

HubSpot Workflows eliminate these bottlenecks at the process level. The automation runs continuously in the background, handling the tasks that should not require human judgment - freeing RevOps to focus on the decisions that do.

Example 1: Automate Sequence Enrollment for Sales

Automated sequence enrollment ensures every new high-intent contact gets a personalized follow-up within minutes of taking a qualifying action - without a rep having to manually identify and enroll them.

Hub required: Sales Hub or Service Hub Enterprise.

How it works: Build an enrollment trigger that fires when a contact meets a defined combination of criteria - for example, visited the pricing page, has a lead score above 50, and has not yet booked a meeting. When all three conditions are true, the workflow automatically enrolls the contact in the appropriate outreach sequence based on their persona, industry, or lifecycle stage.

Set an unenrollment trigger for when the contact books a meeting or replies to a sequence email. This prevents the automation from continuing to send emails to contacts who have already converted - one of the most common sequence management failures RevBlack fixes in inherited HubSpot portals.

Why it matters for revenue: Speed-to-lead is one of the highest-leverage metrics in B2B sales. Manual sequence enrollment introduces delays between a contact's high-intent action and the first outreach. Automated enrollment eliminates that gap. For the full speed-to-lead architecture including routing and SLA enforcement, see RevBlack's speed-to-lead guide.

Example 2: Re-Engage Stalled or Cold Contacts

A re-engagement workflow recovers pipeline value from contacts who went cold - without requiring the sales team to manually identify and outreach to each one.

How it works: Build an enrollment trigger for contacts who meet a stall definition - for example, subscribed to marketing emails but have not opened any email in the last 60 days, have not visited the website in 90 days, and are currently in MQL or earlier lifecycle stage. Enroll those contacts in a re-engagement sequence: a first email acknowledging the silence and offering something genuinely useful, a second email five business days later with a relevant case study or resource, and a final email asking directly whether they want to stay on the list.

Set conditional branches based on engagement: contacts who open or click get re-enrolled in active nurture. Contacts who do not engage after all three emails get their lifecycle stage updated to reflect their inactive status and their marketing contact status set to non-marketing to stop accumulating against the contact tier count.

Why it matters for revenue: Stalled contacts represent paid acquisition cost that has not yet converted. A re-engagement workflow recovers a percentage of that investment automatically - without additional spend and without manual effort from the sales or marketing team.

Example 3: Create a Salesforce URL in HubSpot Contact Records

This workflow solves a specific problem that affects every team running HubSpot and Salesforce simultaneously: sales reps who work in Salesforce need a direct link to the Salesforce record from a HubSpot notification - but HubSpot's standard form notification emails only link to the HubSpot record.

How it works: Create a custom text property on the Contact object called "Salesforce URL." Build a workflow that triggers when a Salesforce Contact ID or Salesforce Lead ID is populated on a HubSpot contact record. Use a "Set property value" action to concatenate the Salesforce base URL with the Salesforce ID field to generate the full Salesforce record URL. Populate the Salesforce URL property with the result.

Once the property is populated, include it in HubSpot notification emails sent to sales reps. When a rep receives a lead notification, they click directly to the Salesforce record rather than opening HubSpot to find the contact.

Why it matters for revenue: Friction in the notification-to-action path slows response time. A rep who receives a notification and has to navigate to a second system to find the record is a rep who responds slower. For teams where sales works exclusively in Salesforce, this workflow removes the only reason they would need to open HubSpot to respond to a lead alert.

Example 4: Trigger Actions Based on Lead Score Thresholds

Lead score workflows automate the MQL handoff - converting a scoring threshold breach into an immediate, documented transfer of ownership from marketing to sales.

Hub required: Marketing Hub Professional or Enterprise for HubSpot Score property.

How it works: Build an enrollment trigger for contacts whose HubSpot Score exceeds the agreed MQL threshold - for example, 60 points. When the trigger fires, the workflow executes four actions in sequence: updates the contact's lifecycle stage to MQL, rotates the contact to the correct sales owner based on territory or round-robin rules, sends an internal notification to the assigned rep with the contact's key properties and recent activity, and creates a follow-up task in the rep's HubSpot task queue with a defined due date.

Add a conditional branch for contacts whose score drops back below the threshold without a rep activity logged - this catches leads that inflated their score through repeated low-value actions (for example, opening the same email multiple times) rather than genuine buying intent.

Why it matters for revenue: Manual MQL review processes introduce inconsistency and delay. A contact who hits the threshold at 4pm on a Friday may not get reviewed until Monday morning. Automated threshold-based routing eliminates the review queue entirely and ensures every MQL gets a rep notification within minutes of qualifying. For the full lead scoring architecture, see RevBlack's RevOps lead scoring playbook.

Example 5: Automate Lead Assignment

Automated lead assignment ensures every new lead reaches the right rep immediately - without a RevOps team member manually reviewing and assigning each record.

How it works: HubSpot supports two lead assignment models in Workflows.

Criteria-based assignment routes leads to a specific owner or team based on property values on the contact or company record - territory (state, country, region), company size tier, industry, or product interest. Build if/then branches for each routing rule and use the "Set property value" action to assign the contact owner field.

Round-robin assignment distributes leads evenly across a team or team subset regardless of lead attributes. Use the "Rotate record to owner" workflow action and select the team or user pool. HubSpot distributes each new enrollment to the next rep in the rotation.

Combine both models when needed: criteria-based routing for territory or segment rules, with round-robin as the fallback for leads that do not match any defined criteria.

Why it matters for revenue: Unassigned leads are invisible in rep-level reporting and do not receive automated follow-up. Every minute a lead sits unassigned is a minute a competitor with faster routing is gaining ground. For the full routing architecture including SLA enforcement and fallback logic, see RevBlack's automatic lead routing guide.

Example 6: Nurture Leads Through the Funnel

Lead nurture workflows move contacts from initial awareness to sales-ready status through a structured, automated email sequence - without requiring marketing to manually monitor and message each contact.

How it works: Build an enrollment trigger for contacts who take a qualifying top-of-funnel action - a content download, a webinar registration, a specific page visit - but have not yet reached MQL status. Design the nurture sequence in three phases:

Awareness (Email 1, Day 0): Deliver the asset or confirmation they signed up for. Include one additional resource relevant to the topic they engaged with. No CTA to book a demo yet.

Consideration (Email 2, Day 5): Send a case study or detailed guide relevant to the contact's industry or persona. Include social proof. Soft CTA to explore a related resource.

Decision (Email 3, Day 10): Send a direct CTA to book a demo or talk to a specialist. If the contact engages with this email, update their lifecycle stage and trigger the MQL workflow. If they do not engage, move them to a lower-frequency nurture list rather than continuing the same cadence.

Use if/then branches throughout to personalize based on the contact's industry, company size, or prior engagement. A VP of Sales at a 500-person SaaS company should receive different content than an analyst at a 20-person agency - even if both downloaded the same initial asset.

Why it matters for revenue: Unworked top-of-funnel contacts represent paid acquisition cost without a return. Nurture workflows systematically move those contacts toward a buying conversation without additional headcount.

Example 7: Manage Bounced and Unsubscribed Contacts

A contact status workflow automatically maintains the marketable contact list - reducing platform costs and protecting email deliverability without requiring manual list management.

How it works: Build two separate workflows.

Hard bounce workflow: Trigger on contacts whose email hard bounce date is known (the Email Hard Bounce Date property is populated in HubSpot after a hard bounce event). Set the marketing contact status to non-marketing contact. Optionally, update the lifecycle stage to reflect the contact's inactive status and remove them from any active sequences.

Unsubscribe workflow: Trigger on contacts whose email subscription status changes to unsubscribed. Update the marketing contact status to non-marketing contact. Remove from any active sequences. If the contact has a Salesforce record, sync the unsubscribe status via the HubSpot-Salesforce integration to prevent sales from emailing an unsubscribed contact from Salesforce.

Why it matters for revenue: HubSpot pricing scales with marketable contact volume. Every hard-bounced and unsubscribed contact that remains in marketable status costs money and contributes to deliverability degradation. This workflow recovers both - automatically, as each event occurs, rather than in a quarterly manual cleanup pass.

Example 8: Automate Webinar Campaign Communications

Webinar workflows automate the full communication cycle - invitation, registration confirmation, reminder, and post-event follow-up - eliminating the manual email coordination that makes webinar programs operationally expensive to run.

How it works: Build three workflows for each webinar.

Invitation workflow: Enroll the target contact list and send two to three invitation emails spaced across the pre-event window. Use conditional branches to stop sending invitation emails to contacts who have already registered.

Registration workflow: Trigger on form submission for the webinar registration form. Send an immediate confirmation email with the event details and calendar link. Integrate with Zoom or GoToWebinar to automatically add the registrant to the event platform. Send a reminder email 24 hours before the event and a final reminder one hour before.

Post-event workflow: Trigger on the event date. Send a thank-you email to confirmed attendees with the recording link and any promised resources. Send a "sorry we missed you" email to registered contacts who did not attend, including the recording. For high-engagement attendees - those who stayed for a defined percentage of the event - update the lifecycle stage or lead score and trigger a sales follow-up task.

Why it matters for revenue: Webinar programs produce high-intent leads but require significant operational overhead when managed manually. These three workflows reduce the coordination cost to near zero while ensuring every registrant and attendee receives the right communication at the right time.

Example 9: Create Salesforce Tasks From HubSpot Activity

This workflow bridges the HubSpot-Salesforce integration gap that causes high-intent contact signals to go unnoticed by sales reps who work exclusively in Salesforce.

Hub required: Operations Hub or a connected HubSpot-Salesforce integration with task sync enabled.

How it works: Build enrollment triggers for the high-intent contact actions that should generate immediate sales follow-up: a specific form submission (pricing page, contact us, request a demo), a visit to a key page (pricing, case studies, specific product pages), or a nurture email click on a decision-stage CTA.

When the trigger fires, use the "Create Salesforce Task" workflow action to generate a task directly in Salesforce assigned to the contact's owner. Include in the task description: the specific action the contact took, the page or email they engaged with, the contact's current lead score, and a suggested next step for the rep.

Why it matters for revenue: Sales reps who work in Salesforce do not monitor HubSpot activity feeds. High-intent signals - a prospect visiting the pricing page three times in one week - go unnoticed unless they generate a direct action in the system the rep actually uses. This workflow turns HubSpot behavioral data into Salesforce tasks that appear in the rep's daily queue the same way a manually created task would. For the full integration architecture that makes this sync reliable, see RevBlack's HubSpot Salesforce integration guide.

How Do You Keep HubSpot Workflows From Becoming a Problem?

HubSpot Workflows are one of the most common sources of portal over-customization RevBlack encounters in inherited instances. Each workflow made sense when it was built. After three years and four different admins, the portal has 200 workflows, 90 of them inactive, and nobody is confident about what depends on what.

Four practices prevent workflow accumulation from becoming a maintenance liability:

Document every workflow at creation. Every new workflow gets a description field populated with its purpose, the business process it supports, the team that owns it, and the date it was built. This description is what prevents the next admin from being afraid to touch it.

Associate every workflow with a campaign. Workflows without a campaign association are orphaned by default. Campaign association creates a natural cleanup trigger: when the campaign ends, the workflows associated with it get reviewed.

Audit inactive workflows quarterly. Filter for inactive workflows in the Workflows tool every quarter. For each inactive workflow, confirm nothing references it before archiving. Workflows that have been inactive for more than 90 days with no documented future purpose should be archived, not left in the inactive list indefinitely.

Set a change control standard for new workflows. Any new workflow that affects lifecycle stages, record ownership, or Salesforce-synced fields requires a review step before activation. These are the workflows most likely to produce unintended downstream effects when built without checking dependencies. For the full workflow governance framework, see RevBlack's HubSpot over-customization guide.