How to Integrate Retool with GoToMeeting

Navigate to GoTo Developer Center at developer.goto.com and sign in with your GoToMeeting account credentials. Click My Apps in the top navigation and then Create an App. Give the app a name like Retool Meeting Manager and select OAuth as the authentication type. Choose the appropriate product scope — select GoToMeeting for meeting access. In the Redirect URIs section, add Retool's OAuth callback URL: https://oauth.retool.com/oauth/user/oauthcallback for Retool Cloud, or your self-hosted Retool instance's equivalent callback URL. Select the required OAuth scopes for your integration: collab:meetings:read to list and view meetings, collab:meetings:write to create and modify meetings. If you also plan to access GoToWebinar from the same app, add the webinar scopes as well. Save the app. GoTo generates a Client ID and Client Secret — copy both values securely. Note your account's organizer key, which is available in your GoToMeeting account settings and is required as a URL parameter in most GoToMeeting API endpoints (the organizer key identifies which GoToMeeting account's data to retrieve). The Client ID and Client Secret will be entered into Retool's Resource configuration in the next step.

Navigate to the Resources tab in Retool and click Add Resource → REST API. Name the resource GoToMeeting API. Set the Base URL to https://api.getgo.com. In the Authentication section, select OAuth 2.0. Fill in the OAuth fields: Authorization URL as https://authentication.logmeininc.com/oauth/authorize, Token URL as https://authentication.logmeininc.com/oauth/token, your Client ID and Client Secret from the developer portal, and Scope as collab:meetings:read collab:meetings:write (space-separated). The GoTo OAuth endpoints use LogMeIn's authentication infrastructure even for GoToMeeting — this is expected. Click Save and then click the Connect button to trigger the OAuth authorization flow. A GoTo sign-in popup appears where you log in with your GoToMeeting organizer account and authorize the app. After authorization, the resource shows as Connected. To configure the organizer key for queries, navigate to Settings → Configuration Variables and add a variable named GOTO_ORGANIZER_KEY containing your GoToMeeting organizer key (found in your GoToMeeting account at app.goto.com → Profile → My Account). This key will be referenced in API endpoint paths as a URL segment.

Create a new query named getUpcomingMeetings in the Code panel. Select the GoToMeeting API resource. Set the HTTP method to GET and the path to /G2M/rest/v2/organizers/{{ retoolContext.configVars.GOTO_ORGANIZER_KEY }}/upcomingMeetings. Add the query parameter fromDate set to {{ new Date().toISOString().split('T')[0] }} to get meetings starting from today, and toDate set to {{ new Date(Date.now() + 30*24*60*60*1000).toISOString().split('T')[0] }} for the next 30 days. Click Run. GoTo returns a meetings array with objects containing: meetingId, subject, startTime, endTime, status, maxParticipants, and hostExitUrl. Create a JavaScript transformer to reshape the data: calculate duration in minutes from startTime and endTime, format the dates for display, and extract the join URL from the meeting object. Drag a Table component onto the canvas and bind it to {{ getUpcomingMeetings.data }}. Configure columns: subject, date (formatted), start_time, duration_min (labeled Duration (min)), and a Link component using the joinUrl field for one-click meeting access. Add a Refresh button with onClick event triggering getUpcomingMeetings. Set the query to auto-run on page load.

1// Transformer: format GoToMeeting upcoming meetings for Table display
2const meetings = data.meetings || data || [];
3const meetingsArray = Array.isArray(meetings) ? meetings : [meetings];
4
5return meetingsArray.map(m => {
6  const start = new Date(m.startTime);
7  const end = new Date(m.endTime);
8  const durationMin = Math.round((end - start) / 60000);
9  
10  return {
11    meeting_id: m.meetingId,
12    subject: m.subject || '(No subject)',
13    date: start.toLocaleDateString('en-US', { weekday: 'short', month: 'short', day: 'numeric' }),
14    start_time: start.toLocaleTimeString([], { hour: '2-digit', minute: '2-digit' }),
15    end_time: end.toLocaleTimeString([], { hour: '2-digit', minute: '2-digit' }),
16    duration_min: durationMin,
17    status: m.status || 'scheduled',
18    max_participants: m.maxParticipants || 'N/A',
19    join_url: m.joinURL || m.joinUrl || ''
20  };
21}).sort((a, b) => new Date(a.start_time) - new Date(b.start_time));

