Activating the Google Workspace integration in Fostr is relatively simple, but managing app permissions, token access, and configuration details requires care, especially in enterprise environments. This section includes troubleshooting tips for maintaining a healthy connection.

Common Issues with Data Visibility

In some cases, Gmail messages, Drive files, or Calendar events may fail to appear within Fostr workflows. Typical causes include:

• Missing OAuth scopes or expired access tokens.
• Restricted file permissions in Google Drive (file not shared with the integration account).
• Incomplete user consent during Workspace connection setup.
• Filtering or labeling rules in Gmail preventing messages from being matched to the proper ingestion patterns.

Gmail Routing Failures

If Gmail messages are not routing correctly into workflows:

• Verify that the user owns or has access to the mailbox being monitored.
• Confirm that label names and filters applied in Gmail are configured consistently with Fostr’s ingestion logic.
• Ensure that the gmail.modify scope is enabled, particularly if label-based automations are being used. Without this scope, labeling operations may fail or not trigger ingestion.

Drive File Preview Limitations

In some workflows, Drive files may appear without a live preview. This is expected behavior:

• By default, Fostr only retrieves file metadata (title, owner, permissions, link) from Drive.
• Live previews or content views are not supported unless explicitly integrated into workflows (e.g., onboarding sequences, curriculum modules).
• Users can still manually open file links in Google Drive to access full content.