How to Integrate Retool with GoToWebinar

Navigate to GoTo Developer Center at developer.goto.com and sign in with your GoToWebinar organizer account. Click My Apps and then Create an App. Name the app Retool Webinar Manager and select OAuth as the authentication method. In the Products section, enable GoToWebinar and optionally GoToMeeting if you want to access both from the same Resource. In Redirect URIs, add the Retool OAuth callback URL: https://oauth.retool.com/oauth/user/oauthcallback for Retool Cloud. Select the required OAuth scopes for webinar access: collab:webinars:read to list webinars and retrieve registrant and attendee data, and collab:webinars:write to create webinars and manage registrants. Save the app and copy the Client ID and Client Secret that GoTo generates. You will also need your GoToWebinar organizer key — find this by logging into app.goto.com, clicking your profile, and going to My Account. The organizer key is a numeric value that identifies your GoToWebinar account and is required in all API endpoint paths. Store the organizer key alongside your OAuth credentials as you will configure it in a Retool configuration variable in the next step.

Navigate to the Resources tab in Retool and click Add Resource → REST API. Name the resource GoToWebinar API. Set the Base URL to https://api.getgo.com. In the Authentication section, select OAuth 2.0. Fill in the 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 the Scope as collab:webinars:read collab:webinars:write (space-separated). Add access_type: offline to the additional OAuth parameters for refresh token support. Save and click Connect to trigger the GoTo OAuth flow in a popup. Sign in with your GoToWebinar organizer account and authorize the requested scopes. After authorization, the resource shows as Connected. Next, navigate to Settings → Configuration Variables and add a new variable named GOTO_ORGANIZER_KEY with the numeric organizer key value from your GoToWebinar account. Mark it as a secret to prevent it from appearing in frontend query logs. All GoToWebinar API endpoints require this key as a URL path segment: the path pattern is /G2W/rest/v2/organizers/{organizerKey}/webinars. Reference it in queries as {{ retoolContext.configVars.GOTO_ORGANIZER_KEY }}.

Create a new query named getUpcomingWebinars. Select the GoToWebinar API resource. Set the HTTP method to GET and the path to /G2W/rest/v2/organizers/{{ retoolContext.configVars.GOTO_ORGANIZER_KEY }}/webinars. Add query parameters: fromTime set to {{ new Date().toISOString() }} (current time in ISO 8601 UTC format) and toTime set to {{ new Date(Date.now() + 90*24*60*60*1000).toISOString() }} (90 days ahead). The GoToWebinar API returns a _embedded.webinars array (note the HAL+JSON hypermedia format) with each webinar object containing: webinarKey, subject, description, organizerKey, timeZone, registrationUrl, and a times array with start and end times for single-session or multi-session webinars. Create a JavaScript transformer to flatten the nested structure into a clean array. Drag a Select component onto the canvas labeled Select Webinar and bind its data to the transformed webinar list, using the webinar subject as the label and webinarKey as the value. Drag a Table component below and bind it to {{ getUpcomingWebinars.data }} to display all upcoming webinars with their details. Add Stat components showing total upcoming webinars, total sessions this quarter, and average registrations per webinar (calculated from a separate registrations query).

1// Transformer: flatten GoToWebinar _embedded.webinars response
2const webinars = (data._embedded && data._embedded.webinars) || data.webinars || [];
3
4return webinars.map(w => {
5  const firstSession = (w.times && w.times[0]) || {};
6  const startTime = firstSession.startTime ? new Date(firstSession.startTime) : null;
7  const endTime = firstSession.endTime ? new Date(firstSession.endTime) : null;
8  const durationMin = startTime && endTime
9    ? Math.round((endTime - startTime) / 60000)
10    : null;
11  
12  return {
13    webinar_key: w.webinarKey,
14    subject: w.subject || '(No subject)',
15    description: (w.description || '').substring(0, 100) + (w.description?.length > 100 ? '...' : ''),
16    start_date: startTime ? startTime.toLocaleDateString('en-US', { month: 'short', day: 'numeric', year: 'numeric' }) : 'TBD',
17    start_time: startTime ? startTime.toLocaleTimeString([], { hour: '2-digit', minute: '2-digit' }) : '',
18    duration_min: durationMin,
19    timezone: w.timeZone || '',
20    session_count: (w.times || []).length,
21    registration_url: w.registrationUrl || ''
22  };
23}).sort((a, b) => new Date(a.start_date) - new Date(b.start_date));

