We often get questions regarding integrating ScreenConnect with other products— such as ticketing systems, RMM, MSP, etcetera. Integrations can be useful as they can provide a means to instantaneously launch remote support sessions or connect to unattended systems from within an application. There are two primary methods of standard integration with ScreenConnect, link creation and pass parameters, and a third less common process of running scripts.
The most common means of integration launches other products or connects to the web application via an active link. This process designates a specific URL for each machine. For example, in the past LogMeIn Free allowed customers to connect to their unattended clients via a LogMeIn free link within Labtech (Desktop Shortcut). The user could click the link from the Labtech application and quickly navigate to the desired machine. We learned just recently LogMeIn restricted access to their Desktop Shortcut feature for Labtech (and possibly other third-party applications). Users clicking on the link would be taken to a page that talks about Desktop Shortcuts and that the feature is now part of LogMeIn Pro-only. ScreenConnect can be setup in a similar fashion, by putting in your link/folder name/computer name into the Labtech application. Then from within the Labtech application you can jump straight to the desired machine in your ScreenConnect folder. Many tools enable this functionality.
Notice the URL in the picture below, the URL displays the path to the machine inside your ScreenConnect installation. The "live.teekie.com" would be the path to your ScreenConnect installation, "Host#TeekieComputer" is the folder, and the "/dublin" is the computer name in the folder. **Now that we have shown the name teekie as a URL path we know everyone is going to go out and register that subdomain tomorrow!
Another popular method allows software to pass parameters. This allows you to use a generic URL as opposed to a specific URL for each system. Here, you only have to put a single link, such as https://support.my.company.com/Parameter1/Parameter2. You then define each parameter within that link. For example, Parameter 1 is the “$Customer" or "$Folder Name” and Parameter2 is the “$ComputerName”. Passing variables like this is a fairly common practice and many of the big solutions provide easy setup. We are currently investigating applications to see whether they have the means to integrate with ScreenConnect by way of this method.
The final method is a bit more complex as it requires specific collaboration with the other party. For this, the tool provides integration by way of a button or link that runs a script that calls into ScreenConnect’s API. This can be beneficial as it can provide more functionality. An example is that you can automatically launch and create sessions to bypass a web application altogether. While we don’t currently have any integrations available using this method we do see this as a powerful alternative that we hope to explore in the future.