Once Google Calendar is connected to Fostr, it becomes a central link between your scheduling data and the operational workflows running in the platform. This page outlines which calendar details are accessed, how event information is synchronized, and the ways Fostr leverages meeting and availability data to enrich Actions, Records, and automated processes with real‑time context.

Sync Timing & Update Behavior

Fostr synchronizes Google Calendar data through a combination of scheduled refreshes and event‑triggered fetches.

• Update Flow:
  • Calendar events are refreshed at predefined intervals while also being requested on demand whenever a workflow requires the latest information. This ensures that both upcoming and recent changes (e.g., rescheduled times, updated attendees) remain aligned.
• Configurable Cadence:
  • Sync frequency can be adjusted per tenant. For example, organizations with rapidly changing schedules can opt for higher‑frequency updates, while others may prefer lighter polling for long‑term planning.
• Event‑Based & Passive Sync:
  • The integration uses both passive background checks and event‑based calls to ensure that Fostr is always using current calendar data while minimizing unnecessary API requests.
• Credential Monitoring:
  • Integration health is actively monitored. If access tokens expire or permissions shift, Admins are automatically alerted and prompted to re‑authenticate to avoid interruptions in sync continuity.

Data Scope & Ingestion Rules

By design, Fostr ingests only the scheduling data needed to provide operational context inside workflows.

• Included Data:
  • Event details such as title, time, duration, attendees, and organizer information are indexed for cross‑workflow use.
• Recurring & Shared Calendars:
  • Recurring series and shared calendars are supported as long as the authorized account has the appropriate viewing permissions.
• Private Details & Attachments:
  • Only fields essential for workflow context are ingested by default. Sensitive notes, attachments, or descriptions remain in Google Calendar unless explicitly enabled during setup.
• Historical & Archived Events:
  • Fostr focuses on active and upcoming events to minimize data clutter. Selective backfill can be enabled during onboarding to incorporate relevant historical data.

Data Handling & Security

Fostr ensures that all Google Calendar data respects boundaries defined in both Google and Fostr environments.

• Record Storage:
  • Calendar data is mapped into secure, role‑based Recordsets inside Fostr. While Google Calendar is always the source of truth, Fostr surfaces usable event data where it adds operational value.
• Read‑Only Mode:
  • The integration is read‑only by default. Event details can be referenced or linked to Actions, but any edits to scheduling (time, attendee lists, cancellations) must be made in Google Calendar directly.
• Role‑Based Visibility:
  • Fostr leverages its internal permission framework to control visibility. Only those with the appropriate Fostr roles (e.g., Admins, Operators) will see linked calendar data in Actions or Recordsets.
• API Constraints:
  • Google’s API rate limits apply. For most operational patterns, Fostr operates well within threshold limits. High‑volume tenants may use scoped queries or staged syncs to optimize throughput.