The WorkLink CMS allows WorkLink CMS Administrators and Analysts to manage Webhooks and Integrations under the Developer Tools Menu.

 

Webhooks

Webhooks allow integrators to build Applications that execute after specific events occur in the Scopear.com ecosystem.

For example, a Scope Customer might leverage a webhook to trigger a custom action that imports ScenarioSession data into the Customer’s system of record whenever a User completes a session in the Scope Worklink App.

 

Requirements

• Your organization must be an active Scope customer.
• Your organization must have provisioned at least one admin User account.

 

Use Cases

Common webhook use cases include the following:

• Collecting data for data-warehousing
• Sending notifications to IM clients and pagers (e.g. when new Scenarios become available)
• Updating state in a system-of-record (e.g. when users complete Scope Scenarios)

See Orchestrating Common Use Cases to see a visualization of webhooks used in connection with other services and components.

 

For more information about Webhooks and how to create one, please refer to: Using Scope AR Webhooks.

 

 

Integrations

 

WorkLink Scenario Integration

The WorkLink platform allows customers to integrate a wide variety of third-party systems to ensure that the operations completed within the WorkLink AR are known are recorded by other systems of record. This could be an MES, CMMS, LMS, or other systems.

There are two main approaches to this integration and which solution you choose will depend on the amount of business logic that needs to occur on that data before storing it in your third-party system: Using Built in Integrations and Using a Middleware App.

For more information: Scenario Integration with Third-Party Systems

 

WorkLink Call Integration

The WorkLink platform allows customers to integrate a wide variety of third-party systems to ensure that the calls made within the WorkLink AR are known are recorded by other systems of record. This could be an MES, CMMS, LMS, or other systems.

There are two main approaches to this integration and which solution you choose will depend on the amount of business logic that needs to occur on that data before storing it in your third-party system: Using Built in Integrations and Using a Middleware App.

 

For more information: Call Integration with Third-Party Systems