|SharpSpring enables you to integrate your GoToWebinar account to use SharpSpring forms to collect information on live webinar attendees.
Dynamic forms pass first name, last name, and email address information to GoToWebinar.
This article will detail how to integrate GoToWebinar with SharpSpring.
Adding a GoToWebinar App
You must have a GoToWebinar license before proceeding with this integration.
To obtain GoToWebinar information and add a new app to GoToWebinar, do the following:
- Log in to GoToWebinar's developer web page.
- In the top toolbar, click My Apps.
- Click Add a new App.
- In the App Name field, enter SharpSpring.
- In the Description field, enter SharpSpring
- In the Product API field, enter GoToWebinar.
- In the Application URL field, enter the following URL:
- In the entered URL, replace YourCompanyDomain
with the domain you are using with SharpSpring.
For example, if Franco's Franks, Inc. is using
SharpSpring, their domain may be as follows:
- Click Create App.
Be aware that the integration will not work unless the application URL is correct.
Obtaining GoToWebinar API Keys
To obtain the necessary GoToWebinar API Key, do the following:
To integrate GoToWebinar with SharpSpring, do the following:
Once integrated, it may take a few hours for the status to change from Pending to Connected.
Note: This account information should match the account for which you are setting up the webinar, and not the developer account.
Creating GoToWebinar Forms
After integrating GoToWebinar with SharpSpring, you need to add the GoToWebinar field to a SharpSpring form to gather information on attendees. When a visitor finishes filling out the form, they will be registered for the associated webinar.
To create a connected form for GoToWebinar, do the following:
Important: SharpSpring only displays live webinars. Recorded webinars are not currently supported.
Note: Do not make the GoToWebinar field hidden.
Once a form is created, be aware that changes to existing webinar names in GoToWebinar will require re-saving the form in SharpSpring to reflect the changes in the live version of the form.