- Home
- HubSpot integration
- HubSpot automation
HubSpot's full workflow builder starts at Professional
HubSpot's workflow guide lists Professional and Enterprise plans for creating workflows. Its agent builder page says Starter includes simple automation, and the full builder, with event-based triggers, comes with Professional and Enterprise. Custom code actions need Data Hub Professional or Enterprise, and AI actions use HubSpot Credits.
Which plans get workflows: HubSpot’s pages disagree
HubSpot’s own pages give two answers, so here are both. Its workflow guide, updated November 12, 2026, lists the Professional and Enterprise editions of Marketing Hub, Sales Hub, Service Hub, Data Hub, Smart CRM and Revenue Hub. Its agent builder page says Starter includes simple automation, and the full workflow builder, with event-based triggers and advanced automation, comes with Professional and Enterprise. HubSpot’s Revenue Hub guide says a Professional or Enterprise subscription is required to create workflows. If you run Starter, check what your account allows before you plan around it.
How many workflows you can make depends on your subscriptions. Some kinds, such as quote or contract based workflows, need specific subscription types.
Workflows live under Automation, then Workflows. HubSpot gives three ways to start one: from scratch, with AI, or from a template. With AI, Breeze Assistant drafts the triggers and actions from your prompt. HubSpot suggests writing the prompt as “When [this happens], then [do this]”.
Four trigger types start a workflow
A trigger decides which records enter the workflow. HubSpot’s guide names four types:
- Filter-based. Records that match a set of filters enroll.
- Event-based. Something happens, such as a contact submitting a form.
- Schedule. The workflow runs on a set date or a regular rhythm.
- Webhook. Another system calls HubSpot to start it.
By default, a record enrolls only the first time it meets the triggers. Re-enrollment is a setting you switch on. HubSpot’s own example: enroll every contact who submitted a certain form, send them a marketing email, then assign them to a user.
Custom code needs Data Hub, and AI actions use credits
HubSpot groups actions by type, such as delays, branches, CRM actions and AI actions. A few facts decide what you can build:
- Branches. One value-based branch can split into up to 250 paths for a single property.
- Associations. A workflow can link records, for example contacts and companies whose company names match.
- Invoices. A workflow can create a one-time draft invoice from a deal or a quote.
- AI actions. HubSpot Credits are required to use AI workflow actions. Several are marked BETA, including Data Agent: Custom prompt, Summarize record and Use a custom LLM. The Run Agent action, which starts an AI agent from inside the workflow, carries no beta label.
- Custom code. For Data Hub Professional and Enterprise only.
Workflows on their own use no credits. HubSpot’s agent builder page says they do not consume HubSpot Credits.
Custom code actions must finish in 20 seconds
A custom code action runs your own JavaScript or Python inside a workflow, on Data Hub Professional or Enterprise. Python is still in beta. HubSpot runs the code as a serverless function on AWS Lambda. The limits:
Scroll the table sideways to see every column.
| Limit | Value |
|---|---|
| Run time | Must finish within 20 seconds |
| Memory | Up to 128 MB |
| Secrets | All secret values together, at most 1000 characters |
| Text output | At most 65,000 characters per value |
| Retries | Up to three days after a rate limit, or a 429 or 5XX error from axios or @hubspot/api-client, with at most eight hours between tries. Your code must throw the error (Node.js) or raise it (Python) for HubSpot to retry |
HubSpot says Node.js 16 and 20 no longer get security updates. It asked for such actions to move to Node.js 24 before November 17, 2026, and that date has passed. Since November 3, 2026, you can’t create new Node.js 20 actions. We could not load HubSpot’s changelog post on the change, so check any action still on Node.js 16 or 20 now.
Webhook actions reach your other systems
HubSpot’s pages name two plans here. Its webhook article lists Data Hub Professional or Enterprise. Its API usage guidelines say a Marketing Hub Enterprise subscription lets you use webhook actions in workflows. Check which applies to your account.
The article covers contact-based workflows. A POST webhook sends data out of HubSpot. A GET webhook pulls data in. You can cap how fast the action runs. Webhook calls made through workflows don’t count against HubSpot’s API rate limit, which leaves that limit for your other links.
Sequences and automated emails need different hubs
Sequences send one-to-one sales emails. Automated emails are marketing emails that a workflow sends.
Sequences need Sales Hub or Service Hub, Professional or Enterprise, and each user needs an assigned Sales or Service seat. They send a series of timed sales emails and follow-up tasks. A contact who replies or books a meeting is unenrolled by itself. Sequence emails go out through the user’s own work email, not through HubSpot’s marketing email servers.
Automated emails need Marketing Hub Professional or Enterprise. They reach only contacts who are eligible to receive marketing email. An email that uses deal tokens can only run in deal-based workflows.
HubSpot links logged activities to records by itself
One kind of automatic association covers activities. When someone logs a call, sends an email, books a meeting or adds a note or task, HubSpot can link it to related records. One setting links it to the five most recently associated records of a type. HubSpot’s auto-associations API reads and changes those rules, and it is in beta.
We could not load HubSpot’s article on linking contacts to companies by email domain, so this page does not cover that setting. Inside a workflow, the Create associations action links records on a rule you set, such as matching company names.
Workflows can be built and extended through the API
Code can build a workflow too. You create one with a POST request to /automation/v4/2027-03-beta/flows, and every endpoint needs the automation scope. HubSpot’s Fall 2026 Spotlight lists the Automation Workflows API and the auto-associations API among the new public beta APIs in 2026.09.
An app can add its own steps. Custom workflow actions let an app run tasks inside workflows, such as sending data to an outside API or creating records in another system. HubSpot’s agent tools build on the same idea: they are custom workflow actions made available to HubSpot agents. In that beta, an agent has no CRM data unless a tool gives it some.
Test before you go live. A workflow in a developer test account can enroll at most 100,000 records a day.
Two automation jobs have their own pages
Each page below settles one job in HubSpot:
- HubSpot reporting: what the custom report builder, dashboards, Breeze Assistant and the beta Reporting API can and can’t do.
- HubSpot quotes and RFQs: how Revenue Hub quotes and approvals work, what HubSpot’s closing agent answers, and where an agent reads an incoming request for quote.
Where a workflow stops and an agent starts
A workflow follows fixed rules every time. HubSpot’s agent builder page says a custom agent’s actions vary from one run to the next. So use a workflow when the steps never change. Use an agent when something messy has to be read first, such as an emailed request or a PDF, and a person checks the result.
Our team has taken HubSpot implementation end to end: hubs set up, data moved in, and teams trained on site or remote. For agents that work inside HubSpot, see HubSpot AI agents. For automation across your other systems, see AI automation services.
Questions
Where can I see workflows in HubSpot?
Open Automation, then Workflows. In some accounts the Automation menu sits under More. To create a workflow there you need Edit permissions for workflows or Super Admin rights. HubSpot's workflow guide lists Professional and Enterprise plans for this, while its agent builder page says Starter includes simple automation.
What is an example of a workflow?
HubSpot's own guide gives this one. Enroll every contact who has submitted a certain form. Then send them a marketing email and assign them to a user. A deal example works the same way. When a deal is won, a workflow can create a one-time draft invoice from it. Each step runs without anyone clicking.
What are the four types of workflows?
HubSpot's guide names four types of enrollment trigger. Filter-based triggers enroll records that match filters. Event-based triggers react to something that happens. Schedule triggers run on a set date or rhythm. Webhook triggers start when another system calls in. Workflows also differ by the record they run on, such as contact-based or deal-based.
How do I create a workflow?
Go to Automation, then Workflows, and click Create workflow. Pick From scratch, With AI or From template. Then set the enrollment triggers, decide whether records can re-enroll, and add actions. By default a record enrolls only the first time it meets the triggers. Placeholder actions must be filled in before you can turn the workflow on.
Do HubSpot workflows use credits?
Workflows themselves don't. HubSpot's agent builder page says workflows do not consume HubSpot Credits. AI actions inside a workflow do, because HubSpot says credits are required to use AI workflow actions. So a workflow of delays and emails uses no credits, while one with an AI action does.
Can a HubSpot workflow send data to another system?
Yes, in three ways. A webhook action can POST data out or GET data in. A custom code action can call an outside API in JavaScript or Python, on Data Hub Professional or Enterprise. And an app can add custom workflow actions that create records in external systems. Webhook calls made through workflows don't count against HubSpot's API rate limit.
Sources
Every source behind a figure or a vendor fact on this page, with the day we read it.
- HubSpot Knowledge Base, manage end-to-end revenue in HubSpotRead 18 Nov 2026
- HubSpot Knowledge Base, create workflows (updated 12 November 2026)Read 18 Nov 2026
- HubSpot Knowledge Base, choose your workflow actions (updated 18 November 2026)Read 18 Nov 2026
- HubSpot developer docs, custom code actionsRead 18 Nov 2026
- HubSpot Knowledge Base, trigger webhooks in contact-based workflowsRead 18 Nov 2026
- HubSpot Knowledge Base, create and edit sequencesRead 18 Nov 2026
- HubSpot Knowledge Base, send automated emails in workflowsRead 18 Nov 2026
- HubSpot developer docs, Workflows API (beta)Read 18 Nov 2026
- HubSpot developer docs, auto-associations API (beta)Read 18 Nov 2026
- HubSpot developer docs, custom workflow actionsRead 18 Nov 2026
- HubSpot developer docs, agent tools referenceRead 18 Nov 2026
- HubSpot developer docs, API usage guidelines and limitsRead 18 Nov 2026
- HubSpot developer docs, account typesRead 18 Nov 2026
- HubSpot, agent builderRead 18 Nov 2026
Pages in this section
- HubSpot quotes and RFQsHubSpot quotes need Revenue Hub Professional or Enterprise. The Quotes API, approvals, e-sign rules, the closing agent and where an agent reads an RFQ.
- HubSpot reportingEvery HubSpot plan has dashboards, and custom reports need Professional. The report builder's limits, AI credit rules and the beta Reporting API.
Plan your HubSpot automation
Bring your HubSpot hubs and plans, and the steps your team still does by hand each week. The first call is free.