SignalOS · Integrations
Manage connector readiness across email, meetings, CRM, data, and automation
This integrations surface gives SignalOS a dedicated operational control layer for connector strategy, readiness visibility, and future expansion without forcing integration planning into worker, sequence, or analytics screens.
Total integrations
8
Tracked connector surfaces
Connected
1
Live or already in use
Available
2
Candidate surfaces
Planned
5
Roadmap connectors
Critical priority
1
Highest operational sensitivity
Live dependency
Nylas
Live system dependency in the existing outbound execution layer.
Best next candidate
Webhook / Automation Layer
Define trusted inbound event types and event-handling boundaries before implementation.
Roadmap focus
Google Calendar
Meeting ingestion, booking visibility, and event normalization are not built yet.
Integration registry
This registry keeps connector planning, operational priority, and next milestone visible in one surface.
8 visible
Live
1
Candidate
2
Roadmap
5
Review
0
connectedemailcriticallive
Nylas
Execution infrastructure
Outbound email infrastructure currently used for mailbox connectivity and sending.
Purpose
Supports mailbox connection, sender resolution, and execution-aligned send operations.
Current state
Live system dependency in the existing outbound execution layer.
Next use
Continue as the canonical email connector for sending and mailbox operations.
Next milestone
Preserve stability while future event, reply, and mailbox-adjacent surfaces mature around it.
Blocked by
No current blocker. This connector is already in active production use.
Risk note
Execution-critical system. Changes around email routing or send behavior should remain tightly controlled.
plannedcalendarhighroadmap
Google Calendar
Meeting operations
Calendar integration for future meeting visibility, booking sync, and event ingestion.
Purpose
Would support meeting tracking, scheduling visibility, and future calendar-linked workflows.
Current state
Not yet connected to a live SignalOS meeting ingestion path.
Next use
Candidate for future meeting sync and booking outcome visibility.
Next milestone
Define event model and meeting ingestion rules before connector implementation.
Blocked by
Meeting ingestion, booking visibility, and event normalization are not built yet.
Risk note
Should not be connected until meeting data ownership and state transitions are clearly defined.
plannedcrmhighroadmap
HubSpot
CRM alignment
CRM connector for syncing contacts, companies, lifecycle context, and pipeline metadata.
Purpose
Would connect outbound activity with CRM-level deal and lifecycle visibility.
Current state
Not implemented in the current system.
Next use
Future prospect and opportunity enrichment path.
Next milestone
Clarify contact-company-opportunity mapping before exposing CRM sync behavior.
Blocked by
CRM object mapping, sync direction rules, and conflict handling are not defined yet.
Risk note
Unsafe to connect before ownership rules are clear for prospect, company, and activity records.
availableautomationhighcandidate
Webhook / Automation Layer
Platform orchestration
Reserved area for inbound events, external triggers, and cross-system workflow orchestration.
Purpose
Would support bounce events, reply signals, meeting outcomes, and external status changes.
Current state
Not formalized as a product layer yet.
Next use
Future event-driven architecture and cross-system automation support.
Next milestone
Define trusted inbound event types and event-handling boundaries before implementation.
Blocked by
Reply tracking, bounce handling, unsubscribe enforcement, and event normalization are not built yet.
Risk note
Automation should be added carefully so inbound events do not destabilize the execution layer.
availabledatamediumcandidate
Apollo / Data Source
Research and sourcing
Represents future enrichment or prospect data connectivity rather than current execution infrastructure.
Purpose
Would support higher-quality prospect data and enrichment inputs.
Current state
No direct integration in the current stable build.
Next use
Future enrichment and sourcing layer.
Next milestone
Define how imported data should map into research pipeline and prospect records.
Blocked by
Need a stable enrichment contract and import governance before enabling live sourcing.
Risk note
Should avoid polluting prospect records with unclear overwrite or deduplication behavior.
plannedcallingmediumroadmap
Calling Provider
Call operations
Reserved integration slot for future call workflows and voice activity tracking.
Purpose
Would support call logging, call outcomes, and future sequence-to-call orchestration.
Current state
Not implemented yet.
Next use
Future calling system under the broader outbound intelligence platform.
Next milestone
Define call object, source attribution, and outcome model before provider selection.
Blocked by
Call ingestion, provider choice, and outcome schema are not finalized.
Risk note
Calling integrations should follow a clear operational model instead of driving the model.
plannedcalendarmediumroadmap
Outlook Calendar
Meeting operations
Microsoft calendar integration for teams operating in Outlook ecosystems.
Purpose
Would extend meeting and event visibility to Microsoft-based scheduling environments.
Current state
No live integration layer yet in the product.
Next use
Future scheduling and meeting ingestion support for Microsoft users.
Next milestone
Add after the first calendar ingestion model is proven with one calendar ecosystem.
Blocked by
Depends on the same meeting ingestion and booking model required for Google Calendar.
Risk note
Should follow, not precede, the first stable calendar integration pattern.
plannedcrmmediumroadmap
Salesforce
CRM alignment
Enterprise CRM integration for account, contact, and opportunity alignment.
Purpose
Would allow SignalOS to align outreach and meetings with enterprise sales workflows.
Current state
Not yet added.
Next use
Future enterprise reporting and CRM synchronization path.
Next milestone
Sequence after the first CRM integration model is validated on a narrower connector.
Blocked by
Depends on stable CRM mapping rules and a proven sync architecture.
Risk note
Enterprise CRM surfaces introduce higher field complexity and heavier lifecycle coordination.
Operational summary
This summary turns the integrations shell into a clearer control surface without touching live backend execution.
Critical
1
Connectors with the highest operational sensitivity.
High
3
Strong candidates for structured planning after execution-safe review.
Candidate
2
Surfaces that are closer to structured implementation than pure roadmap items.
Roadmap
5
Future connectors that still depend on missing operational systems.
Category coverage
Keep platform expansion visible without mixing roadmap planning into stable execution interfaces.
Email
1
Sending and mailbox infrastructure
Calendar
2
Scheduling and meeting visibility
CRM
2
Pipeline and lifecycle alignment
Calling
1
Voice workflow expansion
Data
1
Enrichment and sourcing support
Automation
1
Webhooks and event orchestration
What this page now does better
This version stays UI-first and low-risk, but gives the integrations surface more operational value.
Clearer prioritization
Each connector now shows operational priority instead of status alone.
Better sequencing
Next milestone and blocker fields make implementation order easier to reason about.
Lower roadmap drift
This page keeps connector planning in one place without reopening worker or routing logic.
Safer expansion
Risk notes help prevent future integration work from destabilizing core execution layers.