HubSpot
Workflows

The event that starts every workflow — eight categories, each with a different use case.

Everything a workflow can do — organised by category. These are your tools.

If/then logic that makes workflows intelligent — routes contacts down different paths based on their data.

A branch splits the workflow into two or more paths. Each path has its own sequence of actions. After the branch, paths can rejoin or remain separate. Branches can be nested inside other branches.

Pausing execution at a specific point — the timing layer that makes automation feel human.

The complete onboarding workflow — showing every node type in a real-world sequence.

Every HubSpot portal needs these 8 workflows. Without them, the CRM runs on manual processes and data degrades.

• 01Lifecycle Stage: Lead → MQL promotion
  Trigger: Lead Score ≥ threshold AND meets ICP criteria (industry, size, title)
  Set Lifecycle = MQL Set Lead Status = New Set MQL Date = Today Notify assigned SDR Create review task
• 02Deal close → Customer promotion + onboarding
  Trigger: Associated Deal Stage = Closed Won
  Set Lifecycle = Customer Set Customer Date = Today Notify CS Slack Send welcome email Create onboarding task Enrol in onboarding sequence
• 03Blank Lifecycle Stage — catchall default
  Trigger: Lifecycle Stage is unknown AND Contact is created
  Set Lifecycle = Lead Set Lead Status = New
• 04Bad Timing re-engagement
  Trigger: Lead Status = Bad Timing AND Follow-up Date = today (date-based, re-enrollment enabled)
  Set Lead Status = New Clear Follow-up Date Notify owner Create re-engagement task
• 05Stale MQL alert — SLA enforcement
  Trigger: Lifecycle = MQL AND Lead Status = New AND MQL Date > 2 business days ago
  Notify SDR manager Create urgent task for manager
• 06Form submission — post-form follow-up
  Trigger: Contact submits [specific form]
  Set Lifecycle = Lead Set Lead Status = New Send confirmation email Notify SDR Create follow-up task
• 07Deal stage automation
  Trigger: Deal Stage changes to [key stage]
  Create task for deal owner Send internal notification Update contact lifecycle
