Skip to content
AAA.win

AI tool

Agent Hub

HubSpot's current workspace for discovering, building, running, and managing prebuilt and custom agents and agentic workflows with approved CRM context.

Editorially reviewedVerified 2026-08-112 official or primary sources

What it is

Agent Hub is HubSpot's current name for the agent platform previously called Breeze Agents. Official documentation describes a central place to discover, configure, run, and manage prebuilt agents, custom agents, and agentic workflows using HubSpot context.

Keep Agent Hub distinct from the separate Breeze Assistant product. Test access to CRM objects and properties, knowledge grounding, action scope, workflow triggers, approvals, handoff, audit logs, prompt injection, data retention, and recovery from incorrect updates.

Worth evaluating for

  • HubSpot customers adding controlled agents to CRM-centered work
  • Marketing, sales, or service workflows with explicit object permissions
  • Teams comparing prebuilt agents with custom agentic workflows

What to measure

  • CRM grounding, object and property permissions, and action accuracy
  • Trigger, approval, handoff, audit, error-recovery, and administrator controls
  • Clear separation between Agent Hub, Breeze Assistant, and other HubSpot AI features

Decision cautions

  • Older Breeze Agents materials may not match the current Agent Hub product.
  • Breeze Assistant remains a separate product and should not be conflated with Agent Hub.
  • CRM writes and customer communications require sandbox testing and human gates.

Sources checked

Open the original pages before relying on a time-sensitive product decision.

  1. HubSpot Agent HubHubSpot
  2. Understand Agent HubHubSpot
Version · v4.3.4-indexnow-root-proof

Latest releases

IndexNow root-proof request compatibility

After v4.3.3, the exact root-level {key}.txt proof returned HTTP 200, but a full request carrying keyLocation still returned HTTP 403; a minimal homepage request with the same production key and no keyLocation returned HTTP 202. This release omits that field, while the automatic full run and idempotent rerun remain deployment checks.

IndexNow key-proof compatibility

Changed IndexNow verification to the official root-level {key}.txt convention after the first production notification returned HTTP 403; revalidation remains pending, while the website, sitemaps, and Bing sitemap processing are unaffected.

Bing sitemap discovery and IndexNow change notifications

Prepared canonical sitemap discovery for Bing and added automatic IndexNow change notifications while keeping segmented sitemaps authoritative and making no claim that a notified URL has been crawled or indexed.

View all releases