Which HubSpot workflows can I build without Data Hub Professional (formerly Operations Hub Professional)?
Short answer
Nearly all of them. Every workflow in this pack runs on native actions at Sales, Marketing or Service Hub Professional: rotation, ... property edits, tasks, branches, delays, internal notifications, Slack alerts and marketing emails.
No code, no Data Hub, no third-party tool. Data Hub, now sold as Data Hub, adds custom coded actions, the Format data action and native webhooks on top. Expect twenty to forty-five minutes per workflow.
Read the whole answerShow less
What a spec looks like
The nine sections, and the files
Every spec follows the same nine sections, so a team reads one and knows how to read all of them.
- Outcome, when to use it and when not to
- Prerequisites: properties, lists, tiers, with the JSON to create them
- Enrollment and re-enrollment, then every step with its parameters
- Known pitfalls, a test plan, variants, and the YAML build spec
PDF, Markdown, properties JSON, workflow JSON, custom code where used. Test plan and known pitfalls in every spec.
Each spec states its minimum tier. The 12 free ones open in full, the others show their public preview.
The 40 specs, in build order
Get the lead to a rep
Rotation by flat pool or by territory, routing on lifecycle change and on trial tier, plus the cleanup when a rep is deactivated.
What each spec doesHide
Show the 2 other specs in this groupShow fewer
Keep the pipeline honest
Stage tasks, forecast category, next-step chasing, win alerts, the closed-won handoff into onboarding, and the auto-renewal window.
What each spec doesHide
Show the 9 other specs in this groupShow fewer
Move the lifecycle and nurture around it
Score to MQL, MQL to SQL with the sales ping, aging alerts, list hygiene, locked first-touch source, and two email tracks.
What each spec doesHide
Show the 4 other specs in this groupShow fewer
Route tickets and act on feedback
Ticket routing by product and by channel, the first-response breach alert, a response timestamp, and the detractor and promoter branches.
What each spec doesHide
Show the 3 other specs in this groupShow fewer
Flag what is missing before it skews reporting
Required fields on contacts and companies, the three association-hygiene checks, and the contract date that renewal automation depends on.
What each spec doesHide
Show the 2 other specs in this groupShow fewer
The 3 things that break this, and how the specs stop them
Native rotation does not rebalance, and it does not replace a leaver
Rotate record to owner distributes by assignment count across the pool as it stands at run time.
Adding a rep does not rebalance what came before, a rep on holiday still gets their turn, and a deactivated user is skipped rather than replaced. Pool membership is a maintenance job, not a setting.
How the specs stop itShow less
A workflow cannot stop a bad record from being created
Workflows react after the record exists, so every required-field and association check here is detect and flag, never block.
The create-form setting gates manual creation in the interface only, not imports, API calls or records made by other workflows. Plan a review queue, and expect that queue to need a second workflow to clear itself.
How the specs stop itShow less
Some actions do not exist at any tier
There is no merge action, no Remove from workflow action, and no native wait-until-a-task-is-complete step.
There is no manager-of-the-owner lookup below Enterprise teams either, which is why several specs here carry an explicit Manager or Escalation contact property. Data Hub does not add these. Knowing they are missing saves the afternoon you would spend looking.
How the specs stop itShow less
What this bundle builds
The question underneath this page is a budget question. Someone read a blog post, saw a custom coded action in the screenshots, and now believes the automation they need costs another line on the renewal. Usually it does not.
This bundle is the working set of a portal that runs on Sales, Marketing or Service Hub Professional. Leads get an owner within minutes and the owner gets a task. Deals pick up the right next step at each stage, chase their own missing fields, and hand off cleanly the moment they close. Contacts move from lead to MQL to SQL on a documented threshold, with the sales ping attached. Tickets route by product and by channel, and a missed first response wakes somebody up. Feedback gets acted on instead of read.
The last component is the one people skip and then regret. Six flags catch the records that quietly break everything else: a contact with no company, a deal with no company, a ticket with no contact, a company with no domain, a contract with no end date. None of them needs code. All of them need a real owner on the other end of the queue.
Read the restShow less
How the pieces fit together
Routing first, because almost everything downstream assumes a record has an owner. Start with the flat rotation, then add the territory version once the territory field is reliable, then the lifecycle and trial-tier routes on top. The deactivated-owner cleanup comes last and depends on an admin habit, not on a property.
Deal hygiene next, since stage tasks and forecast category both branch on your pipeline's internal stage names, which you should confirm once and reuse everywhere. The closed-won specs share three properties, Onboarding Owner, CS Handoff Notes and a sent flag, so build the handoff task before the summary email and the checklist.
Lifecycle sits beside that and depends on one number, the score threshold, kept in a single workflow so sales gets one answer. The ticket set needs SLA goals configured on the help desk pipeline first, or the breach alert enrolls nothing and fails quietly. Leave the flags for last: they depend on nothing, and by then you know which gaps your portal actually has.
What you get
- 40 specs, each as PDF and Markdown, with enrollment criteria, step list, diagram, test plan and the known pitfalls written out.
- Properties JSON: 52 property definitions across contacts, deals, companies and tickets, including the status and flag properties that stop these workflows re-triggering on their own writes.
- Workflow JSON in Automation API format, switched off, so nothing runs before you have read it.
- Custom coded actions: none. No private app token, no secret to store, no execution limit to watch.
- Tier stated per spec, at the top: 23 Sales Hub Professional, 9 Marketing Hub Professional, 8 Service Hub Professional.
- Static lists and review queues named and specified, not left as an exercise.
- Test plans that cover the negative path, the unowned record, the blank field, the ticket created in a later stage.
- Install in one click for Full and Agency buyers.
Who it is for, and who should skip it
This is for the admin or RevOps person who inherited a Professional portal and needs it working this quarter, and for the consultant who rebuilds the same twenty workflows on every new client and would rather not retype the pitfalls. Roughly nineteen hours of build sits in here, at an honest pace with testing.
Skip it if you are on Starter, where only simple automation exists and most of these specs will not load. Skip it if you already own Data Hub and came for the code, since the power pack is the page you want. And if you want both sides plus the other nine categories, the full library costs less than three packs.
Questions admins ask
Do HubSpot workflows require Data Hub Professional?
No. Workflows come with the Professional and Enterprise tiers of Marketing, Sales and Service Hub, and that action list already covers rotation, property edits, tasks, internal notifications, delays, branches, list membership and marketing emails. Data Hub, now sold as Data Hub, adds a specific set of actions on top rather than unlocking automation itself.
What does Data Hub Professional add to a workflow?
Three things you can see in the action picker: custom coded actions in JavaScript or Python, the Format data action for string and number cleanup at scale, and native webhooks for outbound calls. The cross-object property copy across an association sits there too. The specs that need those live in the Data Hub power pack, not here.
When is Data Hub worth buying?
When you need a lookup or a search that the filter language cannot express, text normalization at a volume nobody will do by hand, or a call out to another system. If all you need is a computed number, a calculated property gets you there on any Professional tier. Buy it for the code, not for the automation.
Can a workflow enforce a required field?
Not as a hard block, on any tier. Six specs here take the honest route: detect the gap at creation, write a status property, add the record to a review list and assign a task to a real owner. Pair that with required properties on the form or on the pipeline stage, which is the only preventive control HubSpot offers.
Which hub do the ticket specs in this bundle need?
Service Hub Professional. Tickets only exist where Service Hub is provisioned, and the SLA goals that the first-response breach alert reads are set on the help desk, not on a Sales Hub pipeline. Sales Hub Professional does not grant them. The same applies to the NPS specs, since customer loyalty surveys are a Service Hub Professional feature.
Read 12 complete specs before you pay.
One per category, same format as the paid ones. Email only, no card.
We email the link, then a short note when specs change. Nothing else.
Here it is. Download the pack now (.zip) The link is in your inbox too.
Browse the library