Skip to main content
Connect Syncro with an API token that uses Custom Permissions. MSPilot uses it to list customers and assets, then sync those into your clients. It does not create, update, or delete records in Syncro. You need a Syncro administrator who can create API tokens.

​
Create an API token in Syncro

  1. In Syncro, go to Admin → API - API Tokens.
  2. Click New Token.
  3. Open the Custom Permissions tab. Don’t stay on App Integration. Those tokens are prebuilt for other apps and grant more than MSPilot needs.
    New Token page in Syncro, with Custom Permissions selected and Name set to MSPilot Access.
  4. Enter a Name you’ll recognize later, such as MSPilot Access. You can leave Expiration blank.
  5. Enable only:
    • Assets - List/Search
    • Customers - List/Search
  6. Leave every other permission off.
  7. Create the token and copy it to a password manager. Syncro typically won’t show it again.

​
Connect Syncro

  1. In MSPilot, open Integrations and choose Syncro.
  2. Enter Subdomain. For https://your-subdomain.syncromsp.com, enter your-subdomain. Don’t include https://, and don’t include .syncromsp.com. The form also accepts the full hostname.
  3. Paste the token into API token.
  4. Click Connect Syncro.
    Syncro connection panel in MSPilot, with the API token field and Connect Syncro.

​
After you connect

MSPilot starts syncing customers and devices from Syncro.
  • If you skipped a PSA, Syncro customers are imported as clients first. Devices then land in those clients.
  • If clients already came from a PSA, map each client to the Syncro customer that owns its endpoint inventory.
Each Syncro customer can map to only one client. Assets without a mapped customer, or without a Syncro agent installed, are skipped. On the client, use Syncro mapping to bind the customer, then Refresh devices when you want that client’s inventory updated immediately.

​
Install the agent

Connecting syncs devices. It does not install the agent.

​
Windows

On the client, open Deployment. Under AI applications, tick the apps to install, then choose Copy script (mspilot-deploy.ps1). The copy is a short launcher: replace any older MSPilot script saved in Syncro once. In Syncro, save it as MSPilot install and enroll, run as System, with Max Script Run Time set to 90 minutes. Open Assets & RMM, select the Windows devices, and run it. When Claude Desktop is included, keep a user signed in during the run, and restart Windows if the job reports reboot_required=true. You do not schedule a pull job; the agent schedules its own. Details are on Install.

​
macOS

On the client, open Deployment, pick macOS, and choose Copy script. In Syncro, create a new script. Only change these fields: Save the script. Open Assets & RMM, select the Apple Silicon Macs (macOS 12 or later), and run it. It runs as root, so nobody needs to be signed in. The signed-in user’s AI apps are configured right away; other users at their next sign-in, then every 3 minutes. You can schedule the same script daily; running it again is a safe repair. You do not schedule a pull job in your RMM; the agent runs its own config pull for each user at sign-in and every 3 minutes. What success and each exit code look like: macOS.
Last modified on October 5, 2026