WorkTracker › Connection guides › Google Calendar + Gmail

Connect Google Calendar + Gmail to WorkTracker

Meetings become tracked time; sent mail becomes work items.

What you need

• A Google or Google Workspace account.
• The WorkTracker server must have a Google OAuth client configured (self-hosting: a “Web application” client with redirect URI {APP_BASE_URL}/api/connectors/google/callback).

Setup

1. Open Connections

   In WorkTracker open Connections and find the Google Calendar + Gmail card.

2. Connect and consent

   Click “Connect Google” and approve the read-only Calendar and Gmail scopes. Google asks for consent every time by design — that is what produces the offline token the background sync needs.

3. Sync

   Run a sync: meetings land in the time column, sent mail in the work items column. Mails sharing a subject collapse into one thread row.

What WorkTracker collects

• Calendar: meetings you organized or accepted, with organizer and attendees — counted as tracked time and deduplicated against Toggl.
• Gmail: sent mail as zero-duration work items (subject and From/To/Cc; bodies are read transiently for AI summaries, never stored).

Both scopes are read-only. Mail bodies are fetched transiently when the AI writes a summary — only the summary is stored. Meeting time already tracked in Toggl counts once. Credentials are stored encrypted (AES-256-GCM) and are never shown again or returned by the API.

Troubleshooting

Error 400: redirect_uri_mismatch

Server-side setup: the Google OAuth client must list {APP_BASE_URL}/api/connectors/google/callback (and /api/auth/google/callback for sign-in) as authorized redirect URIs, and it must be a “Web application” client — a Desktop client cannot host these redirects.

“Google returned no offline access”

Retry the connect flow and approve all screens — a refresh token is only issued on a full consent.