CSV and structured imports
Bring a structured customer source into evidence-led account research without consuming mailbox or calendar identity capacity.
- Published plan scope
- Proof of Signal · Focus · Momentum · Command
Signal OS integration catalogue
Connect the commercial context. Keep each system in its proper role.
Signal OS is designed to sit between evidence sources and the systems where a PropTech team manages data, relationships and action. The public catalogue currently names CSV and structured imports, HubSpot and Apollo; connector readiness and exact behaviour must be confirmed for the workspace before rollout.
Catalogued connections
A clear boundary between source, qualification and action.
Connector inclusion and mailbox/calendar identity capacity are separate. Third-party subscriptions, provider usage and commercial terms are not included with Signal OS.
HubSpot
Use CRM context alongside CRE evidence and keep approved commercial outputs aligned with the existing system of record.
- Published plan scope
- Focus · Momentum · Command
Apollo
Use an existing Apollo subscription within supported enrichment workflows while keeping its licence, usage and terms separate.
- Published plan scope
- Momentum · Command
Before enabling a connector
Confirm the exact deployed behaviour.
The plan catalogue establishes inclusion, not every implementation detail. Procurement and rollout should use the enabled workspace behaviour as the source of truth.
- Authentication method and requested scopes
- Permitted objects, fields and data direction
- Sync trigger, frequency and failure handling
- Retention, deletion and audit behaviour
Published boundary
No connector claim should outrun the implementation.
Signal OS does not use this page to imply an unverified two-way sync, object list or automatic customer-facing action. Human approval remains required for individual outbound communication.
Review security and governance →