Connect Google Calendar to Rig

    Rig syncs your calendar list and the events on each calendar, with recurring events expanded into individual occurrences and cancellations kept. You can connect with Google sign-in, or share calendars with a service account.

    Before you start

    • Choose a route. Google sign-in finds every calendar you can read. The service account route reads only the calendars you share and list.
    • For the service account route, you need permission to share each calendar. If a calendar belongs to a work or school account, your administrator decides whether you can share it.

    Step 1: Share each calendar (service account route only)

    Skip this step if you use Google sign-in.

    1. In Google Calendar, point at the calendar under My calendars, click the three dots, and choose Settings and sharing.
    2. Open Shared with and click Add people and groups.
    3. Enter the service account email Rig shows you and give it See all event details.
    4. Send the invite. Note each calendar's ID. A person's primary calendar ID is their email address.

    Step 2: Connect it in Rig

    Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

    1. In Rig, open Connections and search for Google Calendar.
    2. For Google sign-in, choose the sign-in with Google option, click Authorize with Google Calendar, pick your account and approve read-only access.
    3. For the service account route, choose the service account option instead. Paste the full JSON key into Service account JSON key (direct auth).
    4. Under Calendar IDs (service-account mode, comma-separated) list the calendars you shared, separated by commas. This field is required for a service account and should stay blank for Google sign-in.
    5. Save the connection.

    What Rig pulls in

    Google Calendar lands in its own google_calendar schema in your warehouse:

    • Calendars: The calendar list, with each calendar's name and settings.
    • Events: Each event, with recurring events expanded into occurrences and cancelled events included.

    Events sync incrementally on each event's last-modified time.

    Good to know

    • The same meeting can appear on an organiser's and an attendee's calendar, so events are identified by calendar and event ID together.
    • A calendar shared with a service account never shows up in the service account's own list, which is why the Calendar IDs field is required there.
    • Rig asks for read-only calendar access, so it cannot create or change events.
    • To disconnect Google Calendar, click the bin icon on the source's row under Sources & actions. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

    What people use this for

    • See where selling time actually goes
    • Measure meeting load honestly
    • Track cancellations

    More ideas for using Google Calendar

    Google Calendar documentation

    Was this guide helpful?