Skip to content
Integrations & Connectors

SuperOps integration

Last updated: 10/9/2026

SuperOps integration

What it does

The SuperOps integration connects your xClause account to your SuperOps MSP account with an API token.

  • Imports SuperOps clients into xClause. You choose which SuperOps clients become xClause clients, and which of their contacts become client users, from the Manage drawer on the integration card.
  • Refreshes data for clients you have already imported. Sync now reads managed devices (SuperOps assets), and optionally sites, for each SuperOps client that already exists in xClause. It also refreshes the contacts you chose to import.
  • Shows imported devices on the client's Managed Assets page, and imported sites on the client's Sites tab.
  • Pushes device changes back to SuperOps. When you add, edit, or delete a managed endpoint on a client's Managed Assets page, xClause tries to make the same change in SuperOps (see the limits below).
  • Offers device counts as a source when you import line items into a SOW. This is read-only and is off until you turn on SuperOps as a source under your SOW integration settings.

Sync now never creates new xClause clients on its own. A SuperOps client only becomes an xClause client when you select it in Manage.

Before you start

In xClause

  • The Integrations settings page is not available on the MSP Starter plan unless your account has been given integrations access. If you are on that plan, opening Settings > Integrations sends you to the billing page with an upgrade prompt.
  • You must be signed in as a user who belongs to your MSP company. The connect action checks company membership only. It does not check for an admin role.

In SuperOps

  • A SuperOps MSP account, and an API token for it.
  • Your SuperOps subdomain.
  • Know whether your SuperOps account is in the US or the EU data center.
  • The API token must be allowed to read the areas in the permissions table below. To use device write-back, it must also be allowed to create, update, and delete devices. xClause does not request scopes. Access is whatever the token holder has in SuperOps.

Connect

SuperOps lives under Settings > Integrations, on the SuperOps tile (category PSA & RMM).

  1. In SuperOps, go to Settings > Profile Information > API Token. Click Generate Token, or copy the existing token.

  2. In SuperOps, go to Settings > MSP Information to find your subdomain.

  3. In xClause, open Settings > Integrations and open the SuperOps tile.

  4. Click Connect to SuperOps.

  5. Fill in the fields:

    FieldWhat to enter
    API Token (required)The token from step 1.
    Subdomain (required)Your subdomain, for example your-company. xClause shows .superops.ai next to the field.
    Data CenterUS (api.superops.ai) or EU (euapi.superops.ai). The default is US.
  6. Click Connect. xClause saves the details, then makes a test call to SuperOps. On success you see SuperOps connected and the card shows the subdomain, data center, Total Clients, Connected Since, Last Synced, and Data sync.

To change the token, subdomain, or data center later, click Update connection on the card and submit the form again.

To choose what to import:

  1. On the connected card, find the Clients & users section and click Manage.
  2. Optional: turn on Keep picked clients' contacts updated on each SuperOps sync if you want new contacts imported automatically on later syncs. The list of SuperOps orgs shows either way, and nothing is imported until you pick it.
  3. Expand a SuperOps client. Tick Import this org as a client.
  4. For its contacts, choose Import everyone, select individual people, or choose no users. A contact whose email already belongs to a non-client xClause account is shown as locked and is not imported.
  5. Click Save.

Permissions the API account needs

xClause sends every request to SuperOps as an HTTPS POST to the GraphQL API, using your token as a Bearer token and your subdomain in the CustomerSubDomain header. The "Read or write" column below describes the GraphQL operation, not the HTTP verb.

SuperOps areaWhat xClause does thereRead or write
Clients (getClientList)Tests the connection, lists clients for Manage, reads names and account IDs during Sync now, counts clients for Total Clients, and lists clients for the SOW device-count import.Read
Client users (getClientUserList)Reads each client's contacts (name, email, user ID) for the Manage drawer and for Sync now.Read
Assets (getAssetList)Reads managed devices (name, class, serial number, manufacturer, model, host name, public IP, MAC, platform, status, last communicated time). Used by Sync now and the SOW device-count import.Read
Client sites (getClientSiteList)Reads each client's sites (name, address lines, city, state, postal code, country, contact number, time zone). Used by Sync now when Sync sites from SuperOps is on.Read
Tickets (getTicketList, IT API)Used only as a fallback to test the connection if the MSP API test does not succeed. xClause does not import tickets.Read
Devices (createClientDevice, updateClientDevice, deleteClientDevice)Creates, updates, or deletes a device in SuperOps when you add, edit, or delete a managed endpoint on a client's Managed Assets page.Read and write

Only the last row writes. If you do not want xClause to change anything in SuperOps, use a token that cannot create, update, or delete devices. Imports and Sync now will still work. Device changes you make in xClause will then not reach SuperOps.

