Complete the following steps to enable synchronization of Fonteva Events with GoTo meetings or webinars.
Important: A GoTo account is required to complete this procedure.
Step 1: Create a GoTo Connection in Fonteva
Create a new authentication provider in Webinar Sync to allow the GoTo platform to access your Salesforce org.
Best Practice: Use similar names when creating the Fonteva Webinar Sync connection and the GoTo OAuth app. Doing so will make it easy to discern which GoTo OAuth apps are associated with your Webinar Sync connections.
Go to App Picker > Webinar Sync - Setup.
Select + Add GoTo.
In Connection Name, enter a name for the connection.
Create a new authentication provider.
Select Create New Auth Provider.
Select Update Auth Provider with Client ID & Secret. The Auth. Providers window opens in a new tab.
Return to the Lightning Experience | Salesforce browser tab, then select Save.
Go to the Auth. Providers | Salesforce browser tab.
In the Salesforce Configuration section, copy and paste the Callback URL field value to a text editor. This information is required in the following sections; for reference keep this tab open.
Step 2: Create an OAuth Client in GoTo
Create a GoTo OAuth Client to authorize Fonteva to connect with your GoTo account. OAuth 2.0 is an industry-standard authorization protocol that enables Webinar Sync to obtain requested access to GoTo user accounts.
Go to the GoTo Developer Center and log in with your GoTo credentials.
Select OAuth Clients. The Client Management Portal opens in a new browser tab.
Select Create a client or Create a new client.
On the Details tab of the Create client window:
In Client Name, enter a name for the OAuth client. Use a name similar to the GoTo Connection name created in step 3 of the previous section.
(Optional) In Description, enter information about the OAuth client.
In Redirect URIs, paste the Callback URL copied in step 10 of the previous section, then select + Add.
On the Scopes tab, select the following settings:
GoToMeeting, GoToWebinar, or GoToTraining.
On the Credentials tab:
Copy and paste the Client ID and Client Secret field values to a text editor. These values are required in the next section.
Select I have stored the client secret.
Step 3: Configure the GoTo Connection in Fonteva
The Fonteva GoTo connection and the GoTo OAuth client are now created. As a final step, copy the GoTo information to Fonteva so that the two platforms can communicate.
Configure the Authentication Provider
Go to the Auth. Providers | Salesforce browser tab, then select Edit.
Paste the Client ID and Client Secret values copied in step #8 of the previous section.
In the Consumer Key field, remove the default entry and paste the value from the GoTo OAuth app Client ID field.
In the Consumer Secret field, remove the default entry and paste the value from the GoTo OAuth app Client secret field.
Go to the Lightning Experience | Salesforce browser tab.
If the Meeting & Webinar Setup screen is not displayed, select App Picker > Webinar Sync - Setup.
Select the Named Credentials value. The Named Credentials setup screen opens in a new browser tab.
Select Edit, then select Save. The LogMeIn authentication prompt opens.
Select Allow. The Named Credentials setup screen opens.
Go to the Lightning Experience | Salesforce browser tab, then select Verify & Activate.
Confirm the connection Status updates to Active.
Gather Host IDs
Identify the Host ID for each GoTo account that will need to synchronize Fonteva events. The Host ID is required to add a GoTo user account as a Connection User in Webinar Sync.
Login to GoTo, then select Manage Users.
In the Name column, select the user name. The User Details screen opens and the user’s Host ID displays at the end of the website address.
In the browser address bar, copy the Host ID number at the end of the website address.
Paste the Host ID into a text editor.
Repeat steps 2 - 4 for each GoTo Host account as needed.
Add a Connection User. Now that a Connection exists between Fonteva and GoTo, identify and add the people who need to use the Connection.