GoToWebinar

Navigate to developer.goto.com and sign in with your GoToWebinar account. Click 'My Apps' in the top navigation, then click 'Create an app'. Fill in the application name (e.g., 'My Bubble App'), a description, and select the product 'GoToWebinar' from the available products list. The most critical field here is the Redirect URI — this must be set to your Bubble callback page URL. Use the format: https://yourapp.bubbleapps.io/oauth-callback (or your custom domain if configured). If you have not yet created the callback page in Bubble, create a new page called 'oauth-callback' now, then come back and enter this URL. The redirect URI must match EXACTLY — including whether or not there is a trailing slash — what your Bubble app will send during the OAuth flow. After saving the app, copy the Client ID and Client Secret. Store the Client Secret securely — you will put it in your Bubble API Connector marked as Private. Also note that the Authorization URL for GoToWebinar is: https://authentication.logmeininc.com/oauth/authorize And the Token URL is: https://oauth.getgo.com/oauth/v2/token Before testing, confirm that your GoToWebinar account has the correct permissions. If the account is a plain user account rather than an organizer/host account, webinar creation and management calls will fail with permission errors. The integration works with any GoToWebinar paid plan where the account has organizer rights.

Open your Bubble app editor and click the Plugins tab. Install the API Connector plugin if not already present. Click 'API Connector' to open the configuration panel. Click 'Add another API' and name this group 'GoToWebinar OAuth'. Do not add any shared headers to this group — authorization varies by call. Add your first call named 'Exchange Code for Token'. Set method to POST and URL to https://oauth.getgo.com/oauth/v2/token. Set 'Use as' to 'Action'. For the body parameters, add: - grant_type: 'authorization_code' (static text) - code: '[code]' (dynamic — the code that arrives in the callback page URL) - client_id: your actual client_id (static — not secret, but you can also make it dynamic) - client_secret: '[client_secret]' (dynamic, mark as Private — or put your actual secret here and mark the field Private) - redirect_uri: 'https://yourapp.bubbleapps.io/oauth-callback' (static, must match exactly what is registered) Add a second call named 'Refresh Token'. Method POST, same URL, body: - grant_type: 'refresh_token' (static) - refresh_token: '[refresh_token]' (dynamic, mark Private) - client_id: your client_id - client_secret: '[client_secret]' (dynamic, Private) For the Initialize call on 'Exchange Code for Token': you need a real OAuth code, which you can only get by completing an actual OAuth flow. Skip initialization for now — we will complete it after building the callback page. This means Bubble will not have auto-detected response fields yet, but you can manually define them by adding the expected fields (access_token, refresh_token, token_type, expires_in, organizer_key) as text parameters in the response detection area.

1{
2  "call_name": "Exchange Code for Token",
3  "method": "POST",
4  "url": "https://oauth.getgo.com/oauth/v2/token",
5  "body": {
6    "grant_type": "authorization_code",
7    "code": "<code -- dynamic>",
8    "client_id": "<your_client_id>",
9    "client_secret": "<your_client_secret -- PRIVATE>",
10    "redirect_uri": "https://yourapp.bubbleapps.io/oauth-callback"
11  }
12}

Now build the two Bubble UI elements that drive the OAuth flow: an authorization button on your settings page, and a workflow on the callback page that processes the code. For the authorization button: create a button labeled 'Connect GoToWebinar Account' on your admin or settings page. In its workflow, add the action 'Go to external website' (or 'Open an external website in a new tab'). Set the URL to the following constructed string — you must build this as a Bubble dynamic expression: https://authentication.logmeininc.com/oauth/authorize?client_id=YOUR_CLIENT_ID&response_type=code&redirect_uri=https://yourapp.bubbleapps.io/oauth-callback Replace YOUR_CLIENT_ID with your actual client ID. You can store this as an app-level text option or hardcode it in the URL expression (the client_id is not secret). For the callback page: in your Bubble editor, open the 'oauth-callback' page. Add a Page Loaded workflow (from the Workflow tab, add an Event → 'Page is loaded'). In this workflow: Step 1: Call the 'Exchange Code for Token' API action. For the 'code' parameter, use the expression: 'Get data from page URL → key: code'. This reads the ?code= value that GoToWebinar appends to your callback URL. Step 2: Save the results to the current user's fields. Add a 'Make changes to current user' action. Set: - access_token = Result of Step 1's access_token - refresh_token = Result of Step 1's refresh_token - organizer_key = Result of Step 1's organizer_key - token_expiry = Current date/time + 3550 seconds (just under 1 hour as a safety buffer) Step 3: Navigate the user back to your main admin page. To test this: click the 'Connect GoToWebinar Account' button in your Bubble app preview, complete the GoToWebinar login, and confirm you land back on your Bubble callback page. Then check your User record in Bubble's Data tab — all four fields should be populated. If the exchange fails, check that the redirect_uri in the API call body exactly matches what is registered in the GoTo Developer portal (trailing slash matters).