Drag a Form component onto the canvas for meeting creation. Add the following form fields: a Text Input for Meeting Subject, a DateTimePicker for Start Time, a Select component for Duration (with options 30, 45, 60, 90, 120 minutes labeled in minutes), and an optional Text Input for Meeting Password. Create a new query named createMeeting. Set the HTTP method to POST and the path to /G2M/rest/v2/organizers/{{ retoolContext.configVars.GOTO_ORGANIZER_KEY }}/meetings. Set the body type to JSON. Construct the request body from the form fields: subject from the text input, starttime formatted as an ISO 8601 string from the datetime picker value, endtime calculated by adding the selected duration in milliseconds to the start time, and optionally conferenceCallInfo and meetingSettings if you want to configure specific options. Click the Form's Submit button event handler and configure it to trigger createMeeting. On the createMeeting query's On Success event, trigger getUpcomingMeetings to refresh the meetings table, and use a Show notification action to display the new meeting's join URL in a success toast. Handle the On Failure event with an error notification displaying the API error message. Add a confirmation modal before triggering createMeeting if your team accidentally submits meetings — wrap the trigger in an event that first shows a Confirm dialog.

1// POST body for creating a GoToMeeting session
2// Use this as the JSON body in the createMeeting query
3{
4  "subject": "{{ meetingSubjectInput.value }}",
5  "starttime": "{{ new Date(startTimePicker.value).toISOString() }}",
6  "endtime": "{{ new Date(new Date(startTimePicker.value).getTime() + parseInt(durationSelect.value) * 60000).toISOString() }}",
7  "conferenceCallInfo": "PSTN",
8  "meetingSettings": {
9    "waitingRoom": true,
10    "attendeeAudioAccess": "Muted"
11  }
12}

Create a third query named getHistoricalMeetings for the analytics view. Set the HTTP method to GET and path to /G2M/rest/v2/organizers/{{ retoolContext.configVars.GOTO_ORGANIZER_KEY }}/historicalMeetings. Add query parameters fromDate and toDate referencing a DateRangePicker component. The historicalMeetings endpoint returns past meeting records including actual start and end times, number of attendees, and session key for retrieving attendee details. Write a transformer to aggregate total meetings per week using a reduce function on the startTime field. Drag a Chart component and bind it to the weekly aggregated data, setting it to a Bar Chart with week as X axis and meeting count as Y axis. Add Stat components showing total meetings in period, total meeting hours, and average attendees. Organize the full dashboard with a top section containing the date picker and stat components, a middle section with the Chart, and tabs below for Upcoming Meetings (with the creation form) and Meeting History (with the historical table). For comprehensive meeting management across multiple organizers, this kind of multi-organizer view often requires connecting to multiple GoToMeeting accounts — consider using Retool's configuration variables to store multiple organizer keys and a Select component to switch between them.

1// Transformer: aggregate historical meetings by week
2const meetings = data.meetings || [];
3
4const weeklyAgg = {};
5
6meetings.forEach(m => {
7  const date = new Date(m.startTime);
8  // Get the Monday of the week
9  const dayOfWeek = date.getDay();
10  const monday = new Date(date);
11  monday.setDate(date.getDate() - (dayOfWeek === 0 ? 6 : dayOfWeek - 1));
12  const weekKey = monday.toISOString().split('T')[0];
13  
14  if (!weeklyAgg[weekKey]) {
15    weeklyAgg[weekKey] = {
16      week_start: weekKey,
17      meeting_count: 0,
18      total_minutes: 0,
19      total_attendees: 0
20    };
21  }
22  const start = new Date(m.startTime);
23  const end = new Date(m.endTime);
24  weeklyAgg[weekKey].meeting_count += 1;
25  weeklyAgg[weekKey].total_minutes += Math.round((end - start) / 60000);
26  weeklyAgg[weekKey].total_attendees += m.numAttendees || 0;
27});
28
29return Object.values(weeklyAgg)
30  .sort((a, b) => new Date(a.week_start) - new Date(b.week_start))
31  .map(w => ({
32    ...w,
33    total_hours: (w.total_minutes / 60).toFixed(1),
34    avg_attendees: w.meeting_count > 0
35      ? (w.total_attendees / w.meeting_count).toFixed(1)
36      : 0
37  }));