Kylon vs HubSpot

HubSpot runs on workflows you build. Kylon runs on what you ask for.

Kylon is a workspace where agents sit with the team, read the thread and the tools you connected, and hand back the records, the dashboard and the email draft for one person to approve.

Choose HubSpot if

A record timeline and a workflow editor somebody configures.

Choose Kylon if

A room where you ask for the work and approve what comes back.

Get started

01 Which one is the right answer

Not every team should pick the same one.

HubSpot is the right answer when

Marketing and sales run one inbound motion together, and someone on the team owns the workflow editor, the sequences and the properties. That ownership is what makes the system work, and HubSpot is built for it.

Kylon is the right answer when

Nobody wants to own an editor. The work starts as a message, it needs the mailbox and the thread as much as the record, and the result has to come back for a person to approve in the same place.

02 Operating model

How each one works

Every statement about HubSpot below cites HubSpot's own product pages or knowledge base. Checked 2026-09-16.

Where the work happens
HubSpotWork is organised around CRM record views for contacts, companies, deals and tickets, with an object timeline of activities, meetings and tasks, and adjacent views for properties, workflows, sequences and meetings. HubSpot positions Breeze Assistant as available inside HubSpot and on its mobile app.Source: Breeze Assistant, HubSpot
KylonThe work happens in the room where the team already talks. The ask, what the agent read, and the records it produced are one thread instead of a record view plus a chat panel.
Who keeps the records current
HubSpotRecords are created from forms, integrations or by hand. HubSpot's data enrichment settings can automatically enrich newly created records and keep previously enriched records updated as new information becomes available, with administrators configuring mappings and overwrite behaviour.Source: Manage data enrichment settings, HubSpot Knowledge Base
KylonAn agent reads the mailbox, the calendar and the thread you granted it, then writes the contact, the company and the deal stage as a proposed change you can see before it lands.
How the AI gets context
HubSpotHubSpot's AI can be given access to CRM data such as contacts, companies, deals, tickets and notes, to conversation data including calls, emails and chats, and to public files in HubSpot. It separates account wide business context from knowledge vaults an administrator attaches to specific agents.Source: Manage AI context, HubSpot Knowledge Base
KylonAn agent reads the rooms it is a member of, the files and records attached to them, and the accounts connected to it. Context is membership plus grants, and the agent names what it read in its reply.
Approving what the AI does
HubSpotFor tools exposed through Breeze Assistant connectors an administrator sets access to Always allow, Ask permission or Never allow, and Ask permission prompts the user each time. The agent inbox marks runs Needs approval when they are waiting on tool approval and lets a user inspect the output and its sources.Source: Connect apps to Breeze Assistant, HubSpot Knowledge Base
KylonApproval is the default and it is one step, not a per tool setting. The records, the dashboard and the email draft arrive together in the thread behind a single approve control.
Reaching email and calendar
HubSpotA user connects an individual work email to send one to one messages from the CRM and log replies, which requires personal email access and provider authorisation through Gmail, Outlook, Exchange or IMAP. A user connects one Google, Office 365 or Exchange calendar for the meetings tool.Source: Connect an individual work email, HubSpot Knowledge Base
KylonThe mailbox and calendar are workspace connections the agent reads directly, and outbound email comes back as a draft card in the thread rather than a send.
What setting up automation takes
HubSpotAutomations are created under Automation then Workflows, starting from AI, a template or a blank workflow. In the editor a user configures enrollment triggers, re-enrollment and unenrollment, actions and execution settings, then reviews and turns the workflow on. AI can generate a first set of triggers and actions, and the workflow still opens in the editor for setup.Source: Create workflows, HubSpot Knowledge Base
KylonYou describe the outcome in the room. If it should repeat, the same request is saved as a scheduled or event driven run, and its output stays in the room.

What Kylon is for

Kylon is the layer where the work is asked for and approved. It reads the tools you already run, including HubSpot, and returns records, dashboards and drafts into the conversation that produced them. Running an inbound marketing engine with its own content, forms and nurture programmes is a different job, and Kylon is not that tool.

Questions people ask

Do we have to move off HubSpot?
No. Connect the HubSpot account to the room and the agent reads and writes through it, so the records stay where your team already works.
Is this another chat panel next to the CRM?
The difference is where the result lands. The agent answers in the room with the records it wrote and the draft it prepared, behind one approval, instead of returning a suggestion you then carry into the record.
Can it still run on a schedule?
Yes. Ask once, then keep it as a scheduled or event driven run. The output stays in the room where people can see it.

Keep reading

The workflow you never built is the one you needed.

Put an agent in the room where the work is discussed, connect the mailbox and the CRM, and approve what it hands back.

Get started