What to automate first in activation: the HubSpot workflows that mattered

Before anything: what you need in place

Workflows are available on Professional and Enterprise tiers across HubSpot's hubs, and the number you can create depends on your subscription (HubSpot Knowledge Base, updated August 3, 2026). If you want to call an API or do arithmetic inside a workflow, the custom code action needs Data Hub Professional or Enterprise, runs JavaScript or Python in beta, has to finish within 20 seconds and can use up to 128 MB of memory (HubSpot developer docs, accessed October 3, 2026).

HubSpot has renamed some of its hubs recently, so check the names in your own portal against the billing page before you plan around a tier.

You also need one thing that is not a HubSpot feature: a decision about what your activating action is. Everything below depends on it, and user activation is the page on how to find it.

Workflow 1: write the activation event into the CRM

Build this before you write a single email.

What it does: takes the one product event that defines activation and writes it onto the contact record as a date, plus a boolean, plus a couple of counts.

The properties to create: first_session_date, second_session_date, activating_action_date, activated (yes or no), activating_action_count_7d, and signup_source.

How it gets there: a native product integration if one exists, the Forms or CRM API from your own backend, or a custom code action calling your product's API on a schedule. The method matters less than the fact that the date lands on the contact.

Why it goes first: every workflow after this one enrolls on, branches on, or exits on these properties. Build the nudge emails first and you will rewrite all of them the week the activation definition changes, and it will change at least once.

This is the step people skip because it has no visible output. It is also the one that turns HubSpot from a mailing list into something that knows whether your product worked.

Workflow 2: route the signup before a human sees it

Enrollment trigger: a submission on the signup or demo form.

Actions, in order: set a score from the 3 or 4 fields your sales team agreed actually predict a close. Set the owner by rule. Create a task with a due date measured in hours. Post to the Slack channel the owner reads. Stamp an sla_due_at property so you can report on response time later.

Why second: speed to first human reply is the one thing in this stage that is entirely within your control. A lead that waits a day has read two competitors' pages in the meantime.

The detail that matters: route on the fields that predict a close, not the fields that are easy to collect. In practice that is usually the tool they are replacing, the size of the team who would use it, and the deadline behind their search. Company size alone routes a lot of leads to the wrong person.

Workflow 3: the no-second-session nudge

Enrollment trigger: activated is no, and signup date is 2 days ago.

Actions: one email, naming the single next action, with a deep link that lands them on the exact screen rather than the dashboard. If still not activated at day 5, a second email with a different angle, usually a 2 minute recording of someone doing that one action with sample data. At day 9, stop and let them go.

Goal criterion: activated is yes. Set it. A workflow with no goal will keep nudging people who already did the thing, which is the fastest way to make new users distrust your email.

Why third, not first: you cannot write this email until you know the activating action and have it in the CRM, which is what the first two workflows are for. Teams that build this first end up sending a generic "need help getting started" email, which reads as a mailing list and performs like one.

Workflow 4: tell the company when somebody activates

Enrollment trigger: activating_action_date is known.

Actions: move the lifecycle stage, notify the owner, and only now start the sales sequence.

This is the workflow that changes how people spend their day. Sales stops working an alphabetical list of signups and starts working the people who have proved the product does something for them. Nothing in this workflow sends an email to a customer, which is why it is easy to leave unbuilt and expensive to leave unbuilt.

Workflow 5: the stuck halfway nudge

Enrollment trigger: first_session_date is known, activating_action_count_7d is 0, and the user started but did not finish the activating action more than 24 hours ago.

Actions: one in-product nudge if you can trigger one, and one email that picks up exactly where they stopped.

This is the highest-yield audience in the whole stage, because intent is already proven. They tried. Something in the way stopped them, and there are usually only 2 or 3 things it can be. Ask them which one, in the email, with a reply address that goes to a person.

The one that did nothing

A 6-email education sequence over 3 weeks, one per feature, enrolled on signup.

The open rates were respectable. The effect on activation, measured against a holdout, was nothing I could distinguish from zero. We turned it off and nobody noticed.

Why it failed is worth sitting with, because it is the default thing teams build. It enrolled on a date rather than on a behavior, so it talked to people who had already activated, people who had already left, and people stuck on something email number 4 was never going to mention. Calendar-based sequences are for things that happen on a calendar, like a renewal. Everything in activation should enroll on a behavior and exit on a behavior.

The mistakes that cost weeks

No goal criteria. This is the one that costs six weeks, because you do not find out from a report. You find out when a customer forwards you three emails asking them to do something they did a month ago. Every activation workflow gets a goal criterion on the day it is built.

Re-enrollment turned on without thinking. A record currently enrolled in a workflow cannot re-enroll in it until it completes, and you choose which triggers re-enroll (HubSpot Knowledge Base, updated August 3, 2026). Decide deliberately for each workflow, and write the decision in the description field.

Two workflows that both send a welcome email. This happens in every portal that has existed for more than two years. Keep one sheet listing every workflow, its trigger, its goal, its owner and whether it sends anything to a customer. Ten minutes a month, and it prevents the duplicate-email problem permanently.

Naming. Prefix them: ACT-01 activation event, ACT-02 routing, ACT-03 no second session. A portal with 40 workflows named after whoever built them is a portal nobody will touch.

Letting a workflow be the only place a business rule is written. If the definition of a qualified lead exists only inside a filter in HubSpot, nobody outside the person who built it knows what the company means by qualified. Write it in a document, then build the filter from the document.