Connect the relationship record
Use the enabled CRM context to understand what the team already knows about the account.
Signal OS integration catalogue · HubSpot
Use HubSpot as the relationship record. Add the CRE “why now”.
The Signal OS catalogue includes HubSpot for paid public plans. The connection is intended to bring CRM context into evidence-led qualification and keep governed commercial outputs aligned with the team’s existing system of record.
Published catalogue position
HubSpot has a defined role in the Signal OS stack.
HubSpot remains the CRM. Signal OS researches and qualifies commercial real estate change before a person approves the next action.
- Included in the public catalogue for
- Focus · Momentum · Command
- Mailbox/calendar identity use
- This connector does not consume mailbox or calendar identity capacity.
- Third-party commercial terms
- HubSpot licensing, usage and provider terms remain separate from Signal OS.
A bounded workflow
Use the connection to support qualification—not to bypass it.
External data remains untrusted until it is validated, connected to an account and preserved with its source context.
Qualify the commercial change
Preserve source evidence, timing, contradictions and the account-level hypothesis in Signal OS.
Route the approved output
Use only the deployed and tested connector surface; keep the decision and approval history attributable.
What the catalogue supports
- HubSpot is listed as an included connector for the published paid plans
- The connector is separate from mailbox and calendar identity capacity
- CRM, mailbox and other third-party licences remain separately contracted
What this page does not claim
- An unverified two-way sync or universal object coverage
- That every HubSpot field or workflow is enabled in every workspace
- Automatic customer-facing communication without human approval
Rollout gate
Inspect scopes and behaviour before production use.
- Verify the enabled connection in the target workspace
- Approve the exact data path and permissions
- Test failure, retry and audit visibility