The CloudRadial AutomationAI Action1 extension gives a workflow or agent read-only access to your Action1 patch management tenant: list the organizations you manage, inventory their managed endpoints, check agent and patch status, review detected vulnerabilities, and pull report data. This article covers what the extension can do, the API credential and secrets it needs, and the skills that ship with it. It is for workspace users who build automations (Admin or Owner Role).
- What the Extension Covers
- Creating the API Credential
- Providing the Credentials to Your Runner
- Read-Only Access
- Skills
- Tips for Working With Action1
What the Extension Covers
The extension calls the Action1 REST API v3.0 and provides 11 tools across four areas:
| Area | Tools | What you can automate |
| Organizations and account | 3 | List the organizations you manage, look up the identity and role of the API credential, and list the users in your Action1 tenant |
| Managed endpoints | 4 | List the managed endpoints (devices) in an organization, read one endpoint, get the agent and patch status roll-up, and list endpoint groups |
| Vulnerabilities | 1 | List the vulnerabilities Action1 has detected across an organization's endpoints |
| Reports | 3 | List the available reports and the data sources that feed them, and fetch the rows of a report for an organization |
Install it from Extensions like any other catalog extension. See Browsing and installing extensions for the general install flow.
Creating the API Credential
In Action1, go to Configuration > Users & API Credentials and select + New API Credentials. Copy the Client ID and the Client Secret. Action1 shows the secret only once, at creation, so store it securely right away.
The role you give the credential determines what the agent can see in Action1. The runner exchanges the Client ID and Client Secret for a short-lived access token and renews it as needed, so you store only the credential, never a token.
Providing the Credentials to Your Runner
Store three secrets in your runner's Key Vault with these exact names:
| Secret | Value |
Action1-BaseUrl |
The Action1 API base URL. Use https://app.action1.com/api/3.0 for the North America instance. If your Action1 account is in another region, use that region's host with the same path: https://app.na-2.action1.com/api/3.0 (North America 2), https://app.eu.action1.com/api/3.0 (Europe), https://app.uk.action1.com/api/3.0 (United Kingdom), or https://app.au.action1.com/api/3.0 (Australia). |
Action1-ClientId |
The Client ID of the API credential |
Action1-ClientSecret |
The Client Secret from the same credential |
For how to add secrets, see Accessing and updating your runner's Key Vault. Add the secrets in the Key Vault only; never paste their values into the extension.
Read-Only Access
All 11 tools only read data. None of them change anything in Action1, so none pause a run for approval, and agents can use the extension without anyone approving each call. To trial a prompt before you build a workflow, see Testing your setup in the AI Playground.
Skills
The extension ships five skills that guide an agent through common Action1 tasks:
| Skill | Use it to |
| List organizations | Discover the organizations you manage and their ids, which nearly every other Action1 call needs |
| Inventory managed endpoints | List and inspect the managed devices in an organization, their groups, and their agent and patch status |
| Assess vulnerabilities | Review the vulnerabilities Action1 has detected across an organization's endpoints |
| Pull report data | List Action1's available reports and pull the rows of a specific report for an organization |
| Account and users | Look up the current API identity and the users in your Action1 tenant |
Tips for Working With Action1
- Almost everything in Action1 belongs to an organization. Name the organization, or let the agent list organizations first, so it can pass the right organization id to the endpoint, vulnerability, and report tools.
- Ask for extended endpoint detail when you need it. The endpoint list can include OS, patch status, last-seen time, and missing critical updates.
- The organization and managed-endpoint list tools return the complete list in one call, so you don't need to page through results
- Action1 allows about 30 requests per minute. Above that it returns HTTP 429, so avoid workflows that query many endpoints one at a time.
- If results are missing data you expect, check the role on the API credential. It determines what the agent can see.
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.