Setting up the Google Drive integration in Fostr involves authorizing your Google Workspace account, selecting the appropriate access scopes, and confirming permissions for Shared Drives or folders you want to bring into workflows. A short configuration process ensures files and metadata are synced correctly, with visibility aligned to both Google sharing rules and Fostr’s role-based access controls.

This section provides troubleshooting guidance to address common issues such as credential errors, missing file access, or sync timing delays, helping you maintain smooth and reliable integration.

File Visibility and Sync Failures

When Google Drive content does not appear in Fostr after integration, several configuration or permission-related issues are usually the cause:

• Invalid or incomplete credentials: OAuth tokens or Google API scopes may not have been provisioned correctly. During integration, the authorized Google account must grant consent for Drive scopes such as drive.readonly, drive.metadata.readonly, or broader drive.file access in order for files to be indexed.
• Unshared or unauthorized files and folders: Only files and folders that the integration account has explicit access to will appear in Fostr. Content marked private, stored in Trash, or restricted to another Workspace domain will not sync unless shared with the integration account. Shared Drive access must also be provisioned where relevant.
• Permission mismatches: If a file has its sharing permissions changed after connection (for example, the integration account is removed or downgraded to restricted access), sync operations will fail for that item. Files and folders must remain accessible throughout the lifecycle of the integration.
• Unsupported content or structure: Certain file types, such as trashed items, shortcuts pointing to out-of-scope content, or oversized binary assets, may not be ingested beyond metadata references.

Impact of Google Drive Configuration Changes

Structural changes within Google Drive or Google Workspace can affect integration performance and file visibility. Common scenarios include:

• Renaming, moving, or deleting Shared Drives or folders that were previously mapped into workflows
• Revoking or reducing OAuth scopes for the integration app through Google Workspace admin settings
• Moving files into a Workspace domain not accessible by the integration account
• Changing file visibility controls (for example, toggling to “private” or removing the integration account from a shared file or folder)

These modifications may block future sync operations or break references to files already surfaced inside Fostr. Reauthorization or updated sharing assignments are required if configurations are modified after setup.

Validating Integration Health

To test and confirm that the Google Drive integration is functioning correctly, the following process is recommended:

1. Add a new file to a Shared Drive or My Drive folder that the integration account is authorized to access.
2. Wait for the next sync cycle (typically within 30 minutes) or perform a manual refresh if available.
3. Navigate to a connected Record or Action in Fostr where the file link should appear.
4. Confirm that the file metadata has synced, including name, owner, last modified date, and folder location.
5. Review the integration activity logs (visible to administrators) to verify successful processing and confirm no authentication or rate-limit errors were reported.

If expected files are still not visible, check for expired OAuth credentials, revoked scopes, or incorrect file‑sharing settings in Google Drive. Restoring permissions or re‑authenticating the integration typically resolves these sync flow issues.