Google Calendar support

Last updated date:

Connect, reconnect, and troubleshoot Google Calendar without sharing credentials or customer content through support channels.

1. Before you start

  • Choose the Google user and Seedling connection scope deliberately, or use the verified Google Workspace parent for organization-wide coverage.
  • For a dedicated connection, configure a Google OAuth web client and request offline access with the exact Calendar scopes in this guide.
  • Confirm the authorized user can natively open the calendars and events Seedling should synchronize.
  • Do not send Google Calendar credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Google Calendar authorizationGoogle's Calendar API authentication and scope guidance.

2. Connect Google Calendar

  1. In Seedling, open Connections and choose Google Calendar.
  2. Choose personal or workspace scope; personal Calendar data remains actor-owned.
  3. Enter the access and refresh tokens returned by the Google authorization-code flow.
  4. Connect and verify the Google user before allowing the first calendar synchronization to complete.
  5. Confirm the restricted workspace/no-human access policy before relying on member-facing event reads.

3. Authorization and connection problems

Calendar scope rejected
Repeat consent with the exact Calendar read scopes. Do not add a write scope to work around a missing calendar or event.
Calendar or event forbidden
Confirm the delegated user can open it natively and that shared-calendar access, event visibility, and tenant policy still permit the read.
Workspace member cannot read events
Review the connection's restricted default. Seedling does not turn Calendar ACL metadata, workspace membership, administration, or stewardship into an event-content bypass.

4. Missing or delayed data

  1. Confirm the calendar remains in the authorized user's calendar list and the event is visible to that user.
  2. Check recurrence, cancellation, sync-token reset, time range, and provider retry warnings.
  3. Confirm the personal owner policy or workspace restricted default permits the requesting member's read.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Run a fresh Google OAuth flow for the same user and Calendar read scopes with offline access.
  2. Replace both tokens on the exact connection and confirm the same Google identity and connection scope.
  3. Revoke the previous Google authorization after the replacement synchronizes successfully.