Skip to main content

HubSpot automation and workflows for revenue teams

OneGTM builds HubSpot automation for revenue teams. We set up the HubSpot workflows that decide who owns a lead, what lifecycle stage it sits in, which data gets filled in when a record is created, and when sales takes over from marketing. Where native workflows run out, we add custom code, Clay, or a Claude Code agent that writes back into HubSpot.

By Garrett Wolfe, founder of OneGTM. Updated .

Key takeaways

  • Full HubSpot workflows start at Professional (up to 300) and Enterprise (up to 1,000). Sales Hub Starter caps you at 50 with restricted triggers and actions.
  • Most broken HubSpot portals have the same problem: leads with no owner, and lifecycle stages nobody trusts.
  • Enrich a record before you route or score it. Rules can only act on fields that are filled in.
  • Custom code actions run for 20 seconds at most. Anything heavier belongs outside HubSpot, writing back through the API.

What we automate in HubSpot

Lead routing

Owner rotation by territory, segment, or rep capacity, with a Slack ping and a task so a new lead gets worked the same hour.

Lifecycle stages

Stages that move forward on real events, like a demo request or a deal being created, so funnel reports mean something.

Rules of engagement

Who owns an account, when a contact follows the company owner, and when a quiet account goes back into the pool.

Enrichment on create

New companies and contacts get industry, headcount, and title filled in before any routing or scoring rule runs.

Scoring

Fit and engagement scores in HubSpot's lead scoring tool, or an AI fit score written to a property from outside.

Sequences and handoffs

Marketing to SDR to AE handoffs, sequence enrollment, and deal creation when a meeting is booked.

Common HubSpot workflows and what they fix

These are the workflows we set up most often. Each one is small on its own. Together they replace the spreadsheet and the Slack thread where leads get handed around by hand.

WorkflowTriggerActionsWhat it fixes
Inbound lead routingContact created from a form, owner is unknownBranch on country and company size, rotate to an owner in that team, create a task, notify in SlackDemo requests sitting unowned overnight
Lifecycle stage updatesDemo form submitted, meeting booked, or deal createdSet lifecycle stage to SQL or Opportunity, stamp the date in a propertyStages that never move, and funnel reports nobody believes
Rules of engagementContact associated with a company that has an ownerCopy the company owner to the contact, alert the owner if a different rep had itTwo reps emailing the same account
Enrichment on createCompany created with a domainCall an enrichment provider through a webhook or custom code, write industry and headcount backBlank fields that break routing and scoring
Score thresholdLead score crosses a set numberSet lead status, assign or notify the owner, create a call taskHot leads waiting in a list nobody checks
Meeting booked handoffMeeting booked from an SDR sequenceCreate a deal in the first stage, assign the AE, post a summary in SlackAEs walking into calls with no context
Stale lead recyclingOwned lead with no activity for 30 daysClear the owner or move to nurture, log the reasonLeads parked with reps who stopped working them
Closed lost follow-upDeal moves to Closed LostRequire a loss reason, create a re-engage task 90 days outLost deals that never get a second look

Enrolling contacts into a sales sequence from a workflow needs Enterprise. On Professional, reps enroll by hand or you trigger the next step another way.

Native HubSpot workflows vs custom automation

Start native. A HubSpot workflow is visible to your admins, it logs every enrollment, and it survives the consultant leaving. Go custom only for the steps HubSpot can't do on its own.

Native workflowsCustom code actionOutside HubSpot (Clay, n8n, Claude Code)
Good forRouting, stages, tasks, notifications, emailsShort calls to an API, small calculations, formattingEnrichment waterfalls, AI research and scoring, multi-system jobs
Plan neededProfessional or Enterprise (Starter is limited)Data Hub Professional or EnterpriseAny plan with API access
Limits300 workflows on Professional, 1,000 on EnterpriseJavaScript or Python, 20 seconds and 128 MB per runWhatever the external tool allows
Who can change itAny HubSpot adminSomeone who reads codeWhoever owns that tool
Where it breaksLogic that needs outside data or judgmentLong jobs, retries, rate limitsSync drift if nobody watches it

