The CloudRadial AutomationAI Atera extension lets a workflow or agent work with your Atera RMM and PSA data: look up agents (monitored devices), resolve customers and contacts, triage and manage service tickets, and review monitoring alerts, contracts, billing invoices, and knowledge base articles. This article covers what the extension can do, the API key and secrets it needs, which tools require approval, and the skills that ship with it. It is for workspace users who build automations (Admin or Owner Role).
- What the Extension Covers
- Getting the API Key
- Providing the Credentials to Your Runner
- Reads and Approval-Gated Changes
- Skills
- Tips for Working With Atera
What the Extension Covers
The extension calls the Atera REST API v3 and provides 17 tools across these areas:
| Area | Tools | What you can automate |
| Agents (devices) | 3 | List all agents, list the agents for one customer, and read one agent's detail, such as its OS, machine name, last reboot, and customer |
| Customers | 3 | List customers, read one customer, and update a customer's details, such as phone, address, or business-number fields |
| Contacts | 2 | List contacts (end users) and create a contact for a customer |
| Tickets | 4 | List tickets, read one ticket, open a ticket, and update a ticket's status, priority, or assigned technician |
| Alerts, contracts, billing, and knowledge base | 5 | List monitoring alerts, list contracts and read one contract, list billing invoices, and list knowledge base articles |
Install it from Extensions like any other catalog extension. See Browsing and installing extensions for the general install flow.
Getting the API Key
Atera issues one API key per account. In Atera, go to Admin > Data Management > API and copy the key shown there. The key has no scopes: it gives full access to your Atera account, so treat it as a full-access credential and store it only in your runner's Key Vault. The approval gates described below limit what an agent does with it, not what the key itself allows.
Providing the Credentials to Your Runner
Store two secrets in your runner's Key Vault with these exact names:
| Secret | Value |
Atera-ApiUrl |
The Atera API base URL, normally https://app.atera.com/api/v3 |
Atera-ApiKey |
The account API key, exactly as Atera shows it. The extension sends it unchanged on every request. |
For how to add secrets, see Accessing and updating your runner's Key Vault. The agent reads the credentials from the runner and never asks you for them.
Reads and Approval-Gated Changes
Of the 17 tools, 13 only read data and run without interruption. The other four create or change records in Atera, and each one pauses the run for approval. 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 | Open a ticket; update a ticket; create a contact; update a customer |
| Read-only | List and read agents, customers, contacts, tickets, and contracts; list a customer's agents; list monitoring alerts, billing invoices, and knowledge base articles |
Monitoring alerts, contracts, billing, and the knowledge base are read-only in this extension.
Skills
The extension ships four skills that guide an agent through common Atera tasks:
| Skill | Use it to |
| Triage and Manage Tickets | Find or read a ticket, check its status, open a ticket for a customer, or change a ticket's status, priority, or assignee. Creates and updates are approval-gated. |
| Look Up Devices and Agents | List all agents, list a customer's devices, or read one device's OS and last-reboot detail. Read-only. |
| Manage Customers and Contacts | Find a customer or contact, read customer detail, update a customer, or create a contact. Updates and creates are approval-gated. |
| Review Alerts, Contracts and Billing | Review monitoring alerts, contracts, billing invoices, or knowledge base articles. Read-only. |
Tips for Working With Atera
- Refer to customers and contacts by name. The agent looks up the customer or contact before it creates or updates a ticket or contact, rather than guessing an id.
- A new ticket needs a title and a description. The agent identifies the requester by their contact record where it can, or by their email address.
- Ticket priority is one of
Low,Medium,High, orCritical, and ticket status is one ofOpen,Pending,Resolved, orClosed - A new contact needs an email address, and the agent associates it with the customer you name
- The list tools return the complete list in one call, so you don't need to page through results
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.