Once connected, the Google Drive integration enables Fostr to reference and sync file metadata, shared folders, and collaborative documents into platform workflows. By linking Drive content to Records and Actions, teams can keep project artifacts and source materials aligned with execution. This documentation explains what types of Drive data are brought into Fostr, how that data is represented inside the platform, and which file attributes or sharing configurations are included or excluded during sync.

Sync Frequency, Data Refresh, and Timing

The Google Drive integration with Fostr synchronizes file and folder information into the platform on a scheduled polling basis. Once connected, Drive metadata and content become available inside workflows, supporting collaboration and operational continuity.

Drive sync operations occur in the following ways:

• On a scheduled polling interval (typically every 30 minutes by default)
• In response to workflow-driven events, such as a user attaching a file to a Record or Action
• On-demand when administrators manually trigger a refresh for testing, troubleshooting, or revalidation

Sync cadence is standardized across tenants for performance consistency, though on-demand actions provide flexibility when verifying new integrations or linking large volumes of data during onboarding. Fostr also spaces requests to respect Google’s API usage policies and avoid exceeding organizational rate limits.

Automatic vs. Manual Sync Behavior

After initial setup, Google Drive sync runs passively in the background with no daily input required from end users. Metadata updates and new file linkages flow automatically into connected workflows.

Administrators or integration managers can manually initiate sync jobs when needed, such as during initial backfills, when troubleshooting credential issues, or when confirming permissions on newly linked Shared Drives. Sync runs are tracked internally, with errors flagged if tokens expire, access is revoked, or file paths are restructured in Drive.

Data Coverage and Historical Access

The integration processes and surfaces file and folder data accessible through the connected Google account or service account. This includes:

• Metadata from both My Drive and Shared Drives
• Core file details such as title, type, owner, last modified date, and permissions metadata
• Folder structure and hierarchy to preserve organizational context

Initial ingestion captures existing accessible files, making them referenceable inside workflows at the time of setup. Newly created or updated files are recorded in subsequent scheduled sync cycles.

By default, deleted, trashed, or restricted files are excluded. Large binary assets (such as videos or archives) are not ingested beyond title and metadata fields unless explicitly required.

Data Granularity and Metadata Captured