CRM

The tool list is reviewed. The built-in use case is not here yet

HubSpot has a reviewed tool list: fourteen reads, five writes that each need an approval step, everything else refused. No built-in use case yet.

Not open yetThe HubSpot integration is not yet available to external organizations. This guide describes the intended experience; availability will be updated when access is ready.

Join the waitlist See the HubSpot example

HubSpot with Aestus

Keep the tool. Change what the team can see.

This guide is here so a use-case page can name HubSpot honestly, and honesty means starting with what is missing. There is no Aestus HubSpot workflow to switch on. What there is, today, is a connection and a pinned list of the HubSpot operations a step may use, with the writes marked. Fourteen operations read: deals, contacts, companies, pipeline stages, owners and support tickets. Five change a record, and each one needs an approval step upstream: updating a contact, a company, a deal or a ticket, and linking two records that already exist. Everything else HubSpot offers is refused, which includes creating a record, deleting one and merging two.

The advice worth giving in the meantime is about shape. Reporting on a pipeline wants nothing but reading, and a step that only reads needs no approval, so the whole thing runs on a schedule without interrupting anybody. The moment a graph edits a deal it inherits the approval gate, which is correct and also slower; mixing the two into one step means paying that cost for the reporting as well.

Where a number is involved, let the workflow count rather than the model. Days since last contact is arithmetic. A report whose figures were computed and cited can be checked against the deals underneath it; one whose figures were produced by a language model cannot.

Good first workflows

Watch the pipeline
Report the deals with no activity for a set number of days, each linked to its record.
Hand a won deal over
Turn a closed-won deal into the onboarding work it implies, leaving the CRM untouched.
Log a call from chat
Draft the CRM update from what was said and hold the write for the person who said it.

A complete HubSpot example, from trigger to proof.

The example names the people, task event, tool boundary, returned evidence, and acceptance state. The run row below it is a fixed product example, not customer data.

Example — fictional team and data. Not a live run or customer result.

Inside the connected tool

What the HubSpot connection gives you today

An org-owned account a workflow you author can read through. There is no Aestus HubSpot use case to switch on yet.

meridian · connectedConnection only

Runs without an approval

Read deals, companies and contacts

Held for a named person

Change a deal stage or a property

Not built yet

No Aestus HubSpot workflow and no pinned operation list yet.

Example — fictional team and data. Not a live run or customer result.

Concrete workflow example

Ask which deals went quiet, and get an answer you can check

This is what the connection makes possible. Aestus ships no built-in HubSpot workflow yet, so today the connection is the part that exists.

TriggerA workflow you build reaches HubSpot through the connected account

1
Organization admin
Connects HubSpot in Settings, Integrations
The connection is org-owned and appears in the same catalog as every other connected account.
connected · org-scoped
2
Aestus agent node
Reads deals, companies and contacts
A read-only node needs no approval step, which is the point of keeping it read-only.
read-only · no gate
3
Aestus workflow
Counts the quiet deals in code, not in the model
Days since last activity is arithmetic, so it is computed and cited rather than estimated.
EXAMPLE-HS-01 · counted
4
Aestus
Holds any write behind a named decision
Changing a deal stage or a property is a write, and a write is a person's call.
write · approval required

Example — fictional team and data. Not a live run or customer result.

Illustrative product example — not a production run

Read the stalled deal list

Example run		Runtime	Outcome
EXAMPLE-HS-01	Aestus workflow	aestus	Completed	$0.0209	27.3s

Tokens in / out: 9,100 / 700
Failure code: —
Agent: —

Illustrative Aestus workflow; actual costs and results vary

Example run cost

$0.0209 in the illustrative product example

A fixed illustration drawn from comparable Aestus workflow runs, not a measurement of a HubSpot workflow that has run, because none ships yet. It stands for one reporting run of 9,100 input tokens.

Set it up in four steps.

Follow the real HubSpot connection path. Provider steps link to the provider documentation. Aestus steps name the contract they follow.

