CRM
HubSpot
Available
Connect your company's own HubSpot account through HubSpot sign-in (OAuth with PKCE). A reviewed read sync of contacts and companies into the CRM is in preview; deals are planned.
Available today through account connection from Connections. Step-by-step instructions are in the product guide.
Coverage by service or edition
Account connection from Connections. Each service needs its own permissions and acceptance checks.
Account connection
Available
Connect, check and disconnect a HubSpot account per company. Tokens are stored encrypted and refreshed automatically.
Contacts and companies read sync
Preview
Incremental read of contacts and companies into CRM contacts and organizations. Each new or changed record waits in a review queue with likely duplicates; nothing is written to HubSpot.
Deals sync
Planned
Deals and pipelines under evaluation.
Before you start
Have these ready before you start.
- A HubSpot user who can approve app access for the HubSpot account you want to connect.
- A company admin in os.construction to start the connection from Connections.
Confirm the scope
A HubSpot user who can approve app access for the HubSpot account you want to connect.
Agree the mapping
Object id → source key; dealname → opportunity; pipeline/dealstage → reviewed stage; association IDs → relationships.
Preview and reconcile
Keep source identity/revisions separate from locally owned permissions, project placement and workflow decisions. Unresolved associations or conflicting local edits require review.
Review before applying
An authorized reviewer must confirm destination scope, unresolved records and control totals. A successful extraction is not proof that data has been applied.
Check recovery and access
Pause on expired or revoked access. Restore authorization before resuming from the last complete checkpoint. An incomplete list or permission error is not proof of deletion; inspect uncertain outcomes before retrying.
Mapping and synchronization
- Record mapping
Object id → source key; dealname → opportunity; pipeline/dealstage → reviewed stage; association IDs → relationships.
- Sync boundary
- Pin a date-based API version; do not mix older v3 examples. Confirm object and association paging.
- Source ownership
- The provider remains authoritative for its source records. Local project placement, access and workflow decisions need explicit destination ownership. Match by scoped IDs, not names alone.
- Outbound policy
- No provider business writes are offered here. Sending, posting, inviting, deleting and permission changes require separately approved capabilities.
Conflicts and recovery
When records disagree
Keep source identity/revisions separate from locally owned permissions, project placement and workflow decisions. Unresolved associations or conflicting local edits require review.
When a run stops
Pause on expired or revoked access. Restore authorization before resuming from the last complete checkpoint. An incomplete list or permission error is not proof of deletion; inspect uncertain outcomes before retrying.
Limits to plan around
- Contacts and companies reach the CRM only after review. Nothing is written to HubSpot, and records deleted in HubSpot are not detected.
- Won deals do not automatically create projects. Custom properties and archive reconciliation need validation.
- Disconnecting removes the stored credentials in os.construction; uninstall the app in HubSpot to revoke access there too.
No provider connection is initiated from this page. See the product guide for how to run it.
Documentation and source dates
Provider documentation establishes upstream capabilities, not os.construction availability. Confirm the current edition and API contract before planning setup.
- HubSpot official documentationAccessed