Which integrations are currently shipped in OSTRATA?

Google Drive, Google Calendar, Gmail, and Telegram. Members connect Claude or Cursor via Personal space → MCP. Programmatic server access uses the REST API with scoped keys—see the API feature page and /docs/api.

Why is Drive workspace-level while Calendar and Gmail are personal?

Drive usually represents shared team documents, so admins connect it once at workspace scope. Calendar and Gmail are member-specific channels, so each user connects their own account. This split keeps access ownership aligned with how those services are actually used.

How does Telegram linking work for a team?

Admins first enable the workspace Telegram bot in Setup. After that, each member links their personal Telegram account. This enables individual participation and accountability while supporting mobile access and notifications tied to workspace workflows.

Can API keys be restricted by role-like access?

Yes—on the REST API feature page. Keys inherit one permission profile each, so external systems stay within defined object and field boundaries.

Google and Telegram

Connect Google Drive at workspace level. Members link Calendar, Gmail, and Telegram for personal workflow context—without bolting on a separate integration layer.

Google surfaces

Drive, Calendar, Gmail, per-member connect

2min

Personal connect

Calendar under Personal space

Mobile ops

Telegram bot + member links

Connect where work already happens

Google Drive, Calendar, Gmail, and Telegram beside your CRM.

Integrations stay focused on tools teams use every week. Admins connect shared services; members authorize personal channels for their own calendar and inbox.

French Registry enrichment and Google Drive indexing extend workspace context—official company data and searchable Drive content alongside CRM records.

Need programmatic access? See the REST API feature for scoped keys and /api/v1 endpoints—same permission model, no Setup bypass.

Google split by scope
Drive connects at workspace level, while Calendar and Gmail are linked per member account.
Telegram for mobile operations
Enable workspace bot access, then members link accounts for notifications and conversational workflows.

Workspace

Practical integration set for current workflows

Use focused integrations teams rely on every week in production.

Connect Drive, Calendar, Gmail, and Telegram
Cover docs, schedules, inbox, and mobile
Avoid fragile custom glue for core workflows

Personal

Google model: shared Drive, personal Calendar and Gmail

Connect shared Drive at workspace scope and personal Calendar or Gmail per member.

Admin sets shared document access once
Members authorize personal communication channels individually
Keep credential ownership aligned with real usage

Telegram connection for mobile and notifications

Enable Telegram for mobile notifications and on-the-go workflow participation.

Admins activate bot at workspace level
Members link personal Telegram accounts
Preserve accountability with individual identities

Context

Governance and ownership by integration type

Split integration ownership between admins and members.

Admins own workspace Drive and Telegram bot setup
Members own Calendar, Gmail, and Telegram links
Scale adoption with clear operational accountability

Registry & Drive

French Registry and Google Drive indexing

EU B2B teams enrich companies from SIREN; Drive files become searchable context for Pilot.

Enable French Registry in Setup → Integrations for INSEE and BODACC fields
Enrich companies from Operations, Standard views, or approve pending registry diffs
Index connected Drive folders so Pilot can reference shared documents

Questions

Short answers before you request access.

Which integrations are currently shipped in OSTRATA?: Google Drive, Google Calendar, Gmail, and Telegram. Members connect Claude or Cursor via Personal space → MCP. Programmatic server access uses the REST API with scoped keys—see the API feature page and /docs/api.
Why is Drive workspace-level while Calendar and Gmail are personal?: Drive usually represents shared team documents, so admins connect it once at workspace scope. Calendar and Gmail are member-specific channels, so each user connects their own account. This split keeps access ownership aligned with how those services are actually used.
How does Telegram linking work for a team?: Admins first enable the workspace Telegram bot in Setup. After that, each member links their personal Telegram account. This enables individual participation and accountability while supporting mobile access and notifications tied to workspace workflows.
Can API keys be restricted by role-like access?: Yes—on the REST API feature page. Keys inherit one permission profile each, so external systems stay within defined object and field boundaries.