FastFollow watches your calendar for upcoming meetings and pulls the transcript from Google Drive as soon as Meet finishes recording — typically within 60 seconds of the session ending.
~15 minutes if you already have a Google Cloud project
In the Google Cloud Console, create a new project (or reuse an existing one). FastFollow needs the Calendar API and Drive API enabled.
Set up the OAuth consent screen with your organization details. For Google Workspace customers, use the "Internal" user type to avoid Google verification.
Under Credentials → Create Credentials → OAuth client ID, choose "Web application" and configure the authorized redirect URI.
In FastFollow, go to Integrations → Google Calendar → Connect. Sign in with the Google account whose calendar should be ingested.
FastFollow requests only what is necessary for read-only meeting ingestion
| Scope | Why FastFollow needs it |
|---|---|
| https://www.googleapis.com/auth/calendar.readonly | Read calendar events, attendees, and conference data |
| https://www.googleapis.com/auth/meetings.space.readonly | Read Google Meet space metadata for live meetings |
| https://www.googleapis.com/auth/drive.readonly | Fetch Meet transcript files (Meet stores transcripts in the host’s Drive) |
| openid email profile | Identify the authorizing user |
Push notifications by default, with polling as a fallback
FastFollow registers a Calendar Watch via the Google Calendar API. Google posts every event change to /api/webhooks/calendar within seconds.
If push notifications cannot be registered (network egress restrictions, allowlist requirements), FastFollow falls back to polling every 5 minutes.
Ingest every meeting across an entire Google Workspace org from a single connection
By default, every user connects their own Google account. For Workspace customers who want centralized ingestion across the org, FastFollow supports domain-wide delegation via a service account.
Domain-wide delegation grants FastFollow access to every user's calendar in your org. Only admins should configure this, and only after reviewing FastFollow's security posture and privacy policy.
The most common Google Calendar integration errors
access_deniedUser clicks Cancel or Google blocks the consent screen.
Fix: If the consent screen shows a "verification required" banner, your OAuth app is in External + Testing mode. Either move to Production (requires Google verification for sensitive scopes), or restrict the user type to Internal for Workspace orgs.
invalid_grantRefresh token returns an error during background sync.
Fix: The user revoked access from myaccount.google.com, the password changed, or the account was suspended. Have the user reconnect from FastFollow → Integrations → Google Calendar.
insufficientPermissionsCalendar events appear but transcripts never ingest.
Fix: Drive scope was denied. FastFollow needs drive.readonly to fetch Meet transcripts (Google stores them in the meeting organizer’s Drive). Reconnect and grant all scopes.
watch_renewal_failedPush notifications stop arriving after 7 days.
Fix: FastFollow renews subscriptions every 6 days via a cron job. If renewal fails for 3+ consecutive runs, the integration falls back to polling. Check the cron logs at /admin/health or contact support.
rate_limit_exceededInitial backfill triggers 429s.
Fix: Google enforces per-user quotas (1,000,000 queries/day default). FastFollow honors these with exponential backoff. For large historical backfills, contact support to schedule outside business hours.