• 08Date-stamp properties — funnel velocity data
  Trigger: Lifecycle Stage = MQL (or SQL, or Customer) — separate workflows per stage, re-enrollment OFF
  Set MQL Date = Today (don't overwrite) [Repeat for SQL Date, Customer Date]

1. Choose the object type — Contact, Company, Deal, Ticket, etc. This determines what triggers, filters, and actions are available.
2. Choose: Start from scratch or Use a template — For learning: use templates to understand structure. For production: always start from scratch to ensure every condition is deliberate.
3. Set the enrollment trigger — Click "Set up trigger." Choose the event type and configure the specific condition (property, form, list, date).
4. Add enrollment filters — After the trigger, narrow who actually enrolls. This is where you add industry = SaaS, company size ≥ 50, lifecycle = Lead, etc.
5. Configure re-enrollment — In the left panel Settings tab: decide if contacts can re-enroll. Default is off. Enable only if needed.
6. Add actions — Click the "+" to add actions. Build in logical order: set properties first (data before actions), then send emails, then notify, then create tasks.
7. Add delays between timed actions — Between sequential emails or tasks, insert delays. Use "until a day and time" for actions that should feel human-timed.
8. Add branches where paths diverge — Insert an If/Then branch when different contacts should receive different experiences based on their properties.
9. Set unenrollment conditions — Settings → Unenrollment and suppression. Add: "Contact's Lifecycle Stage is any of Customer, Evangelist" for all nurture workflows.
10. Name the workflow with your convention — [Contact] MQL Promotion — Lead Score 50+. Add a description with purpose, owner, and last-updated date.
11. Check eligible contact count — Before activating, HubSpot shows how many existing contacts are eligible. Verify this matches your expectations. If wrong, fix the trigger/filter before activating.
12. Activate — Toggle "Turn on." Decide: enroll existing eligible contacts, or only new contacts going forward? For most workflows: only new contacts going forward.

A workflow library without governance becomes unmaintainable within 6 months. Structure from day one.

The naming convention

Examples

Quarterly governance checklist

• 🔍
  Review all active workflows — any that enrolled 0 contacts in 30 days should be investigated (trigger broken or audience too narrow)
• 🗄️
  Pause and archive any workflow for a campaign or initiative that has ended — don't leave inactive workflows cluttering the list
• 📝
  Verify every workflow has a description — purpose, owner, last updated date
• ⚠️
  Check for conflicting workflows — two workflows both trying to set the same property can create unexpected results
• 📊
  Review enrollment counts — any workflow with unusually high or low enrollment vs expectation needs investigation

How building 8 core workflows transformed a B2B SaaS company's revenue operations in 3 weeks.

Week 1 — Data foundation

• 01
  Built Workflow 03 (blank lifecycle default) first. Ran overnight — assigned Lifecycle Stage = Lead to 840 contacts that had none. CRM data went from 43% coverage to 97% in 8 hours.
• 02
  Built Workflow 08 (date-stamp properties). Created MQL Date, SQL Date, Customer Date custom properties. Retroactively stamped Customer Date from deal close dates via import. Now had funnel velocity data for the first time.

Week 2 — Handoff automation

• 03
  Built Workflow 01 (MQL promotion). Facilitated joint session with CMO and VP Sales to agree on MQL criteria. Workflow activated — first 12 MQLs auto-promoted with SDR notifications within the first 3 hours.
• 04
  Built Workflow 02 (deal close → customer onboarding). CS team notified within seconds of every new close. First week: 3 deals closed, all 3 onboarding sequences started automatically, CS manager called it "magic."
• 05
  Built Workflow 05 (stale MQL alert). First alert fired within 6 hours of activation — an MQL had been sitting at "New" for 72 hours. SDR had "missed it in their inbox." Problem identified and fixed.

Week 3 — Pipeline automation + re-engagement

• 06
  Built Workflow 04 (Bad Timing re-engagement). 47 existing Bad Timing contacts with Follow-up Dates populated. First week: 8 re-engaged automatically, 2 booked calls.
• 07
  Built Workflow 06 (form submissions). Connected to all 3 active lead-gen forms. Every form submission now triggers lifecycle stage set, SDR notification, and confirmation email within 30 seconds.

30-day outcome

• 01 — No unenrollment conditions on nurture workflows
  Every lead nurture workflow must unenroll contacts when Lifecycle = Customer. Without this, paying customers receive "discover why you should try us" emails indefinitely. Add unenrollment conditions before activating any outbound sequence.
• 02 — Not enabling re-enrollment when the trigger can fire multiple times
  A lead scoring workflow that only runs once misses contacts who later hit a higher threshold. Check: should this workflow run once per contact, or every time the trigger condition is met? Wrong setting = workflow appears to "stop working" for returning contacts.
• 03 — Activating without checking eligible contact count
  HubSpot shows how many existing contacts will immediately enroll. If this number is wildly different from your expectation — stop. Fix the trigger or add a date filter before activating. Activating with too many eligible contacts can send thousands of unexpected emails in seconds.
• 04 — Overwriting manually-set properties without "don't overwrite"
  A workflow setting Lead Status = New every time a contact reaches MQL erases a rep's manually-set "In Progress" or "Bad Timing" status silently. For properties reps also manage, always enable "Don't overwrite existing values."
• 05 — Building monolithic workflows with too many actions
  A 45-action workflow that handles everything is impossible to debug, maintain, or hand off to another admin. Split into focused, single-purpose workflows. One workflow, one job.
• 06 — No naming convention or description
  After 6 months: 80 workflows named "Test," "Copy of," "New MQL flow v3." Impossible to audit. Future admins spend hours reverse-engineering what each does. Enforce naming and descriptions from day one.
• 07 — Testing in production
  Never build and activate a new workflow directly in your live portal. Test in sandbox. Verify triggers, filters, actions, and re-enrollment behaviour with test contacts. Then rebuild in production. This is especially critical for any workflow that sends emails.

• 📋
  One workflow, one purpose. If you can't explain a workflow in one sentence, it's doing too much. Split it. Small, focused, named workflows are infinitely easier to build, debug, maintain, and hand off.
• 🏷️
  Naming convention on every workflow. [Object] [Team] Purpose — Trigger. Non-negotiable. Enforce it for every workflow in every portal you manage.
• 📝
  Description field is documentation. Purpose, owner, last-updated date, any gotchas. Future-you will thank present-you every single time.
• 🧪
  Test in sandbox before production. Always. No exceptions for workflows that send emails, set properties, or create records.
• 🔢
  Check eligible count before activating. The 10-second check that prevents hour-long cleanup sessions. If the count is unexpected, investigate before proceeding.
• 🚪
  Set unenrollment conditions on every nurture flow. Lifecycle = Customer is the minimum. Add: email opted out, form submission (self-qualified), sequence enrolled (already in sales outreach).
• 📅
  Use "delay until day and time" for human-feeling automation. Actions that fire at 3am on Sunday erode trust in the system. Delays until Monday 9am make automation feel intentional.
• 🗓️
  Quarterly workflow audit. Review all active workflows. Pause/archive inactive ones. Check enrollment counts. Look for conflicts. Governance is how you maintain a healthy system as it grows.

Do this in your free HubSpot sandbox — approximately 60 minutes across three workflows.

Workflow 1 — Blank lifecycle catchall (10 min)

1. Automation → Workflows → Create workflow → Contact-based → Start from scratch
2. Trigger: Contact property → Lifecycle Stage → is unknown
3. Action: Set contact property → Lifecycle Stage → Lead. Enable "Don't overwrite."
4. Name it: [Contact] AUTO — Lifecycle Default — New Contact. Add description.
5. Before activating: check eligible count. Activate with "Enroll existing contacts" ON — you want all blank-stage contacts to get a stage.

Workflow 2 — Form submission follow-up (20 min)

1. Create a new Contact-based workflow. Start from scratch.
2. Trigger: Marketing → Form submission → any form you created earlier.
3. Enrollment filter: Lifecycle Stage is not equal to Customer (don't enroll existing customers).
4. Actions: (1) Set Lifecycle Stage = Lead. (2) Set Lead Status = New. (3) Send internal email notification to yourself. (4) Create task: "Follow up with {{contact.firstname}} — form submitted today."
5. Unenrollment: Lifecycle Stage = Customer.
6. Name it. Add description. Activate with "Don't enroll existing" option.
7. Submit your test form from the previous module. Check: did the Contact get the stage? Did you receive the notification? Was a task created?

Workflow 3 — Branching based on company size (30 min)

1. Create a new Contact-based workflow. Trigger: Lifecycle Stage changes to Lead.
2. Filter: Lead Status = New (only newly created leads, not existing ones).
3. Action: Delay until next business day at 9:00am.
4. Add an If/Then branch: condition = Company Employees ≥ 50.
5. YES path: Set Lead Status = In Progress. Create task: "Enterprise lead — call today."
6. NO path: Set Lead Status = New. Send email: a self-serve resource email (you can use any published email).
7. Unenrollment: Lifecycle Stage is any of Customer, Evangelist.
8. Name it. Add description. Activate for new contacts only.
9. Create two test contacts manually: one with Employees = 100, one with Employees = 10. Watch them flow through different paths.