TIBCO Scribe® Online Connector For GoToWebinar

Use the GoToWebinar Connector to create GoToWebinar® source or target Connections in Integration Solutions. You can use this Connector to integrate GoToWebinar data into Dynamics CRM, Salesforce, or other reporting systems.

Connector Specifications

This Connector supports GoToWebinar API version 2.0.

  Supported

Agent Types

On Premise X
Cloud X

Replication Services

Source  
Target  

Integration Services

Source X
Target X

Migration Services

Source  
Target  

Maps

Integration X
Request-Reply  
Message  

Note:  This Connector is available from the TIBCO Scribe® Online Marketplace. See Marketplace TIBCO Scribe® Certified Connectors for more information.

Supported Entities

The GoToWebinar Connector supports the following entities. Select a linked entity name for additional information when using that entity in TIBCO Scribe® Online.

Entity Query Create Update Delete Upsert

Attendee

X

 

 

 

 

AttendeePollAnswer

X

 

 

 

 

AttendeeQuestion

X

 

 

 

 

AttendeeRollup

X

 

 

 

 

AttendeeSurveyAnswer

X

 

 

 

 

Registrant

X

X

 

X

 

Session

X

 

 

 

 

SessionPoll

X

 

 

 

 

SessionSurvey

X

 

 

 

 

UpcomingWebinar

X

 

 

 

 

Webinar

X

X

X

X

 

Setup Considerations

To use the GoToWebinar Connector, you need a GoToWebinar organizer account. For more information, see the GoToWebinar product website.

OAuth Token Expiration

OAuth tokens associated with GoToWebinar OAuth Connections expire over time. The OAuth token associated with a Connection is validated each time a Solution using the Connection is executed. If the token has expired, a new OAuth token is generated and then the Solution executes. In rare cases, one Solution could successfully validate the OAuth token and before that Solution completes, the token expires. A second Solution using the same Connection would generate a new token for the Connection, causing the first Solution to fail with a 403 Forbidden error indicating that the token is no longer valid. In this scenario, the failed Solution must be executed again. On the second execution, the new token is used and the Solution executes successfully.

If you are consistently seeing errors, you may need to generate a new OAuth token manually by opening the GoToWebinar Connection dialog in TIBCO Scribe® Online and re-authenticating using the Authenticate button. Selecting the Test button is not necessary, just select OK to save and close the Connection dialog.

Note: If the Test button is used, a 403 Forbidden error may display when you select OK on the Connection dialog. Disregard the error by selecting Cancel. The new OAuth token should have been generated by the re-authentication process.

If the new OAuth token was not successfully generated, you may see additional 403 Forbidden errors when attempting to use the Connection. If this occurs, configure a new GoToWebinar Connection and assign that new Connection to any Maps that require access to GoToWebinar.

Selecting An Agent Type For GoToWebinar

Refer to TIBCO Scribe® Online Agents for information on available Agent types and how to select the best Agent for your Solution.

Connecting To GoToWebinar

Note: Best practice is to create Connections with credentials that limit permissions in the target system, following the principle of least privilege. Using Administrator level credentials in a Connection provides Administrator level access to the target system for TIBCO Scribe® Online users. Depending on the entities supported, a TIBCO Scribe® Online user could alter user accounts in the target system.

  1. Select More > Connections from the menu.
  2. From the Connections page select Add to open the Add a New Connection dialog.
  3. Select the Connector from the drop-down list in the Connection Type field, and then enter the following information for this Connection:
    • Name — This can be any meaningful name, up to 25 characters.
    • Alias — An alias for this Connection name. The alias is generated from the Connection name, and can be up to 25 characters. The Connection alias can include letters, numbers, and underscores. Spaces and special characters are not accepted. You can change the alias. For more information, see Connection Alias.
  4. Select Authenticate to open the GoToWebinar secure login page.
  5. Enter your GoToWebinar login information and click Continue. Follow any instructions to allow the GoToWebinar Connector to access your GoToWebinar account.
  6. When you are done, the following message displays:

  7. Select Close .

    Tip: Do not test the Connection until the message at the top of the Connection dialog reads Authentication complete. Note that it may take a few minutes for this message to display.

  8. Select Test to ensure that the Agent can connect to GoToWebinar. Be sure to test the Connection against all Agents that use this Connection. See Testing Connections.
  9. Select OK to save the Connection.

Retry Logic

Note: The GoToWebinar Connector governs its throughput to help avoid rate limiting errors when accessing the GoToWebinar API. This may result in poor performance when the Connector is used during periods of high API traffic.

The Connector waits a second after every call, regardless of success or failure. If the call has a rate limit failure, the Connector waits up to an additional five seconds before retrying. With each successive rate limit failure, the wait time is increased up to an additional 20 seconds. Only after 15 successive rate limit failures will the connector return an error and fail the row.

GoToWebinar Connector As IS Source

Consider the following when using the GoToWebinar Connector as an IS source.

GoToWebinar Connector As IS Target

Consider the following when using the GoToWebinar Connector as an IS target.

Notes On Standard Entities

Attendee

AttendeePollAnswer

AttendeeQuestion

AttendeeRollup

AttendeeSurveyAnswer

Registrant

Query

Create

In GoToWebinar, a Registrant is a person who has registered for an upcoming Webinar. The GoToWebinar Connector allows you to add records in the Registrant entity from a source using the Create operation.

Note: You cannot create Registrants in a past webinar.

The following fields are required to create a Registrant:

Note: Use the GoToWebinar Connector to access Registrants by running the Solution before the webinar occurs. After a webinar is finished, the Registrant data becomes Attendee data.

Delete

Session

SessionPerformance

SessionPoll

SessionSurvey

UpcomingWebinar

Webinar

Query

Create

A Webinar record can be one of three types, single_session, sequence, or series. The series type is not supported by this Connector. There is no specific field for Webinar type, instead GoToWebinar determines the type based on the fields that are configured in the Webinar record. To set the Webinar type, map the following fields in the Fields tab of the Create Block:

Note: When a Webinar is created, GoToWebinar generates a WebinarKey. That key is required when adding Registrants to the Webinar.

Delete

Update

Note: Updating sequence type webinars is not supported by the Connector. Attempting to update a sequence type webinar causes associated sessions to be lost and the webinar to become a single session webinar. Use the GoToWebinar application to update sequence type webinars.

TIBCO Scribe® Online API Considerations

Note: Connectors using OAuth for authentication are not fully supported by the TIBCO Scribe® Online API at this time.

License Agreement

The TIBCO Scribe® Online End User License Agreement for the GoToWebinar Connector describes TIBCO and your legal obligations and requirements. TIBCO suggests that you read the End User License Agreement.

More Information

For additional information on this Connector, refer to the Knowledge Base and Discussions in the TIBCO Community.