How to Integrate Lovable with Google Meet

Navigate to console.cloud.google.com and select or create a project. In the left sidebar, go to 'APIs & Services' → 'Library', search for 'Google Calendar API', and click Enable. Next, go to 'APIs & Services' → 'Credentials' and click 'Create Credentials' → 'Service Account'. Give the service account a descriptive name like 'lovable-meet-bot' and click Create and Continue. You do not need to assign any Google Cloud IAM roles for Calendar API access — click Done. Back on the Credentials page, click on your new service account to open it. Go to the 'Keys' tab and click 'Add Key' → 'Create New Key'. Select JSON format and click Create. This downloads a JSON file containing your service account credentials, including the private_key, client_email, and other fields. Keep this file secure — treat it like a password. You will need the private_key (a PEM-formatted RSA private key) and the client_email from this file for the next step.

The service account JSON file contains several fields, but you only need two for the Edge Function: private_key and client_email. In your Lovable editor, open the Cloud tab by clicking the '+' panel selector at the top right, then click Cloud. Scroll to 'Secrets' and add two secrets. Name the first secret GOOGLE_SERVICE_ACCOUNT_EMAIL and paste the client_email value from your JSON file (it looks like lovable-meet-bot@your-project.iam.gserviceaccount.com). Name the second secret GOOGLE_SERVICE_ACCOUNT_PRIVATE_KEY and paste the entire private_key value — this is a multi-line string starting with -----BEGIN RSA PRIVATE KEY----- or -----BEGIN PRIVATE KEY-----. Copy the entire string including the header and footer lines. A common issue: the private key in the JSON file has literal \n characters representing newlines. When you paste it into Cloud → Secrets, you may need to replace the literal \n sequences with actual newlines (or your Edge Function code will handle this with a .replace(/\\n/g, '\n') call). Lovable's Secrets panel stores the value as-is, so be careful about how the key is formatted. Lovable blocks approximately 1,200 hardcoded keys daily — always use Secrets, never paste keys in chat.

