How to Integrate Lovable with GoToMeeting

Navigate to developer.goto.com and sign in with your GoTo account. Click 'My Apps' → 'Add a New App'. Name the app (e.g., 'Lovable Meeting Integration') and select 'Authorization Code' as the authorization type. Add a redirect URI — use https://httpbin.org/get temporarily to complete the initial authorization in a browser and capture the code. On the Scopes tab, add the meeting-specific scopes: 'collab:meetings_management' for creating and managing meetings, and 'collab:meetings_read' for reading meeting data and attendance. Do not add webinar scopes unless you also need GoToWebinar access. Click Save. Copy the Client ID and Client Secret from the app details page. These are your OAuth2 credentials. The next step is completing the browser-based authorization to obtain your initial refresh token, which your Edge Function will use to generate access tokens indefinitely.

Build and open the authorization URL in your browser to complete the one-time OAuth2 flow. The URL format is: https://authentication.logmeininc.com/oauth/authorize?client_id={yourClientId}&response_type=code&redirect_uri={yourRedirectUri}&scope=collab%3Ameetings_management%20collab%3Ameetings_read. Replace {yourClientId} with your actual Client ID and {yourRedirectUri} with the encoded redirect URI you configured. After authorizing, you will be redirected to your redirect URI with a code parameter in the URL (e.g., https://httpbin.org/get?code=XXXXXXXX). Copy the code value. Now exchange it for tokens by making a POST request to https://authentication.logmeininc.com/oauth/token. Use Basic Auth (your Client ID as username, Client Secret as password) with grant_type=authorization_code, code, and redirect_uri in the body. This returns access_token, refresh_token, and account_key. In Lovable's Cloud tab → Secrets, add: GOTO_CLIENT_ID, GOTO_CLIENT_SECRET, GOTO_REFRESH_TOKEN (the refresh token from above), and GOTO_ACCOUNT_KEY (the numeric account key). These are the same secret names used in GoToWebinar integration — if you have both, you can share the same OAuth app and secrets between both Edge Functions.

Create an Edge Function called gotomeeting that handles meeting creation, listing, and attendance retrieval. The function must first refresh the access token using the stored refresh token, then call the appropriate GoToMeeting API endpoint based on the action in the request body. The GoToMeeting API base URL for meeting management is https://api.getgo.com/G2M/rest/v2/me/meetings (note G2M for GoToMeeting, versus G2W for GoToWebinar). For creating a meeting, POST to this endpoint with subject, startTime, endTime, and optionally conferenceCallInfo, passwordRequired, and maxParticipants fields. The response includes meetingId, joinURL, and hostURL. For listing meetings, GET the same endpoint with optional query parameters for time range filtering. For attendance data after a meeting ends, use GET /meetings/{meetingId}/attendees to retrieve participant details including join time, leave time, and duration. This endpoint is only available after the meeting has ended. Ask Lovable to generate the Edge Function with all three operations (create, list, attendance) controlled by an action parameter. Review the deployed code to verify secret names and API endpoints are correct.

1// supabase/functions/gotomeeting/index.ts
2import { serve } from 'https://deno.land/std@0.168.0/http/server.ts';
3
4const corsHeaders = {
5  'Access-Control-Allow-Origin': '*',
6  'Access-Control-Allow-Headers': 'authorization, x-client-info, apikey, content-type',
7};
8
9async function getAccessToken(): Promise<string> {
10  const clientId = Deno.env.get('GOTO_CLIENT_ID')!;
11  const clientSecret = Deno.env.get('GOTO_CLIENT_SECRET')!;
12  const refreshToken = Deno.env.get('GOTO_REFRESH_TOKEN')!;
13  const credentials = btoa(`${clientId}:${clientSecret}`);
14
15  const res = await fetch('https://authentication.logmeininc.com/oauth/token', {
16    method: 'POST',
17    headers: {
18      'Authorization': `Basic ${credentials}`,
19      'Content-Type': 'application/x-www-form-urlencoded',
20    },
21    body: `grant_type=refresh_token&refresh_token=${encodeURIComponent(refreshToken)}`,
22  });
23  if (!res.ok) throw new Error(`GoTo auth error: ${await res.text()}`);
24  const data = await res.json();
25  return data.access_token;
26}
27
28serve(async (req) => {
29  if (req.method === 'OPTIONS') return new Response('ok', { headers: corsHeaders });
30
31  try {
32    const { action, meetingId, subject, startTime, endTime } = await req.json();
33    const token = await getAccessToken();
34    const headers = { 'Authorization': `Bearer ${token}`, 'Content-Type': 'application/json' };
35    const baseUrl = 'https://api.getgo.com/G2M/rest/v2';
36
37    if (action === 'create') {
38      const res = await fetch(`${baseUrl}/me/meetings`, {
39        method: 'POST',
40        headers,
41        body: JSON.stringify({ subject, startTime, endTime }),
42      });
43      const data = await res.json();
44      if (!res.ok) throw new Error(`Create error: ${JSON.stringify(data)}`);
45      return new Response(JSON.stringify({
46        meetingId: data.meetingId,
47        joinURL: data.joinURL,
48        hostURL: data.hostURL,
49        subject: data.subject,
50        startTime: data.startTime,
51      }), { headers: { ...corsHeaders, 'Content-Type': 'application/json' } });
52    }
53
54    if (action === 'list') {
55      const now = new Date().toISOString();
56      const future = new Date(Date.now() + 90 * 24 * 60 * 60 * 1000).toISOString();
57      const res = await fetch(`${baseUrl}/me/meetings?startDate=${now}&endDate=${future}`, { headers });
58      const data = await res.json();
59      return new Response(JSON.stringify(data), { headers: { ...corsHeaders, 'Content-Type': 'application/json' } });
60    }
61
62    if (action === 'attendance') {
63      const res = await fetch(`${baseUrl}/meetings/${meetingId}/attendees`, { headers });
64      const data = await res.json();
65      return new Response(JSON.stringify(data), { headers: { ...corsHeaders, 'Content-Type': 'application/json' } });
66    }
67
68    throw new Error('Invalid action');
69  } catch (error) {
70    return new Response(
71      JSON.stringify({ error: error.message }),
72      { status: 500, headers: { ...corsHeaders, 'Content-Type': 'application/json' } }
73    );
74  }
75});

With the Edge Function deployed, use Lovable's chat to build the frontend components. A meeting scheduler form should collect a meeting title and start/end time from the user, call the gotomeeting Edge Function with action='create', and display the resulting join URL. Store meeting data in a Supabase table — at minimum, columns for meeting_id, subject, start_time, end_time, join_url, host_url, and created_by (user ID from Supabase Auth). The host_url should only be visible to the meeting organizer — apply a Row Level Security policy that restricts host_url visibility based on the created_by field matching the logged-in user. For meeting participants who need to join, display the join_url prominently with a 'Copy Link' button and a 'Join Now' link that opens in a new tab. Consider sending the join URL via Resend email to invited participants if your app manages guest lists. For complex scheduling scenarios with calendar integration, timezone handling, and recurring meetings, RapidDev's team can help design the full scheduling system.