Google Calendar

Connect Google Calendar to read and manage events, list the calendars you have access to, and check when people are free or busy. metamorphOS connects with Google sign-in (OAuth), so you grant access once and it acts on your behalf.

What you can do

• Events: list, view, create, update, and delete events on a calendar.
• Calendars: list the calendars available to the connected account.
• Availability: check free/busy times across one or more calendars for a given window.

Before you start

You need a Google account with access to the calendars you want to use, and a Google Cloud project you can administer (or permission to create one). Setting up the sign-in flow requires the ability to configure an OAuth consent screen and create OAuth client credentials in that project.

Set up Google

1. Create or select a Google Cloud project. In the Google Cloud Console, open the project picker and choose New Project (or select an existing one).
2. Enable the Calendar API. Go to APIs & Services > Library, search for Google Calendar API, and choose Enable for this project.
3. Configure the consent screen. Go to APIs & Services > OAuth consent screen. Pick the user type (Internal for a Workspace organization, otherwise External), and set the app name, support email, and developer contact. While the app is still in testing, add the Google accounts that will connect under Test users.
4. Grant calendar access. On the consent screen’s Scopes step, add permission to view and manage calendar events, and to read your calendars.
5. Create OAuth credentials. Go to APIs & Services > Credentials > Create Credentials > OAuth client ID, choose application type Web application, and give it a name (for example, metamorphOS).
6. Add the redirect URL. On the OAuth client, add the callback URL that metamorphOS gives you as an Authorized redirect URI, then save. Copy the generated Client ID and Client secret.

Connect in metamorphOS

Activate the Google Calendar connector from the marketplace and add an account. Provide the Client ID and Client secret from the step above, then start the connect flow: metamorphOS sends you to Google to sign in and approve access, and Google returns you to metamorphOS to finish. Once approved, the account is connected and ready to use. Your credentials are stored securely per account, never in the connector itself.

Good to know

• Events are addressed by a calendar and an event id. Use primary for the connected account’s main calendar, or a calendar’s email address for a shared one.
• Field coverage is a representative subset of Google Calendar, focused on the common event and scheduling fields. Some advanced fields may not be available yet, so confirm the fields you need before relying on them in production.