The CloudRadial AutomationAI Cork Protection extension lets a workflow or agent review your clients' cyber risk in Cork: Cork Cyber Scores, cyber-warranty coverage, compliance and risk events, and software vulnerabilities across the devices, domains, and inboxes Cork observes. It can also list the integrations that feed Cork and, with approval, trigger a manual resync of one. This article covers what the extension can do, the API key it needs, which tool 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
- Creating the API Key
- Providing the Credentials to Your Runner
- Reads and Approval-Gated Changes
- Skills
- Tips for Working With Cork Data
What the Extension Covers
The extension calls the Cork API and provides 14 tools across these areas:
| Area | What you can automate |
| Account | Read the Cork user the API key belongs to, which also confirms the key works |
| Clients and assets | List clients with their Cork Cyber Score and score history, warranty status, and integration tenants, and list the devices, email domains, and inboxes Cork observes for a client |
| Warranties | List active cyber-warranty packages |
| Compliance and risk events | List the compliance event types with their descriptions and cure periods, list a client's policy violations and risk events, and read a client's compliance notification settings |
| Software vulnerabilities | Read a summary of CVEs grouped by software product, and list individual CVEs with CVSS score, EPSS score, and known-exploited status |
| Integrations | List connected integrations and the integration types available to connect, and trigger a manual resync of a connected integration |
The extension does not connect a new integration or change an integration's credentials. Those steps require another vendor's credentials, which must not pass through an automation, so do them in the Cork console.
Install it from Extensions like any other catalog extension. It appears in the catalog as Cork Protection. See Browsing and installing extensions for the general install flow.
Creating the API Key
The extension signs in to Cork with an API key.
- In the Cork platform, open the Admin tab and select API Keys.
- Select Add API Key.
- Enter a name and choose when the key should expire.
- Generate the key and store it securely.
A Cork API key has the permissions of the user who creates it, so create it as a user whose access covers the clients and data you plan to automate. When the key expires, generate a new one and update the Cork-ApiKey secret. See Cork's Cork Public API & MCP Server article.
Providing the Credentials to Your Runner
Store two secrets in your runner's Key Vault with these exact names:
| Secret | Value |
Cork-ApiUrl |
The Cork API base URL, normally https://api.corkinc.com/api/v1. Include the /api/v1 path. |
Cork-ApiKey |
The API key you generated in Cork |
Store the key exactly as Cork issued it, without a Bearer prefix; the extension adds it for you. 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. Once the secrets are in place, ask the AI Playground which Cork user the extension is signed in as, to confirm the connection works.
Reads and Approval-Gated Changes
Of the 14 tools, 13 are read-only and run without interruption. The one tool that acts in Cork, a manual integration resync, is approval-gated: the run pauses 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 | Resync an integration. This triggers a fresh data pull on an integration that is already connected; it takes no credentials. |
| Read-only | Read the current user; list clients and a client's devices, domains, and inboxes; list warranties; list compliance event types and events; read compliance notification settings; read the vulnerability summary; list software vulnerabilities; list connected and available integrations |
Skills
The extension ships three skills that guide an agent through common Cork tasks:
| Skill | Use it to |
| Review Client Cyber Risk and Warranty | Review a client's Cork Cyber Score, software vulnerabilities, or warranty coverage, including finding clients with no active warranty. Read-only. |
| Investigate Compliance and Risk Events | Investigate a client's policy violations and risk events across their devices, domains, and inboxes, and review how those events are alerted. Read-only. |
| Review Integrations and Resync | See which integrations are connected, check which integration types are available, or force a fresh data pull on a connected integration. The resync is approval-gated. |
To give an agent these skills, see Creating custom agents and using them in workflows.
Tips for Working With Cork Data
- Refer to clients by name and let the agent look up the client id. The device, domain, inbox, and compliance-event tools all need it.
- To find clients with no active warranty, ask for clients whose warranty status is unwarranted. Cork has no separate per-client warranty lookup.
- Compliance events show only unresolved events unless you ask to include resolved ones. Ask for currently at-risk events to see only active risks.
- To focus on the highest-risk vulnerabilities, ask for known-exploited CVEs, a minimum priority (critical, accelerated, or routine), or a minimum CVSS or EPSS score
- After you connect an integration or change its credentials in the Cork console, ask the agent to resync it if you want the new data right away
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.