HubSpot integration

What moves in each direction

For HubSpot, reading is live. Records, activity and attachments are extracted from the connected portal into SAGARIS, and the record in SAGARIS is the one the pipeline gates and the agents act on.

We state it this plainly because the alternative is a customer discovering it after connecting a portal. If your evaluation depends on SAGARIS writing into HubSpot today, it will not, and the Salesforce integration is the one where write-back is live.

What the dry run computes

The payloads are real even though they are not sent, which is what makes a dry run worth inspecting. Four mutation shapes are produced against the HubSpot CRM v3 API.

Deal stage update

A patch against a deal, moving it to the stage the SAGARIS pipeline gate allowed.

BANT property update

A patch writing qualification properties onto the same deal.

Call log

A call object created with an association to the contact it belongs to.

Activity create

An email or a note object, associated to its contact.

What your HubSpot subscription decides

What SAGARIS can do inside HubSpot also depends on your own HubSpot subscription rather than on us. HubSpot's tier ladder runs Free, Starter, Professional and Enterprise, and the capability each unlocks is fixed by HubSpot, not by your SAGARIS plan.

Custom objects

Enterprise only.

Field write-back, in the direction HubSpot permits

Starter and above.

Workflow automation, calculated properties, webhook subscriptions and multiple pipelines

Professional and above.

A portal can be Enterprise and still not have granted the custom-object scope to a connected app, so the connection confirms the scope at runtime instead of inferring it from the tier. A tier is a claim about what you bought; a granted scope is a fact about what this app may do.

When both systems changed the same field

The conflict is recorded rather than silently resolved, and the decision is reviewable. This applies to what SAGARIS holds regardless of whether the outbound path is writing, because reads from the portal continue either way.