Day 3: Google Cloud Console setup

May 30, 2026

What I worked on

  • Created project
  • Added OAuth credential

What I learned

Setting up Google Calendar integration requires first configuring the Google Cloud Console correctly.

Google Cloud Console Setup

To set up Calendar integration, you need to make a new project, enable the Google Calendar API, configure the OAuth consent screen, and finally create an OAuth Client ID.

what is an OAuth Client ID, and why is it necessary?

It helps identify your application. Since OAuth implies a three-party negotiation, Google needs to know information about your application, like what it does and the type of services it accesses so that the user knows who they’re giving their data to.

It’s also used as a way for Google to keep track of what the user has agreed to. After the user agrees from the consent screen, Google stores that the user has granted this Client ID access to the calendar.readonly scope.

Lastly, it’s used so that Google can verify that the application’s verified website domain is sending requests with the Client ID. Since the Client ID is public, Google needs to verify that the developer’s website is the one sending the request.

Here’s what my Google Cloud Console setup looks like:

alt text

What’s still confusing

How do service accounts work?

What are client secrets and what are they used for?