Skip to main content
Triggr finds ScreenConnect sessions, updates their custom properties and calls the RESTful API Manager’s other methods, such as sending a command to a session. It needs ScreenConnect 22.3 or later, cloud or on-premises.

​
Set up ScreenConnect

1

Install the RESTful API Manager

Go to Admin > Extensions, click Browse Extension Marketplace, find RESTful API Manager and click Install. If it’s already installed, click Check for Updates.
2

Set the authentication secret

Open the extension’s Options menu and select Edit Settings. Enter a long random string in the Custom field for RESTfulAuthenticationSecret, leave RESTfulAllowedOrigin empty and click Save Settings. Anyone with the secret can send commands to your machines, so store it like an administrator password.
3

Find your hostname

It’s the address you open ScreenConnect at, without https://, such as yourcompany.screenconnect.com. An on-premises server must serve HTTPS at a public address; add the port if it isn’t 443 (support.example.com:8443) and allow Triggr’s IP addresses through any firewall.
See ConnectWise’s RESTful API Manager guide.

​
Connect it in Triggr

1

Open the client's configuration

Go to Integrations > ConnectWise ScreenConnect and click Configure on the client’s row in the Per-Client Configuration card.
The Per-Client Configuration card listing Acme Corp and Globex, each Not Configured with Admin Consent Not Required and a Configure button.
2

Enter the instance details

Enter the Hostname and the secret as Restful Authentication Secret, then click Save Configuration. For an on-premises server with a self-signed or internal certificate, turn on Allow insecure TLS first.
The ConnectWise ScreenConnect configuration window with Hostname and Restful Authentication Secret fields, an Allow insecure TLS switch under Advanced, and a Save Configuration button.
Most MSPs enter the same instance for every client; each row holds its own copy. Per-client integrations never fall back to the Base Configuration, so a client without its own row fails its ScreenConnect steps. The Base Configuration is only for workflows that don’t run for a client.

​
Use ScreenConnect in workflows

  • Set every action’s appExtensionId to 2d558935-686a-4bd0-9991-07539f5fe749, the extension’s ID on every instance.
  • Get Sessions By Filter takes a session group filter, such as CustomProperty1 = 'Contoso'.
  • Make Post Request takes a method name as endpoint, such as SendCommandToSession, and its parameters in order as a JSON array, such as ["<session ID>", "ipconfig"].

​
Troubleshooting

Configure the client on the Per-Client Configuration card, then run the workflow again.
Check the secret matches RESTfulAuthenticationSecret exactly, RESTfulAllowedOrigin is empty and the extension isn’t Inactive. If you changed the secret, update every row.
Hostname must be only the hostname and port, with no https:// or path, served over HTTPS at a public address. For certificate errors, turn on Allow insecure TLS in each row that uses the server.
Check appExtensionId and the endpoint spelling. AddNoteToSession needs version 1.0.6 or later of the extension.