Connect Google Calendar and Google Meet to Aithon

Aithon builds a meeting from two sources. Google Calendar supplies the meeting: its title, time and attendees. Google Meet supplies the transcript. A Meet transcript on its own has no title and no attendee email addresses, so Aithon cannot attach it to an account without the calendar event. Connect Google Calendar first, then Google Meet.

Both connections are per user and use standard Google OAuth: you sign in yourself and Aithon never sees your password.

Prerequisites

1. A Google Workspace account.
2. Transcription turned on for the meetings you want in Aithon. Meet only produces a transcript when transcription was enabled during the call.
3. An active Aithon account.

Step 1: Open Integrations

Open the menu under your name at the bottom of the left sidebar and choose Integrations.

Step 2: Connect Google Calendar

Find Google Calendar and click Connect. Google's consent screen lists two permissions; approve them and you are returned to Aithon.

Aithon reads only your primary calendar, never shared, holiday or other calendars, and never asks for calendar sharing or access-control permissions. If you decline the booking permission, the Calendar card later offers an Enable meeting booking button; when booking is enabled, Aithon adds the meeting to your calendar and holds the invitations rather than sending them itself.

Step 3: Connect Google Meet

Find Google Meet and click Connect. Google asks for one permission, meetings.space.readonly, which lets Aithon read the participants and transcripts of meetings you hosted. Approve it and you are returned to Aithon.

What is read, and when

New events and transcripts appear within about an hour, and changes, reschedules and cancellations follow through. Google keeps Meet transcripts available for a limited time, so connect Meet before the meetings you care about rather than after.

Two conditions for a transcript to land on a deal:

1. The meeting is on the calendar of the user who connected, with the customer's people among the attendees. That is how Aithon knows which account it belongs to.
2. The connected user is the host of the Meet space. Transcripts of meetings you joined but did not host cannot be read with this permission.

Meetings then appear on the account and opportunity timelines, and transcripts feed Deal Intelligence alongside email and calls.

Gmail, Google Calendar and Google Meet share one authorization

Google treats Aithon's Gmail, Google Calendar and Google Meet connections as one application, and there is no way to revoke one product's permission on its own. Disconnecting the last connected Google product revokes Aithon's Google authorization for your account; disconnecting one while others stay connected keeps the authorization in place.

Disconnecting

On the Integrations page, click Manage on the card, then Disconnect. This removes that connection for you only; other users' connections are unaffected.