Quick answer
HubSpot announced Agent Hub and Agent Builder in public beta for Professional and Enterprise customers on July 23, 2026. That statement establishes a product and a dated plan boundary; it does not guarantee that every Professional or Enterprise portal, Hub, seat, role, country, or user sees identical access.
Check the live portal and contract before designing a workflow. Separate beta enrollment, subscribed Hub, edition, seat, user permission, CRM data access, integration permission, price, limits, support, and production-readiness decisions.
Access checklist
| Check | Question to answer |
|---|---|
| Portal | Which HubSpot account and business unit owns the workflow? |
| Subscription | Which Hub or Customer Platform bundle is Professional or Enterprise? |
| Beta | Is Agent Hub and Agent Builder currently enabled for this portal? |
| Seat and role | Who can view, build, activate, change, and monitor agents? |
| Data | Which CRM objects, fields, transcripts, signals, and connected sources are available? |
| Action | Which records, workflows, messages, integrations, and webhooks can the agent affect? |
| Commercial | Is access included, metered, limited, or subject to separate terms? |
Do not buy or upgrade solely from a dated launch article. Capture the exact live quote, billing term, included capacity, renewal, tax, cancellation, support, and data-processing terms.
Agent Hub and Agent Builder are different surfaces
Agent Hub is the operating view. HubSpot says it can show live status and performance, identify inactive agents, open Agent Builder and Agent Marketplace, and organize outcomes by go-to-market goal.
Agent Builder is the creation surface for custom agents and automations. It combines workflows, triggers, CRM context, and natural-language instructions. Access to one entry point does not prove a particular integration, action, field, or workflow is available or approved.
Use the Agent Hub product guide for the complete product record and the Agent Builder implementation guide for workflow design.
Permissions and data review
Before enabling the beta:
- inventory current HubSpot users, roles, teams, business units, connected apps, and sensitive properties;
- identify who can build, activate, approve, monitor, edit, and disable a workflow;
- minimize accessible records and properties to the named job;
- review cross-border, retention, deletion, audit, consent, and customer-notice obligations;
- test whether the agent can infer or expose data across teams, pipelines, or business units;
- preserve a manual disable switch and ordinary HubSpot audit review.
Shared context can reduce fragmentation, but it can also widen exposure. A central management view does not substitute for least privilege at the data and action layer.
Beta production boundary
Public beta means the product is open for eligible testing, not that every behavior, integration, limit, or support promise is stable. Keep workflow definitions versioned, start with reversible internal work, and prepare for interface, quota, output, model, and terms changes.
Do not use beta status to bypass the organization’s procurement, security, privacy, accessibility, compliance, or change-management process. Keep consequential customer communication and authoritative CRM writes behind review until quality is measured.
Pricing and capacity
HubSpot’s announcement names eligible editions but does not provide a durable standalone price, included run volume, overage unit, or support commitment for every portal configuration. Verify these on the exact account and quote.
Measure cost per accepted outcome. Include failed and retried executions, integration fees, data cleanup, reviewer time, exception handling, and administration—not only license price.
Frequently asked questions
Who can access HubSpot Agent Hub and Agent Builder?
HubSpot announced public-beta access for Professional and Enterprise customers on July 23, 2026. Verify the exact portal, subscribed Hub, edition, seat, region, beta enrollment, permissions, pricing, and terms.
Does every Professional portal receive the same access?
Do not assume so. A plan label does not prove identical rollout, Hub entitlement, seat, region, beta state, integration, limit, or user permission. Check the live portal and contract.
Is public beta the same as production readiness?
No. Public beta supports eligible testing, but behavior, interfaces, limits, models, integrations, support, and terms can change. Start with reversible internal work and preserve security, privacy, review, rollback, and change management.
Bottom line
Professional or Enterprise is the published starting boundary. Real access depends on the exact portal, subscription, beta enrollment, seat, role, data, integration, region, price, and terms. Confirm those before promising Agent Hub or Agent Builder to a team.
Official source
Source check: August 2, 2026. Verify current access and commercial truth inside the live HubSpot account.