Product
SAGARIS HubSpot reads are live, write-back is a dry run
SAGARIS connects to HubSpot, and the two directions are not in the same state, so it is worth being exact about which one you are relying on. For HubSpot, reads are live and the write-back path runs as a dry run: it computes what it would write and does not write it. HubSpot write-back is switched off in production for every workspace, so there is nothing to enable for one portal.
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.
Note
For HubSpot the write-back path is a dry run: it computes the exact mutation it would send and does not send it. This is not a plan-level restriction or a setting on your portal. HubSpot write-back is switched off in production for every workspace, so there is nothing to enable for one portal, and switching it on is a rollout decision on our side.
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 same is true of Salesforce, where write-back is also switched off in production.
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
Field-conflict logging is Salesforce-only: on the HubSpot path a conflict is not recorded. Reads from the portal continue either way, whether or not the outbound path is writing.
What this connects to
Developers and integrations
- SAGARIS documentationGuides, concepts and API reference for the revenue engine.
- Salesforce integrationSalesforce reads are live; write-back is switched off in production.
- IntegrationsWhat SAGARIS connects to, and in which direction.
- The SAGARIS MCP serverYour CRM and Brain in your AI assistant, with scoped Social drafts and gated LinkedIn actions.
Building on it? Bring your use case.
Book a demo