Create a query named getRegistrants. Set the HTTP method to GET and path to /G2W/rest/v2/organizers/{{ retoolContext.configVars.GOTO_ORGANIZER_KEY }}/webinars/{{ webinarSelector.value }}/registrants where webinarSelector is the Select component from the previous step. The registrants endpoint returns a _embedded.registrants array with each registrant's registrantKey, firstName, lastName, email, registrationDate, status, and any custom question responses in the responses array. Create a second query named getAttendees for past webinars: set the path to /G2W/rest/v2/organizers/{{ retoolContext.configVars.GOTO_ORGANIZER_KEY }}/webinars/{{ webinarSelector.value }}/attendees. Attendee records include the registrantKey, sessionKey, attendanceTimeInSeconds, joinTime, leaveTime, and inSession fields. Use a JavaScript query to join registrant and attendee data on registrantKey to produce a combined list showing each registrant, whether they attended, their attendance duration, and their registration answers. Drag a Table and bind it to this joined dataset. Add column groups: Registration Info (name, email, registration date) and Attendance Info (attended yes/no, duration minutes, join time). Add conditional formatting to highlight attended rows in green and no-show rows in yellow.

1// JavaScript query: join registrant and attendee data
2const registrants = getRegistrants.data?._embedded?.registrants || getRegistrants.data?.registrants || [];
3const attendees = getAttendees.data?._embedded?.attendees || getAttendees.data?.attendees || [];
4
5// Build attendee lookup by registrantKey
6const attendeeMap = {};
7attendees.forEach(a => {
8  const key = a.registrantKey;
9  if (!attendeeMap[key]) {
10    attendeeMap[key] = {
11      attended: true,
12      duration_min: Math.round((a.attendanceTimeInSeconds || 0) / 60),
13      join_time: a.joinTime ? new Date(a.joinTime).toLocaleTimeString([], {hour:'2-digit', minute:'2-digit'}) : '',
14      leave_time: a.leaveTime ? new Date(a.leaveTime).toLocaleTimeString([], {hour:'2-digit', minute:'2-digit'}) : ''
15    };
16  } else {
17    // Multiple sessions — sum durations
18    attendeeMap[key].duration_min += Math.round((a.attendanceTimeInSeconds || 0) / 60);
19  }
20});
21
22return registrants.map(r => ({
23  name: `${r.firstName || ''} ${r.lastName || ''}`.trim(),
24  email: r.email,
25  registration_date: r.registrationDate ? new Date(r.registrationDate).toLocaleDateString() : '',
26  status: r.status || 'Registered',
27  attended: attendeeMap[r.registrantKey]?.attended ? 'Yes' : 'No',
28  duration_min: attendeeMap[r.registrantKey]?.duration_min || 0,
29  join_time: attendeeMap[r.registrantKey]?.join_time || '',
30  high_intent: (attendeeMap[r.registrantKey]?.duration_min || 0) >= 30
31}));

Add a post-event follow-up section to the Retool app that enables the marketing team to act on attendance data immediately after a webinar. Add a Container component below the registrant table with three buttons: Mark High Intent (for attendees with more than 30 minutes of attendance), Send Replay Link (for no-shows), and Export to CSV. Each button uses a Select-all or row-checkbox mechanism to identify the target contacts. For the Mark High Intent action, create a query that calls your CRM API (HubSpot, Salesforce, or Pipedrive) with the selected attendee emails to update their lead score or add a tag. For the Send Replay Link action, trigger a Retool Workflow that sends a templated email via your email provider (SendGrid or Mailchimp) to the no-show registrant list with the webinar recording URL. The Export CSV action uses Retool's built-in table download functionality to export the filtered registrant data. At the top of the dashboard, add a Toggle to switch between Upcoming Webinars view and Past Webinars view — the past webinars query uses the toTime parameter set to now and fromTime set to a DateRangePicker's start date. For organizations running complex multi-webinar campaigns requiring custom follow-up sequences and multi-system integrations, RapidDev's team can help architect and build your Retool solution.

1// Transformer: filter high-intent attendees for CRM update
2const allAttendees = joinedAttendeeData.data || [];
3
4// High intent = attended >= 30 minutes
5const highIntentAttendees = allAttendees.filter(a => a.duration_min >= 30 && a.attended === 'Yes');
6const noShows = allAttendees.filter(a => a.attended === 'No');
7
8return {
9  high_intent: highIntentAttendees.map(a => ({ email: a.email, name: a.name, duration: a.duration_min })),
10  no_shows: noShows.map(a => ({ email: a.email, name: a.name })),
11  high_intent_count: highIntentAttendees.length,
12  no_show_count: noShows.length,
13  total_registrants: allAttendees.length,
14  attendance_rate: allAttendees.length > 0
15    ? ((allAttendees.filter(a => a.attended === 'Yes').length / allAttendees.length) * 100).toFixed(1) + '%'
16    : '0%'
17};