Connect Google Calendar

Nothing to install and nothing to register. Two things worth knowing before you press Connect, because both change what you should expect:

• This reads your primary calendar. That is the calendar Google shows under your own name. Secondary calendars, and calendars other people have shared with you, are not read on this path. If the meetings you care about live on one of those, use Apple Calendar (which sees every calendar in the macOS Calendar app, Google accounts included) or a calendar link.
• A managed Google Workspace account may need administrator consent. Some organizations restrict which applications their users can approve. If yours does, the sign-in will say so, and a calendar link gets you the same result without anything for IT to approve.

1. Open Earkeep and press Settings, at the bottom of the left rail.
2. Go to Calendar.
3. On the Google Calendar row, press Connect. Your browser opens at Google's own sign-in page.
4. Sign in and approve the request. Earkeep asks for one permission, to see your calendars, and it cannot ask for more later without asking you again.
5. Google sends you back to a page that says you can close the tab. Close it and return to Earkeep. The row now reads Connected, followed by the account's address so you can tell two accounts apart.
6. Turn on Create spans from events if you want each event to become a meeting on its own.

While the browser is doing the sign-in, the row shows Connecting… and a Cancel button. That button is there because the browser tab is invisible to Earkeep: if you close the tab or change your mind, Cancel is how you tell the app to stop waiting.

Read-only, and only calendars. The single permission Earkeep requests is read access to your calendars. It cannot create, move or delete an event, and it cannot reach your mail, your files or your contacts, because it never asked to.

The token lives in your system keychain. The long-lived credential that keeps the connection alive is stored by the operating system, not written into Earkeep's configuration file. That file holds only which provider is connected, the account label, and whether it is enabled.

Your events are not copied to a server. Earkeep talks to Google directly from your device and there is no Earkeep server in the middle, because there is no Earkeep server. See private by design.

All-day events, declined invitations and cancelled events never become spans, and neither does an event during which nobody said anything. Those rules are the same for every provider and are described on calendar connection.

"No OAuth client id configured." This build was compiled without Google credentials, which happens with a build you made yourself rather than one downloaded from this site. The other three connections still work, and a calendar link is the closest substitute.

The browser opened and nothing came back. Press Cancel on the row and try again. Sign-in has a time limit, and a tab left open past it has to be restarted rather than resumed.

Your organization blocked the request. Some Workspace tenants require an administrator to approve an application before anyone in the organization can use it. Rather than wait, publish a calendar link and paste that instead: it is a feature of Google Calendar itself, so there is nothing to approve.

Some of your meetings are missing. They are probably on a secondary or shared calendar. See the note at the top of this page.

Events look stale. Press Sync now. Earkeep refreshes on its own as the day goes on, and this just skips the wait.

• Calendar connection: what an automatic span is, and what happens when the meeting doesn't match the invite.
• Connect Apple Calendar: reads every calendar in the macOS Calendar app, including Google accounts added there.
• Connect a calendar link (ICS): no account, nothing for IT to approve.
• All Earkeep how-tos.