Now add the functional API calls that your app will use. Add a second API group named 'GoToWebinar API'. Add a shared header: Authorization: Bearer [access_token] — mark as 'Private' and set as Dynamic. This token value will come from the current user's access_token field at runtime. Add the following calls: Call 1 — List Webinars: method GET, URL https://api.getgo.com/G2W/rest/v2/organizers/[organizer_key]/webinars, 'Use as' Data. The [organizer_key] parameter is dynamic. Call 2 — Register Attendee: method POST, URL https://api.getgo.com/G2W/rest/v2/organizers/[organizer_key]/webinars/[webinarKey]/registrants, 'Use as' Action. Body: { 'firstName': '[first_name]', 'lastName': '[last_name]', 'email': '[email]' }. The response includes 'joinUrl' — the most important field to detect. Call 3 — Create Webinar (optional, for organizer dashboards): method POST, URL https://api.getgo.com/G2W/rest/v2/organizers/[organizer_key]/webinars, 'Use as' Action. Body: { 'subject': '[title]', 'times': [{ 'startTime': '[start_iso8601]', 'endTime': '[end_iso8601]' }] }. For Initialize on each call: you need the authenticated user's real organizer_key and access_token. After completing Step 3 (OAuth flow), you will have these values. Use a test webinarKey from an existing webinar in your GoToWebinar account (visible in GoToWebinar's dashboard). For the Register Attendee call, provide real test values including a valid email address — GoToWebinar will actually attempt to send a confirmation email, so use a personal test email. The dates for Create Webinar must be in ISO 8601 UTC format with milliseconds: '2026-07-15T14:00:00.000Z'. Bubble does not produce this format natively — use a text expression with the date formatted as 'YYYY-MM-DDTHH:mm:ss.000Z'.

1{
2  "api_group": "GoToWebinar API",
3  "shared_headers": {
4    "Authorization": "Bearer <access_token -- PRIVATE, DYNAMIC>"
5  },
6  "calls": [
7    {
8      "name": "List Webinars",
9      "method": "GET",
10      "url": "https://api.getgo.com/G2W/rest/v2/organizers/[organizer_key]/webinars",
11      "use_as": "Data"
12    },
13    {
14      "name": "Register Attendee",
15      "method": "POST",
16      "url": "https://api.getgo.com/G2W/rest/v2/organizers/[organizer_key]/webinars/[webinarKey]/registrants",
17      "use_as": "Action",
18      "body": {
19        "firstName": "<first_name -- dynamic>",
20        "lastName": "<last_name -- dynamic>",
21        "email": "<email -- dynamic>"
22      }
23    }
24  ]
25}

GoToWebinar access tokens expire every hour. Without a refresh mechanism, any user who authorized the integration more than an hour ago will start seeing 401 Unauthorized errors on all API calls. The solution is a scheduled Backend Workflow that runs every 50 minutes (a 10-minute safety buffer) and refreshes tokens for all users whose token_expiry is approaching. First, ensure your app is on Bubble's Starter plan ($32/month or higher) and that Backend Workflows are enabled: Settings → API → toggle 'This app exposes a Workflow API'. Navigate to Backend Workflows in the left panel. Click 'New API workflow' and name it 'refresh-goto-tokens'. Set the workflow to accept no external parameters (it will be triggered on a schedule, not from an external call). Inside the workflow, add these steps: Step 1: Search for Users where token_expiry is less than 'Current date/time + 10 minutes' AND access_token is not empty. This finds all users whose tokens will expire within 10 minutes. Step 2: For each user in the result list (use 'Schedule API workflow for a list' targeting 'refresh-single-user' — a second Backend Workflow you create next), pass the user's refresh_token. Create a second Backend Workflow named 'refresh-single-user' that takes a refresh_token parameter. In this workflow, call the 'Refresh Token' API action with the provided refresh_token and client_secret. Then update the User record: set access_token to the new result, refresh_token to the new refresh_token (GoToWebinar may rotate it), and update token_expiry to Current date/time + 3550 seconds. Finally, schedule 'refresh-goto-tokens' to run every 50 minutes using Bubble's 'Schedule a recurring event' feature. In a Backend Workflow, add action 'Schedule a recurring event' → select 'refresh-goto-tokens' → set frequency to every 50 minutes starting from Current date/time. Trigger this once when you deploy to set the recurring schedule in motion.

With all the pieces in place, build the user-facing registration form and test the complete flow. Create a page with a registration form — at minimum, fields for first name, last name, and email. Add a dropdown or static display of available webinars (use the List Webinars API call, display each webinar's subject and startTime in a Repeating Group or Dropdown, store the selected webinarKey). On the Submit button workflow: Step 1: Call 'Register Attendee' with the current user's organizer_key (from their User record), the selected webinarKey, and the form input values for firstName, lastName, and email. Step 2: Create a new Registrant record in Bubble's database storing the firstName, lastName, email, webinarKey, and joinUrl (from Step 1's result). Step 3: Show an alert or navigate to a confirmation page displaying the joinUrl. Step 4 (optional): Trigger an email workflow to send the joinUrl to the registrant's email. Test with a real email address on a real GoToWebinar session. Log in to your GoToWebinar organizer account and check the webinar's registrant list — the test registrant should appear there. Click the joinUrl returned by Bubble to confirm it loads the GoToWebinar waiting room correctly. For debugging, open Bubble's Logs tab and look for the Register Attendee API call. A successful call shows the full response including joinUrl. A 400 error usually means a malformed request body (check that firstName/lastName/email all have values). A 401 means the access_token has expired — check token_expiry against current time.