The pattern we use most: a native workflow fires on the trigger, a webhook or custom code action hands the record to Clay or a Claude Code agent, and the result comes back as HubSpot properties that the next native workflow acts on. Your team still sees the whole flow in HubSpot. Picking the outside tool is its own question, covered in workflow automation tools.

HubSpot automation we have built

  • Patlytics. HubSpot rules of engagement deciding which rep owns which account, alongside a title-fit AI prompt and a reply bot.
  • SuperDial. HubSpot rep views, Slack intent channels, and AE routing by call volume, on top of a Clay TAM scoring model.
  • Statewise. Company, signal, and person data built in Deepline and Supabase, synced into HubSpot with the outbound activity from Instantly.

More of this kind of work, outside HubSpot too, is on AI automation consulting. For CRM structure, reporting, and the rest of RevOps, see our RevOps agency page.

How a HubSpot automation project runs

  1. Audit the portal. We list every active workflow, find the ones that overlap or fight each other, and check which fields routing depends on.
  2. Write the rules down with sales and marketing leads: who owns what, what moves a stage, when a lead goes back to the pool.
  3. Build and test on a filtered set of records first, then turn enrollment on for everyone.
  4. Hand over with a short doc per workflow and a Loom walking through it, so your admin can change it without us.

Still choosing a CRM or a partner?

If you are not sure HubSpot is the right CRM, compare it in HubSpot vs Salesforce and Attio vs HubSpot. If you need a full implementation, including migration and Marketing Hub content, a HubSpot solutions partner may fit better than us. The HubSpot and CRM partners list compares them.

HubSpot automation FAQ

What are HubSpot workflows?
HubSpot workflows are the automation tool inside HubSpot. Each one has enrollment triggers (a form fill, a property change, a new record) and a list of actions that run on every enrolled record, such as setting a property, rotating an owner, creating a task, sending an internal notification or sending an email.
Which HubSpot plans include workflows?
Full workflows come with Professional and Enterprise. HubSpot's Sales Hub pricing page lists up to 300 fully customizable workflows on Professional and up to 1,000 on Enterprise. Sales Hub Starter allows up to 50 workflows with restricted triggers and actions, and Marketing Hub Starter has simple workflows attached to forms and emails.
How does marketing automation with HubSpot work?
Marketing Hub workflows enroll contacts when they fill a form, open an email, visit a page or match a list, then send emails, update lifecycle stage and score, and hand the contact to sales when it qualifies. It works best when the handoff to sales is automated too, so a qualified lead gets an owner and a task the same minute.
Can HubSpot automate emails?
Yes. Marketing Hub workflows send marketing emails on a schedule or after a trigger, and Sales Hub sequences send one-to-one emails from a rep's inbox with tasks in between. A sequence stops when the contact replies or books a meeting. Enrolling contacts in sequences from a workflow needs Enterprise.
When do you need custom code instead of native HubSpot workflows?
When a step needs data or logic HubSpot doesn't have: calling an enrichment API, matching a lead to an account by domain with fuzzy rules, or asking an AI model to classify a record. Custom code actions (JavaScript or Python, with Data Hub Professional or Enterprise) cover short jobs under 20 seconds. Longer jobs run outside HubSpot in Clay, n8n or a Claude Code agent and write back through the API.
Do you build HubSpot automation for clients?
Yes. OneGTM builds HubSpot automation for revenue teams: lead routing, lifecycle stages, rules of engagement, enrichment on create, scoring and sales handoffs. Past work includes HubSpot rules of engagement for Patlytics and HubSpot rep views with AE routing by call volume for SuperDial.

HubSpot portal full of workflows nobody understands? That is a good place to start.

Scope your HubSpot automation

Tell me what's breaking in HubSpot. I reply the same day.

Call with Garrett
Where did you hear about us? (optional)

Takes about 20 seconds. Times show up right here, and the call is with Garrett directly. See our privacy policy.

Rather do it the old way? team@getaob.com LinkedIn