Skip to content
Book a build
← All comparisons

Jetstack AI vs HubSpot Breeze

Breeze drafts a workflow.
Projects ships the whole build.

Breeze Assistant turns a prompt into one workflow’s triggers and actions. Your client needs the properties, pipelines, lists, forms and emails behind that workflow too, built in the right order. Jetstack Projects turns the brief into a plan you approve, builds every supported asset in dependency order, creates workflows switched off, asks for a separate deployment approval and reads the result back from HubSpot.

The Jetstack advantage

The brief should become a portal. Not a canvas you finish by hand.

Projects plans and ships the build around the workflow, not just the workflow.

  1. One plan for the whole brief.

    Jetty, the Projects assistant, turns your brief into a plan covering properties, pipelines, workflows, lists, forms, marketing emails and the other supported types. Approving it starts generation.78

  2. Dependencies first. Workflows off.

    A Project builds in dependency order, properties before the workflows that use them, and every workflow is created switched off.89

  3. Two approvals and a receipt.

    You approve deployment separately from the plan, then get a receipt of what was created, checked by reading it back from HubSpot.79

Book a live build →

What Jetstack covers

Real HubSpot assets. Not just instructions.

Plan → generate → approve → deploy → verify

Projects turns an implementation brief into a reviewable plan and supported asset configurations. The build spans CRM structure, automation, sales enablement, reporting and the workspace around them.

A delivery lifecycle around every build.

Review the plan and approve generation. Inspect the output, then separately approve deployment. Projects orders dependencies, records deployed IDs and receipts, and reads supported assets back from HubSpot. API-backed types deploy directly; extension-backed types require the Chrome extension and a connected portal.

See the deployment lifecycle

Generation coverage is different from library import/copy coverage. CMS content such as pages and blog posts is not generated by Projects. Unsupported work becomes an explicit manual step. HubSpot subscriptions, permissions and type-specific limits apply. Read-back confirms saved configuration, not runtime behavior; functional testing stays with your team.

Read the fine print

Agent Hub’s workflow builder has rules.

HubSpot’s own knowledge base sets the limits on what Breeze builds.

  • One workflow. One trigger.

    Building workflows with Breeze Assistant needs a Professional or Enterprise subscription and Super Admin or Workflows permissions. Each Agent Hub workflow takes a single trigger, and records can’t be enrolled manually.13

  • Only certain actions.

    Only certain actions are available in the Agent Hub builder, they depend on your subscriptions, and Create record supports a fixed list of object types.34

  • Placeholders, not finished steps.

    Actions that can’t be fully set up may be saved as placeholder actions, and every action has to connect to the main sequence before the workflow can be turned on.3

  • Projects ships the whole build.

    A plan from the brief, dependency-ordered generation, workflows created switched off, a separate deployment approval and a read-back receipt.789

Built to go further

A workflow assistant isn’t an implementation system.

Breeze drafts the workflow. Planning the portal around it is still your job.

The Jetstack advantage

The whole build, planned and verified.

  • Start from the client brief and review one plan for every supported asset it needs.78
  • Build properties, pipelines and lists before the workflows that use them, with every workflow created switched off.89
  • Approve deployment separately and keep the read-back receipt. Then reuse the setup across portals, with rollback.91112
Explore Projects →

Where it falls short

One canvas at a time.

  • Breeze Assistant drafts one workflow’s triggers and actions from a prompt, in the Workflows tool or in Agent Hub, and its suggestions go straight onto the canvas.114
  • Its create list covers records, quotes, products, content drafts, agents and workflows. Properties, pipelines, lists and forms aren’t on it.2
  • Agent Hub workflows take one trigger each, can’t enroll records manually and support only certain actions.34
  • Agent Hub, formerly Breeze Agents, runs agents for AEO, data, prospecting, deal progression and support. Building the portal isn’t one of their jobs.56

Side by side

See what Jetstack brings
to the build.

Individual features are only part of the story. Jetstack puts the implementation workflow around the client’s HubSpot portal.

Jetstack Projects compared with HubSpot Breeze. Product-documentation references are linked in each row.
The delivery jobJetstack ProjectsHubSpot Breeze
Where the build startsThe client brief, turned into a reviewable plan for the whole implementation.7A prompt for one workflow, in the Workflows tool or Agent Hub.114
What gets builtProperties, custom objects, pipelines, lists, workflows, forms, marketing emails, reports, sequences and more.8A workflow’s triggers and actions. Properties, pipelines, lists and forms aren’t in Breeze Assistant’s create list.12
DependenciesBuilt in dependency order: properties before the workflows that use them.89No dependency handling documented.13
Going liveWorkflows created switched off, deployed after a separate approval.89Suggestions land on the canvas right away. No separate deployment approval documented.1
Proof it landedA receipt of what was created, checked by reading it back from HubSpot.9No receipt or read-back step documented.13
Builder limitsEvery type on the supported capability list, built with the assets it depends on.8In Agent Hub: one trigger per workflow, no manual enrollment and only certain actions.34
Beyond the buildPortal Audit diagnoses the portal. Portal reuse deploys the setup to other portals, with rollback.101112No portal audit or cross-portal reuse in Agent Hub’s line-up.5

Explore Projects, read the implementation guide, or see pricing.

