The CloudRadial AutomationAI SuperOps extension lets a workflow or agent work with your SuperOps RMM and PSA data: list and read clients, assets, alerts, tickets, tasks, and technicians, and open new tickets or clients. This article covers what the extension can do, the API token and secrets it needs, why every call requires approval, and the skills that ship with it. It is for workspace users who build automations (Admin or Owner Role).
- What the Extension Covers
- Finding Your SuperOps Credentials
- Providing the Credentials to Your Runner
- Every Call Is Approval-Gated
- Skills
- Tips for Working With SuperOps Data
What the Extension Covers
The extension calls the SuperOps MSP GraphQL API and provides 12 tools across these areas:
| Area | What you can automate |
| Clients | List clients (companies), read one client, including its account manager and primary contact, and create a client |
| Assets | List managed assets (devices) and read one asset, including its client and site |
| Alerts | List RMM alerts across your fleet, and list the alerts raised on one asset |
| Tickets | List and read service tickets, and open a new ticket for a client |
| Tasks and technicians | List tasks and list technicians, for example to find a technician for assignment or reporting |
Install it from Extensions like any other catalog extension. See Browsing and installing extensions for the general install flow.
Finding Your SuperOps Credentials
The extension signs in with a SuperOps API token and identifies your account with your MSP subdomain:
- API token: in SuperOps, go to Settings > My Profile > API Token and select Generate Token. Copy the token.
- Subdomain: in SuperOps, go to Settings > My MSP > MSP Information. Your subdomain is the short host label, for example
acmeforacme.superops.ai.
Providing the Credentials to Your Runner
Store three secrets in your runner's Key Vault with these exact names:
| Secret | Value |
SuperOps-ApiUrl |
The API address for your SuperOps data center: https://api.superops.ai/msp (US) or https://euapi.superops.ai/msp (EU). Include the /msp ending. |
SuperOps-ApiToken |
The API token you generated in SuperOps |
SuperOps-SubDomain |
Your MSP subdomain, for example acme |
For how to add these, see Accessing and updating your runner's Key Vault. The agent reads the credentials from the runner and never asks you for them. If you work in a separate SuperOps account for a client, see Managing companies and per-company credentials.
Every Call Is Approval-Gated
SuperOps exposes a GraphQL API, where every request carries its query text in the request body. AutomationAI cannot guarantee that a tool meant to read sends only a read, so all 12 SuperOps tools are approval-gated, including the ones that only list or read data. Each call pauses the run, and the request appears as an Action Required item in the Inbox until someone approves it. See Handling Action Required items in the Inbox.
| Tool behavior | Tools |
| Approval-gated, and changes SuperOps data | Create a ticket; create a client |
| Approval-gated, reads only | List and read clients, assets, alerts, and tickets; list tasks; list technicians |
There are no unattended SuperOps calls. Plan for this when you build a workflow: an agent that looks up a client and then opens a ticket waits for approval at each step. The extension has no update or delete tools.
Skills
The extension ships four skills that guide an agent through common SuperOps tasks. Every step in each skill is approval-gated.
| Skill | Use it to |
| Look up clients & assets | Find a client (company) or a managed asset, resolve its id, or read its details |
| Investigate alerts | Review open or recent RMM alerts across your fleet, or pull the alerts raised on one asset |
| Manage tickets | Find or read service tickets, or open a new ticket for a client |
| Run reports | Compile counts or rollups across clients, assets, tickets, tasks, and technicians |
Tips for Working With SuperOps Data
- Refer to clients by name. Before it opens a ticket, the agent finds the client's id from the client list.
- SuperOps can return a successful response that still contains errors. The agent checks every response for errors, treats any error as a failed call, and reports the messages as SuperOps returned them. It does not report a ticket or client as created when SuperOps returned an error.
- Lists come back a page at a time, with a page number and page size, and can be sorted and filtered
- Times from SuperOps are in UTC
- If every call fails, check that
SuperOps-ApiUrlmatches your data center and ends in/msp, and thatSuperOps-SubDomainis the short label only, not the full host name
If you are still having trouble, we’re here to help! Submit a ticket here for assistance, and don’t forget to check our status page to ensure there are no outages in your area.
Comments
0 comments
Please sign in to leave a comment.