Skip to main content
Once you’ve created an API secret in ScreenConnect, connect it to Neo Agent through the integrations dashboard.
You’ll need your instance URL and the RESTful API Manager authentication secret to complete this setup.

​
Required Information

​
string
required
Your ScreenConnect instance URL, e.g. https://yourcompany.screenconnect.com. Enter just the host — the API path is appended automatically.
​
string
required
The RESTful Authentication Secret from the RESTful API Manager extension.
ScreenConnect authenticates with a single secret — there is no separate client ID, so the Neo form only asks for the URL and the Client Secret.

​
Configuring the Integration

1

Access the Neo Agent Dashboard

Navigate to the Neo Agent Dashboard and log in.
2

Navigate to RMM Integrations

From the dashboard:
  1. Click Integrations in the left sidebar
  2. Select the RMM category
  3. Find and select ConnectWise ScreenConnect from the list of available RMM integrations
Neo Agent Integrations page showing the RMM category with the ConnectWise ScreenConnect tile

Neo Agent integrations page with the RMM category and the ConnectWise ScreenConnect tile

3

Enter Your Credentials

Complete the ConnectWise ScreenConnect integration setup form:
  1. RMM URL: Enter your instance URL (e.g. https://yourcompany.screenconnect.com)
  2. RMM Client Secret: Enter your RESTful Authentication Secret
Neo Agent ConnectWise ScreenConnect setup form showing the RMM URL and RMM Client Secret fields

ConnectWise ScreenConnect integration setup form

Double-check both values for accuracy. An incorrect URL or secret will prevent Neo Agent from connecting to your ScreenConnect instance.
4

Submit Configuration

Click Submit. Neo Agent validates the secret against your instance and establishes the connection.
A successful connection confirms Neo Agent can reach your ScreenConnect instance with the provided secret.

​
Troubleshooting Connection Issues

  • Verify the authentication secret is correct and copied without extra spaces
  • Confirm the RESTful API Manager extension is installed and enabled
  • Check that the secret hasn’t been rotated in the extension settings since you copied it
  • Confirm the instance URL is correct (just the host, e.g. https://yourcompany.screenconnect.com)
A 404 means the request reached your ScreenConnect instance but never reached the RESTful API Manager, so the secret was never checked. There are two causes:
  • The RESTful API Manager extension is not installed (or is disabled) on the instance — see Creating the Secret
  • The instance URL is wrong — enter only the host, e.g. https://yourcompany.screenconnect.com, with no path
If this happens after the integration is already connected, Neo posts an Action Required message to your Inbox and emails your admins, then retries on the next device sync. Once the extension is installed or the URL is corrected, the next sync succeeds and no new message is posted — mark the existing message as read in your Inbox to clear it.
  • Wait a few minutes for the initial sync to complete after connecting
  • Confirm the instance has installed (access) agents — Neo reads ScreenConnect Access sessions as devices

​
Configuring Permission Groups

Once connected, open Agent Settings → Permission Groups to choose what the agent may do in ScreenConnect. Each group can be Disabled, Read-only, or Read & Write:
ScreenConnect commands run as SYSTEM (Windows) or root (macOS/Linux). Enable Require approval on the Commands group to gate every command behind a technician before it runs.

​
What’s Next?

With ScreenConnect connected, Neo can:
  • Device lookup — pull session status, OS, and last-contact time while triaging tickets
  • Company mapping — associate sessions with the right PSA company by name
  • Remote action — run a command or Toolbox item and message the end user, where you’ve granted write access