Your team stays in control

What comes with Projects

A purpose-built workflow for HubSpot implementation.

Coverage, access and deployment requirements
  • Projects is in limited release and requires organization access. Some asset types deploy through the Chrome extension.813
  • Generation and deployment follow the supported capability list. Projects doesn’t build CMS pages, themes or custom-code actions, and doesn’t import data, manage users or set up integrations.8
  • A Project changes only assets it built. For a workflow built elsewhere, it builds a corrected replacement, created switched off, and you retire the old one in HubSpot.9
  • Receipts and read-back evidence document every result, ready for your team’s functional testing.9
How the projects workflow works →

Questions, answered

Before you make the switch.

Can HubSpot Breeze build workflows?

Breeze Assistant can draft a workflow’s triggers and actions from a prompt, in the Workflows tool or in Agent Hub, on Professional or Enterprise plans. Its documented create list doesn’t include the properties, pipelines, lists or forms that workflow depends on. To build the whole setup, we recommend Jetstack Projects: one plan from your brief, dependency-ordered generation, workflows created switched off and a read-back receipt.

Is Breeze Assistant enough for a HubSpot implementation?

No. An implementation is the whole set of assets, built in the right order, approved and checked. Breeze drafts a workflow from a prompt. Jetstack Projects plans every supported asset from the brief, asks for a separate deployment approval and reads the result back from HubSpot.

Breeze comes with HubSpot. Why pay for Jetstack?

Because a prompt in the builder isn’t a finished build. With Breeze, your team still plans the portal, builds the prerequisites, sequences the work and checks it landed. Jetstack ships that lifecycle, plus Portal Audit to find what needs work and Portal reuse to deploy the setup to other portals.

Can Projects fix a workflow Breeze already built?

A Project changes only assets it built. For a workflow built elsewhere, Projects builds a corrected replacement, created switched off, and you retire the old one in HubSpot.

Can I keep using Breeze with Jetstack?

Yes. Projects builds in the same HubSpot portal your team already works in. Use Breeze for day-to-day questions and Jetstack for the build.

Backed by product documentation

The evidence
behind our case.

Written by Jetstack AI from each vendor’s public documentation, checked on the dates shown.

  1. 01
    Build workflows using Breeze Assistant in Agent Hub

    HubSpot Knowledge Base · Checked 29 Oct 2026

    Updated 16 Sep 2026. Professional or Enterprise, Super Admin or Workflows permissions; prompt from the builder and suggestions appear on the canvas.

  2. 02
    Use Breeze Assistant

    HubSpot Knowledge Base · Checked 29 Oct 2026

    Updated 2 Oct 2026. The Create or Generate list: records, notes, agents, content, quotes, products, sales email drafts and workflows.

  3. 03
    Create workflows in Agent Hub

    HubSpot Knowledge Base · Checked 29 Oct 2026

    Updated 16 Oct 2026. One trigger per workflow, no manual enrollment, only certain actions and placeholder actions.

  4. 04
    Choose your workflow actions in Agent Hub

    HubSpot Knowledge Base · Checked 29 Oct 2026

    Updated 16 Sep 2026. Subscription-dependent actions and the object types Create record supports.

  5. 05
    Understand Agent Hub

    HubSpot Knowledge Base · Checked 29 Oct 2026

    Updated 1 Oct 2026. Pre-built agents: AEO, Data, Prospecting, Deal progression and Customer agent.

  6. 06
    Breeze Assistant

    HubSpot · Checked 29 Oct 2026

    Product page. Its FAQ describes Agent Hub as formerly called Breeze Agents.

  7. 07
    Projects: the implementation lifecycle

    Jetstack AI documentation · Checked 27 Oct 2026

    Portal-scoped plans, generation and deployment approval, run evidence and verification.

  8. 08
    What Projects can build

    Jetstack AI documentation · Checked 27 Oct 2026

    The HubSpot asset types Projects generates and deploys.

  9. 09
    Projects deployment

    Jetstack AI documentation · Checked 27 Oct 2026

    Dependency order, deployment controls, run receipts and read-back verification.

  10. 10
    Portal Audit: scope, scoring and reports

    Jetstack AI documentation · Checked 27 Oct 2026

    Template-defined coverage across General, Sales, Marketing, Service, Automation and Reporting, with branded reports.

  11. 11
    Implementations lifecycle

    Jetstack AI documentation · Checked 29 Oct 2026

    Imported asset library, modules, dependency ordering and deployment to one destination portal or several.

  12. 12
    Rolling back a deployment

    Jetstack AI documentation · Checked 29 Oct 2026

    Preview, then delete the assets a deployment created; assets other deployments or Projects use, or that changed since, are kept.

  13. 13
    Getting access to Projects

    Jetstack AI documentation · Checked 29 Oct 2026

    Projects is in limited release and turned on for each organization individually.

  14. 14
    Create workflows

    HubSpot Knowledge Base · Checked 29 Oct 2026

    Updated 16 Oct 2026. Create workflow With AI: Breeze Assistant generates a workflow, including enrollment triggers and actions, from a prompt.

Choose Jetstack

Put the client brief in Projects.

Give your next HubSpot brief a platform built for delivery. See the Jetstack workflow in action.

Book a live build