Context integrations
Mail, calendars, files, notes, and knowledge sources enter Rodon with provenance and synchronization state.
Documentation / Integrations
Connect services without surrendering the product model.
An integration should translate an external service into Rodon’s shared concepts. It should not force every window to understand the provider’s raw protocol.
Capability integrations
Models, MCP servers, transcription engines, and execution providers add bounded tools.
Notification integrations
Approved reminders and operation results can be delivered through configured channels.
Identity
Credentials remain server-side and are scoped to a user, tenant, or administrator-owned integration.
Synchronization
Every connector reports source, last sync, errors, degraded state, and conflict behavior.
Conversion
External content can become notes, documents, tasks, events, attachments, or source references.
Revocation
Disconnecting a provider stops future access without making retained user-owned objects ambiguous.