01
Connect the HubSpot account
An organization admin connects it in Settings, Integrations. The account is owned by the organization and is revocable in the same screen.
Read the provider docs
02
Check the access HubSpot grants
HubSpot shows the scopes being granted during authorization. Grant reading before you grant anything that edits a record.
Read the provider docs
03
Allow the toolkit for workflows
A connected account and a workflow-reachable toolkit are two separate permissions. An organization policy decides the second one.
Aestus product guide
04
Build the workflow that uses it
There is no built-in HubSpot use case to switch on. Today you author the graph yourself and seed it like any other.
Aestus product guide

The boundary stays visible while the work moves.

See what HubSpot can do, where a person still decides, and what Aestus records for every governed run.

Where control lives

Keep the node read-only where you can

A step that only reads deals and contacts runs without an approval. That is the reason to keep reporting separate from editing.

Editing a record is a held action

Moving a deal stage or changing a property is a write. It waits for a named person and is recorded with their decision.

Counting is done by code

Days since last activity and deal totals are computed rather than estimated, so a number in a report can be checked against the records behind it.

What Aestus records

The records the answer used

A pipeline report names the deals it counted, so a figure that looks wrong can be opened rather than debated.

Who changed the CRM

Where a write is allowed, the approver, the record and the previous value stay on the run that made the change.

Run economics

Tokens, latency, cost and failure code stay with the run, the same as every other workflow in the system.

Questions teams ask

Can we use this today?

You can connect HubSpot and author a graph against it, and that graph is held to the reviewed tool list. What does not exist yet is an Aestus HubSpot use case you can switch on.

What is a reviewed tool list, and why does it matter?

Aestus pins which HubSpot operations a step may use and which of those change a record. Fourteen reads are allowed; five writes are allowed and each needs an approval step; every other HubSpot tool is refused before the model sees it, creating and deleting records included.

Will connecting it change our CRM?

Connecting grants access; it does not run anything. Nothing in HubSpot changes until a workflow you built asks it to, and a write in that workflow is a held decision.

See all integrations See the security controls

Start with one HubSpot run.

Bring one real run. Map its actors, boundary, evidence, cost, and acceptance step.

Talk to us

The tool list is reviewed. The built-in use case is not here yet

HubSpot has a reviewed tool list: fourteen reads, five writes that each need an approval step, everything else refused. No built-in use case yet.

Not open yetThe HubSpot integration is not yet available to external organizations. This guide describes the intended experience; availability will be updated when access is ready.

Example — fictional team and data. Not a live run or customer result.

Concrete workflow example

Ask which deals went quiet, and get an answer you can check

This is what the connection makes possible. Aestus ships no built-in HubSpot workflow yet, so today the connection is the part that exists.

TriggerA workflow you build reaches HubSpot through the connected account

1
Organization admin
Connects HubSpot in Settings, Integrations
The connection is org-owned and appears in the same catalog as every other connected account.
connected · org-scoped
2
Aestus agent node
Reads deals, companies and contacts
A read-only node needs no approval step, which is the point of keeping it read-only.
read-only · no gate
3
Aestus workflow
Counts the quiet deals in code, not in the model
Days since last activity is arithmetic, so it is computed and cited rather than estimated.
EXAMPLE-HS-01 · counted
4
Aestus
Holds any write behind a named decision
Changing a deal stage or a property is a write, and a write is a person's call.
write · approval required

Example run

Runtime

Outcome

EXAMPLE-HS-01

Aestus workflow

aestus

Completed

$0.0209

27.3s

Questions teams ask

Can we use this today?

You can connect HubSpot and author a graph against it, and that graph is held to the reviewed tool list. What does not exist yet is an Aestus HubSpot use case you can switch on.

What is a reviewed tool list, and why does it matter?

Will connecting it change our CRM?

Connecting grants access; it does not run anything. Nothing in HubSpot changes until a workflow you built asks it to, and a write in that workflow is a held decision.

The tool list is reviewed. The built-in use case is not here yet