Fostr’s Google Calendar integration connects your scheduling and time-management workflows directly into the AI operating system. This page outlines how Fostr accesses calendar data, key considerations around credentials, and visibility settings so your team understands how events are ingested, who can see them, and how automated workflows maintain role‑appropriate context.

Credentials & Access

The Google Calendar integration requires internal credentials provisioned through Google Cloud. These credentials typically consist of a Client ID, Client Secret, and access tokens associated with the Google account or service account managing the target calendars.

• Scope of Credentials:
  • Credentials are applied at the tenant level, ensuring a single configuration provides consistent access for scheduling, event retrieval, and automation across the tenant’s instance.
• Storage:
  • All credentials are securely encrypted and stored within the associated Google Calendar Integration record in Fostr. Access is limited to Admins and approved internal stakeholders. Credentials are write‑protected across environments.
• Required Scopes:
  • Standard Google Calendar API scopes are required for reading event and availability data. For extended functionality such as creating or updating events, additional OAuth scopes may be required.
• Test Instance Availability:
  • A test instance is available to validate credentials, confirm API connectivity, and simulate calendar ingestion workflows before deploying in production environments.

Permissions & Visibility

Once integrated, calendar data is surfaced selectively within Fostr for use in context flows and automated workflows.

• Calendar event data is used to:
  • Retrieve and link event details to relevant Fostr Actions
  • Surface availability and schedule context within workflows
  • Trigger automations such as reminders, follow‑up tasks, or meeting preparation steps
• Visibility:
  • Event data is only accessible to authorized internal users based on their Fostr role permissions. Calendar information is dynamically linked to relevant workflows and is not exposed outside of assigned contexts.
• Respect for Native Settings:
  • Google Calendar’s native sharing permissions are fully respected. Only events that are accessible through the connected Google account or service account will be synchronized into Fostr.
• Configuration of Access:
  • Visibility is not managed at the integration level. Instead, Fostr role‑based permissions govern which users can view Recordsets and Actions connected to Google Calendar data.

Maintenance

Credential maintenance is minimal. If underlying tokens expire or account permissions change, updated credentials must be re‑issued and stored in the Integration record to maintain workflow continuity.

Fostr Admins will be notified if connectivity is disrupted to ensure updates are applied promptly.