What we do
Tools
Industries
Department
How we workLet's talk →
Home/HubSpot/HubSpot Workflows
HubSpot

HubSpot Workflows: How a Workflow Works, and Why Yours Did Nothing

A HubSpot workflow enrolls records that meet a trigger, then runs actions on them: delays, branches, emails, tasks, property changes. It runs on its own for every matching record, contacts, companies, deals, tickets or custom objects. Here's how the pieces fit, some recipes to copy, and the fixes for the usual surprises.

The four parts of every workflow

Object type. What the workflow is about: a contact, company, deal, ticket or custom object. You choose it first and can't change it later.

Automation Workflows Create workflow

Enrollment trigger. The moment a record gets in: a form submission, a property value, list membership, a date, or an event such as a page view.

Actions. What happens next, in order: delays, if/then branches, emails, tasks, internal notifications, property updates, owner rotation.

Settings. Re-enrollment, unenrollment, timing windows and suppression lists. Most surprises come from here, not from the actions.

HubSpot workflow examples you can build today

Each one is a trigger and a short chain of actions, all inside HubSpot.

01

Rotate new leads to reps

Contact workflow. Trigger: lifecycle stage becomes lead and the owner is unknown. Action: rotate record to owner across your reps, then create a call task due the same day.

02

Flag a deal that has gone quiet

Deal workflow. Trigger: deal has sat in one stage for 14 days (use the date entered stage). Action: notify the deal owner and their manager, and add a task to review it.

03

Update lifecycle stage on a closed deal

Deal workflow. Trigger: deal stage is closed won. Action: set the associated contacts and company to customer, so marketing stops nurturing them.

04

Nurture after a content download

Contact workflow. Trigger: submits the download form. Actions: three emails a few days apart, with unenrollment when the contact books a meeting.

05

Route a ticket by product

Ticket workflow. Trigger: ticket created. Action: branch on the product property and assign to the right team's queue, with a priority bump for your top accounts.

Why a HubSpot workflow enrolled nobody, or everybody

Existing records never enrolled

How you'll know: Contacts who already matched the trigger before you turned the workflow on aren't in it.

Fix: When you turn a workflow on, HubSpot asks whether to include records that already meet the trigger. If you chose no, only new matches enroll. Enroll the backlog by hand, for example by building a list of them and enrolling it.

Contacts went through once and never again

How you'll know: The trigger fires a second time for the same contact, and nothing happens.

Fix: Re-enrollment is off by default. Turn it on in the workflow's settings for the specific trigger that should let a record back in.

The whole database got the welcome email

How you'll know: A broad trigger, like "email is known", met every existing contact the moment it went live.

Fix: Narrow the trigger, and answer no to enrolling existing records unless you really mean it. Test with a single record first.

An email action skipped people

How you'll know: The action history shows contacts passing the email step without receiving it.

Fix: Check that they're marketing contacts and haven't unsubscribed from that email type. Workflows respect both, which is correct but easy to forget.

Two workflows fight over the same property

How you'll know: Lead status or owner changes, then changes back minutes later.

Fix: Find every workflow that sets that property and give the job to one of them. The others should read it, not write it.

Workflow or sequence: which one you actually want

Workflow

Automatic, for every matching record

  • Enrolls records on its own when they meet the trigger.
  • Works on contacts, companies, deals, tickets and custom objects.
  • Sends marketing email, updates fields, assigns owners, creates tasks.
Sequence

A rep's own follow-up

  • A rep enrolls one contact at a time, by choice.
  • Emails go from the rep's own inbox, mixed with call and task reminders.
  • Stops by itself when the contact replies or books a meeting.

If no person should have to decide who gets it, use a workflow. If a rep is following up with someone they spoke to, use a sequence.

What a workflow can reach, and what it never sees

Calling out to other systems costs a tier. Custom code actions come with Data Hub Professional or Enterprise (Data Hub is HubSpot's current name for Operations Hub). The Send a webhook action needs Data Hub Professional or Enterprise, or an Enterprise hub. Without one of those, a workflow mostly acts inside HubSpot and through App Marketplace apps that add their own actions.

A workflow only reacts to HubSpot data. It can't notice an unpaid invoice in your accounting system, a shipment that left the warehouse or a job finished in your field software. It only notices when that fact is written onto a property it's watching. If nothing writes it, the workflow never fires.

Building workflows by API is now possible, in beta. HubSpot's v4 Automation API can create, update and delete workflows as well as enroll records, which makes it possible to copy one workflow across many portals. An update replaces the whole definition, so export it first. Our HubSpot API page has the details.

The first two gaps are where n-frames works on HubSpot: feeding outside events onto the records your workflows watch, and building the system on the receiving end when a workflow hands something off. If the job fits inside HubSpot, build it there. It's the better tool for that.

Questions people ask

What's the difference between a HubSpot workflow and a sequence?

A workflow enrolls every record that meets its trigger with nobody choosing, and can act on contacts, companies, deals, tickets or custom objects. A sequence is a rep's one-to-one email and task cadence for a contact they pick, sent from their own inbox, and it stops when the contact replies. Workflows run the process; sequences run a rep's follow-up.

Can a HubSpot workflow call an external API?

Yes, through the Send a webhook action, which needs Data Hub Professional or Enterprise or an Enterprise hub, or a custom code action, which needs Data Hub Professional or Enterprise. Some App Marketplace apps also add their own workflow actions that talk to their product. Without those, a workflow can't call an outside API directly.

Is there an API to create or edit a HubSpot workflow?

Yes, now. HubSpot's Automation API v4, currently in beta, can list, create, update and delete workflows, and older endpoints can enroll records. Updates replace the whole definition and need its current revision ID, so fetch it, edit it and send the full thing back.

Why isn't my HubSpot workflow enrolling contacts who already existed before I turned it on?

When the workflow was turned on, the option to enroll records that already met the trigger was left off, so only new matches get in. Enroll the existing contacts manually, for example from a list. If they already went through once, re-enrollment has to be on as well.

What are some common HubSpot workflow examples?

Rotating new leads to reps, alerting an owner when a deal sits in one stage too long, setting contacts to customer when a deal closes, a nurture series after a form fill, and routing tickets by product. The recipes above show the trigger and actions for each.

Which HubSpot plan includes workflows?

The full workflow builder comes with the Professional and Enterprise tiers of HubSpot's hubs. Starter tiers get simpler automation tied to forms and emails. HubSpot moves features between tiers from time to time, so check its pricing page for the current split.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.