Productivity
Google Workspace
Planned
Planned: file Google Calendar events that name a project number as project correspondence, after review.
Planned. This connection is not available in os.construction yet. This page describes the intended scope; it is not a release date.
Coverage by service or edition
Calendar filing from Connections (planned). Each service needs its own permissions and acceptance checks.
Drive & shared drives
Planned
File IDs, revisions and scoped permissions.
Docs
Planned
Tab-aware documents; revision IDs are not permanent global versions.
Sheets
Planned
Explicit ranges and stable keys; formulas and formatted amounts need review.
Gmail
Planned
Mailbox-scoped messages; expired history requires re-enumeration.
Calendar
Planned
Planned: events whose title names a project number are offered for review and filed as project correspondence. Read only; incremental with Calendar sync tokens.
Slides, Directory, Contacts, Meet & Chat
Planned
Separate service contracts required; not included by Drive access.
Prepare for a scoped walkthrough
Use this checklist to agree the scope. These are preparation steps, not instructions for an available authorization or sync screen.
- Select each service, account/shared-drive scope and least-privilege grants.
- Confirm the destination company/project and the reviewer responsible for approving imported records.
Confirm the scope
Select each service, account/shared-drive scope and least-privilege grants.
Agree the mapping
Drive file.id → document; Gmail mailbox/message.id → correspondence; Calendar calendarId/event.id → event reference.
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
Drive file.id → document; Gmail mailbox/message.id → correspondence; Calendar calendarId/event.id → event reference.
- Sync boundary
- Drive tokens, Gmail history IDs and Calendar sync tokens are separate checkpoints. Sheets need stable row keys.
- 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
- No sending, inviting, sharing or provisioning. A Google login is not access to every Workspace service.
- Not available in os.construction yet. Provider documentation describes the upstream API, not an os.construction connection.
No provider connection is initiated from this page. For the reviewed accounting import workflow available today, see the accounting import guide.
Documentation and source dates
Provider documentation establishes upstream capabilities, not os.construction availability. Confirm the current edition and API contract before planning setup.