How to Integrate Retool with Google Meet

Navigate to Google Cloud Console → APIs & Services → Library and search for Google Calendar API. Click Enable if it is not already active. To also enable the beta Google Meet REST API for space management, search for Google Meet API and enable it separately — this is optional for basic meeting data retrieval via Calendar. In APIs & Services → Credentials, click Create Credentials → OAuth client ID. Set the application type to Web application. In Authorized redirect URIs, add Retool's OAuth callback URL: https://oauth.retool.com/oauth/user/oauthcallback for Retool Cloud. Copy the Client ID and Client Secret. Configure the OAuth consent screen: go to APIs & Services → OAuth consent screen, set User Type to Internal for Google Workspace single-organization use, and add the scope https://www.googleapis.com/auth/calendar.readonly. This read-only scope allows listing events and reading attendee data without the risk of accidentally modifying calendar data. If you need to create or modify Meet meetings from Retool, add https://www.googleapis.com/auth/calendar.events instead. Save the consent screen. For organization-wide analytics accessing multiple employees' calendars, configure a service account with domain-wide delegation — in the service account settings, enable domain-wide delegation and add the calendar.readonly scope to the Workspace Admin Console delegated scopes. This is an advanced configuration but required for HR and ops teams that need cross-user calendar visibility.

Navigate to the Resources tab in Retool and click Add Resource → REST API. Name the resource Google Calendar API. Set the Base URL to https://www.googleapis.com/calendar/v3. In the Authentication section, select OAuth 2.0. Enter the OAuth configuration: Authorization URL as https://accounts.google.com/o/oauth2/auth, Token URL as https://oauth2.googleapis.com/token, your Client ID, Client Secret, and Scope as https://www.googleapis.com/auth/calendar.readonly. Add access_type: offline in the additional OAuth parameters to receive a refresh token for long-lived access. Save and click Connect to trigger the OAuth authorization flow — a Google sign-in popup appears where you authorize the app with the requested calendar scope. After authorization, the resource shows as Connected with your Google account email. If you need to query multiple users' calendars using domain-wide delegation with a service account, configure the Base URL the same way but authenticate via Bearer token using the service account's access token stored in a configuration variable, similar to the Vertex AI setup. Verify the connection by creating a test query with GET path /users/me/calendarList to list your accessible calendars — this confirms the resource configuration is correct before building the main meeting queries.

Create a new query named getMeetEvents. Select the Google Calendar API resource. Set the HTTP method to GET and the path to /calendars/primary/events. Add the following query parameters to filter and sort results: timeMin set to {{ new Date(Date.now() - 30*24*60*60*1000).toISOString() }} (30 days ago in ISO format), timeMax set to {{ new Date().toISOString() }} (current time), singleEvents set to true (expands recurring events into individual instances), orderBy set to startTime, and maxResults set to 500. Optionally add q: meet to text-search for Meet-specific events, though this is unreliable — instead filter in the transformer. Click Run. The API returns a large JSON response with an items array containing all calendar events in the specified time range. Each event has a conferenceData object when a video conference is attached. For Google Meet events specifically, conferenceData.conferenceSolution.key.type equals hangoutsMeet. Create a JavaScript transformer that filters the items array to only include events with this conference type and extracts the relevant fields: meeting title, start/end times, duration in minutes, organizer email, attendee list with statuses, and the Meet join URL from conferenceData.entryPoints[0].uri.

1// Transformer: filter and flatten Google Calendar events to Meet meetings
2const items = data.items || [];
3
4const meetEvents = items.filter(event => {
5  return event.conferenceData &&
6    event.conferenceData.conferenceSolution &&
7    event.conferenceData.conferenceSolution.key.type === 'hangoutsMeet';
8});
9
10return meetEvents.map(event => {
11  const start = new Date(event.start.dateTime || event.start.date);
12  const end = new Date(event.end.dateTime || event.end.date);
13  const durationMin = Math.round((end - start) / 60000);
14  
15  const meetLink = (event.conferenceData.entryPoints || [])
16    .find(ep => ep.entryPointType === 'video');
17  
18  const acceptedCount = (event.attendees || []).filter(a => a.responseStatus === 'accepted').length;
19  const totalCount = (event.attendees || []).length;
20  
21  return {
22    title: event.summary || '(No title)',
23    start_time: start.toLocaleString(),
24    start_iso: start.toISOString(),
25    date: start.toLocaleDateString(),
26    duration_min: durationMin,
27    organizer: event.organizer?.email || '',
28    attendee_count: totalCount,
29    accepted_count: acceptedCount,
30    meet_url: meetLink?.uri || '',
31    conference_id: event.conferenceData.conferenceId || '',
32    status: event.status || 'confirmed',
33    is_recurring: !!event.recurringEventId
34  };
35});

Use a JavaScript query to aggregate the Meet event data by attendee for meeting load analysis. Reference getMeetEvents.data in the JavaScript query. Iterate over all meetings, then for each meeting iterate over its attendees array, and accumulate meeting counts and total minutes per attendee email. The result is a dictionary keyed by email with meeting_count and total_minutes values. Convert to an array sorted by total minutes descending for the Table component. Drag a Table component onto the canvas and bind it to this aggregated data. Configure columns: email, meeting_count (labeled Meetings This Month), and total_hours (calculated as total_minutes / 60, formatted to one decimal). Add conditional row formatting to highlight rows where total_hours exceeds a threshold — drag a Number Input component labeled Meeting Hour Threshold and reference its value in the conditional: {{ currentRow.total_hours > meetingThreshold.value }}. Drag a Bar Chart component and bind it to the same aggregated data, setting the X axis to email and Y axis to total_hours. Add a Select dropdown to filter by a specific meeting organizer or team domain. Place a DateRangePicker at the top to control the Calendar API query time range by referencing the picker values in the timeMin and timeMax parameters.

1// JavaScript query: aggregate meeting load by attendee
2const meetings = getMeetEvents.data || [];
3
4const loadMap = {};
5
6meetings.forEach(meeting => {
7  // Parse attendee emails from the raw event data (need to map back)
8  // This approach works if the transformer includes the attendees array
9  const rawEvent = getMeetEventsRaw.data?.items?.find(
10    e => e.conferenceData?.conferenceId === meeting.conference_id
11  );
12  const attendees = rawEvent?.attendees || [];
13  
14  attendees.forEach(attendee => {
15    const email = attendee.email;
16    if (!loadMap[email]) {
17      loadMap[email] = { email, meeting_count: 0, total_minutes: 0 };
18    }
19    if (attendee.responseStatus !== 'declined') {
20      loadMap[email].meeting_count += 1;
21      loadMap[email].total_minutes += meeting.duration_min;
22    }
23  });
24});
25
26return Object.values(loadMap)
27  .map(r => ({
28    ...r,
29    total_hours: (r.total_minutes / 60).toFixed(1)
30  }))
31  .sort((a, b) => b.total_minutes - a.total_minutes);