The Edge Function needs to: (1) construct a JWT from the service account credentials, (2) exchange the JWT for a Google access token, and (3) call the Calendar API to create an event with conferenceData. Deno has built-in crypto support for JWT signing. The JWT for Google service accounts uses RS256 signing. The header is { alg: 'RS256', typ: 'JWT' }. The payload includes iss (service account email), scope (https://www.googleapis.com/auth/calendar), aud (https://oauth2.googleapis.com/token), exp (one hour from now), and iat (now). The token endpoint is https://oauth2.googleapis.com/token with grant_type=urn:ietf:params:oauth:grant-type:jwt-bearer. Once you have the access token, POST to https://www.googleapis.com/calendar/v3/calendars/primary/events?conferenceDataVersion=1 with the event body. The conferenceData field must include createRequest with requestId (unique per request) and conferenceSolutionKey.type set to 'hangoutsMeet'. The response contains conferenceData.entryPoints array — find the entry with entryPointType 'video' and return its uri as the Meet link.

1// supabase/functions/google-meet/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 getGoogleAccessToken(): Promise<string> {
10  const email = Deno.env.get('GOOGLE_SERVICE_ACCOUNT_EMAIL')!;
11  const privateKeyPem = Deno.env.get('GOOGLE_SERVICE_ACCOUNT_PRIVATE_KEY')!.replace(/\\n/g, '\n');
12
13  const now = Math.floor(Date.now() / 1000);
14  const payload = {
15    iss: email,
16    scope: 'https://www.googleapis.com/auth/calendar',
17    aud: 'https://oauth2.googleapis.com/token',
18    exp: now + 3600,
19    iat: now,
20  };
21
22  // Encode JWT header and payload
23  const header = btoa(JSON.stringify({ alg: 'RS256', typ: 'JWT' })).replace(/=/g, '').replace(/\+/g, '-').replace(/\//g, '_');
24  const body = btoa(JSON.stringify(payload)).replace(/=/g, '').replace(/\+/g, '-').replace(/\//g, '_');
25  const signingInput = `${header}.${body}`;
26
27  // Import private key
28  const pemContents = privateKeyPem.replace(/-----BEGIN.*-----/, '').replace(/-----END.*-----/, '').replace(/\s/g, '');
29  const binaryKey = Uint8Array.from(atob(pemContents), c => c.charCodeAt(0));
30  const cryptoKey = await crypto.subtle.importKey(
31    'pkcs8', binaryKey.buffer,
32    { name: 'RSASSA-PKCS1-v1_5', hash: 'SHA-256' },
33    false, ['sign']
34  );
35
36  // Sign JWT
37  const signature = await crypto.subtle.sign(
38    'RSASSA-PKCS1-v1_5',
39    cryptoKey,
40    new TextEncoder().encode(signingInput)
41  );
42  const sigBase64 = btoa(String.fromCharCode(...new Uint8Array(signature))).replace(/=/g, '').replace(/\+/g, '-').replace(/\//g, '_');
43  const jwt = `${signingInput}.${sigBase64}`;
44
45  // Exchange JWT for access token
46  const tokenRes = await fetch('https://oauth2.googleapis.com/token', {
47    method: 'POST',
48    headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
49    body: `grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Ajwt-bearer&assertion=${jwt}`,
50  });
51
52  const tokenData = await tokenRes.json();
53  if (!tokenRes.ok) throw new Error(`Token error: ${JSON.stringify(tokenData)}`);
54  return tokenData.access_token;
55}
56
57serve(async (req) => {
58  if (req.method === 'OPTIONS') return new Response('ok', { headers: corsHeaders });
59
60  try {
61    const { summary, start_time, end_time, description = '' } = await req.json();
62    const accessToken = await getGoogleAccessToken();
63
64    const eventRes = await fetch(
65      'https://www.googleapis.com/calendar/v3/calendars/primary/events?conferenceDataVersion=1',
66      {
67        method: 'POST',
68        headers: { 'Authorization': `Bearer ${accessToken}`, 'Content-Type': 'application/json' },
69        body: JSON.stringify({
70          summary,
71          description,
72          start: { dateTime: start_time, timeZone: 'UTC' },
73          end: { dateTime: end_time, timeZone: 'UTC' },
74          conferenceData: {
75            createRequest: {
76              requestId: crypto.randomUUID(),
77              conferenceSolutionKey: { type: 'hangoutsMeet' },
78            },
79          },
80        }),
81      }
82    );
83
84    const event = await eventRes.json();
85    if (!eventRes.ok) throw new Error(`Calendar API error: ${JSON.stringify(event)}`);
86
87    const meetEntry = event.conferenceData?.entryPoints?.find((ep: { entryPointType: string }) => ep.entryPointType === 'video');
88    const meetLink = meetEntry?.uri ?? null;
89
90    return new Response(
91      JSON.stringify({ meetLink, eventId: event.id, eventLink: event.htmlLink }),
92      { headers: { ...corsHeaders, 'Content-Type': 'application/json' } }
93    );
94  } catch (error) {
95    return new Response(
96      JSON.stringify({ error: error.message }),
97      { status: 500, headers: { ...corsHeaders, 'Content-Type': 'application/json' } }
98    );
99  }
100});

With the Edge Function deployed, ask Lovable to build the UI component that calls it. The frontend code should call supabase.functions.invoke('google-meet', { body: { summary, start_time, end_time } }) and handle the returned meetLink. The Supabase client automatically adds the authentication header required by Edge Functions. Display the Meet link with a prominent 'Join Meeting' button and a copy-to-clipboard button. If your app manages bookings or sessions, store the meetLink and eventId in your Supabase bookings table alongside the meeting time and participant information. Make sure your Row Level Security policy allows authenticated users to read their own bookings but not others'. For emailing the link, you can chain the Edge Function response with a Resend call — Lovable can generate this combined flow if you describe it in your prompt.