What syncs, and which direction

DataDirectionTrigger
ClientsSuperOps to xClauseYou select a client in Manage and click Save. xClause creates the client, or updates it if a client with the same SuperOps account ID, or the same name under your MSP, already exists. Sync now does not create clients.
Client users (contacts)SuperOps to xClauseSync now reads each imported client's contacts and imports the ones you selected in Manage. Imported users are contact records. You can invite them to the portal from Manage.
Managed devicesSuperOps to xClauseSync now, for clients already imported. Devices are matched by SuperOps device ID, then by name within the client. This is not controlled by a switch.
SitesSuperOps to xClauseSync now, only when Sync sites from SuperOps is on, for clients already imported.
Managed endpoints (add, edit, delete)xClause to SuperOpsSaving a change on the Managed Assets page. Add requires the client to have been imported from SuperOps. Edit and delete require that the endpoint came from, or was already pushed to, SuperOps.

There is no scheduled SuperOps sync. Data refreshes only when you click Sync now.

The integration settings on the card:

SettingWhat it does
Sync contacts from SuperOpsSaved with your settings. Importing client users is actually controlled by the Manage switch and selections, not by this toggle.
Sync clients from SuperOpsSaved with your settings. Client import is actually done in Manage.
Sync sites from SuperOpsControls whether Sync now reads sites.

If both Sync contacts from SuperOps and Sync clients from SuperOps are off, Sync now does nothing.

When Sync now finishes you see a summary such as Sync completed: 2 endpoints created, 1 sites updated, or Sync completed - no changes needed.

Limits to know about:

  • Edits you make in xClause to a client's name or contacts are not sent to SuperOps. Only managed-endpoint add, edit, and delete are pushed.
  • xClause reads in pages of 100. The device read gets one list of assets from SuperOps and then filters it to each client. On a SuperOps account with many assets, some devices may not appear.
  • Device push to SuperOps runs in the background after you save. If SuperOps rejects the change, xClause still saves it and does not tell you.
  • Total Clients is counted from the first 100 clients only.

Troubleshooting

What you seeWhat it means and what to do
Please provide both API token and subdomainBoth fields are required. Fill them in and click Connect again.
Failed to connect to SuperOps. Please check your credentials.SuperOps did not accept the token, subdomain, or data center. Check all three. Make sure the data center matches where your account lives. The details you entered are saved and Data sync shows Disabled until a connection works. Click Update connection and try again.
SuperOps credentials are incomplete (badge: Credentials incomplete)The saved token or subdomain is missing. Click Update connection and re-enter your API token.
SuperOps is not responding (badge: Not responding)xClause could not get a working answer. This can be a revoked token or a SuperOps outage, and xClause cannot tell which. Nothing was disconnected. Click Check again. If it keeps failing, click Update connection and enter a fresh token.
We could not reach SuperOps just now (badge: Status unknown)The check ran out of time. Your connection is still saved. Click Check again in a moment.
We couldn't load your SuperOps connection status.xClause could not read the status. This does not mean you are disconnected. Click Try again.
SuperOps not connectedYou clicked Sync now but no connection is saved. Connect first.
Failed to connect to SuperOps. Please check your connection.Sync now ran a test call first and it failed. Use the steps for SuperOps is not responding.
Failed to sync with SuperOpsA server-side error during sync. Try again. If it repeats, contact support.
Sync completed with N errors. Check console for details.The sync finished but some items failed. The details are in your browser's developer console. Typical messages: Endpoint sync skipped for <client>: API not supported, Site sync skipped for <client>: API not supported, Failed to sync <client>: ..., and No MSP user found for endpoint <name>.
We couldn't save your sync settings. Check your connection and try again.The toggle did not save and has reverted. Try again.
Could not list orgs or Could not import the org — check the connection.The Manage drawer could not read clients from SuperOps. Click Refresh in the drawer, or check the connection status on the card.
Devices missing after Sync nowThe client must already be imported through Manage. Devices are not synced for clients that are not imported. See also the device paging limit above.

Disconnecting

  1. On the SuperOps card, click Disconnect.
  2. Confirm the prompt: Are you sure you want to disconnect from SuperOps? This will remove all integration settings.

xClause deletes the saved SuperOps connection, which includes your API token, subdomain, data center, and sync settings. xClause stops reading from and writing to SuperOps.

The disconnect action removes only that connection record. It does not delete the clients, contacts, devices, or sites already imported into xClause, and it does not change anything in SuperOps. To connect again, use Connect to SuperOps and enter the token again.

Start running your contracts the modern way.

Build, send, e-sign, and manage every MSA and SOW in one platform. Start today, no demo required.

Free trial • Cancel anytime • No long-term contract