ceven

21risk

Pulls compliance data, audit reports, and site risk metrics into your workflows to automate risk monitoring and report generation.

Try 21risk in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native 21risk integration

    • Describe the outcome and Ceven picks the right 21risk calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your 21risk data, across all 8 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke 21risk access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in 21risk, when, and on whose behalf.
    • The agent pauses and asks when 21risk is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach 21risk.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every 21risk action to support review and sign off.

Supported tools

Every action Ceven's agents can run on 21risk, and when to use it.

Get Compliance
Use this when you need odata based compliance data for specific sites, categories, or questions to drive analytics.
Get Items
Pull a filtered and paged list of items from the beta api for deep reporting on specific risk markers.
Get Items Per Month
Retrieve fact table data with one row per question per site per month to analyze monthly trends.
Get Organizations
List, filter, or paginate organizations to map compliance data to the correct business entity.
Get Properties
Fetch property details and insurance information related to specific sites.
Get Reports
Retrieve a list of draft, published, or scheduled audit reports for review.
Get Risk Model Categories
Pull risk model categories to group questions and compliance checks in a report.
Get Risk Models
List available risk models used for audits to determine which framework a site is following.
Get Sites
Retrieve a list of locations and sites using odata query parameters.
Get Items (BETA)
Tool to retrieve items (beta) from the 21risk odata api. use when you need a filtered and paged list of items for analytics and reporting. example: get items($filter="item cost gt 100", $top=50).

10 actions · scroll to see them all

Frequently asked questions

Ceven communicates with 21RISK using the odata protocol, which allows for sophisticated filtering, selecting, and paging of data. When you ask for a specific site or a set of failed items, the agent constructs an odata filter string that requests only the necessary records from the 21RISK server. This ensures that workflows remain fast and do not hit payload limits when dealing with thousands of audit points. The agent can handle complex queries like filtering items where the cost is greater than a certain value or pulling only specific columns to reduce data noise. This structured approach allows Ceven to transform raw audit data into clean summaries for your team.
Ceven can retrieve scheduled reports and monitor their status via the Get Reports action. While the agent reads the status and content of these reports, the actual scheduling logic resides within the 21RISK application. You can set up a workflow where Ceven checks for a published report every Monday morning and then parses the results to send alerts to site managers. If a report is still in draft status, the agent can notify the auditor to finalize it. This creates a bridge between the report generation in 21RISK and the action taking in your other business tools.
The Get Items tool is currently in beta, which means it may have different stability profiles than the core compliance endpoints. One specific quirk is that it requires very precise odata syntax for filtering to avoid timeout errors on large datasets. If a query is too broad, the 21RISK api may reject the request or return an incomplete set. Ceven manages this by automatically implementing pagination and limiting the top record count to fifty per request. Users should be aware that beta endpoints may undergo schema changes that require the agent to refresh its mapping of the risk items.
Ceven uses the Get Organizations and Get Sites actions to build a relational map of your risk landscape. When a workflow triggers on a site failure, the agent first identifies the site id and then queries the organization endpoint to find the parent entity. This allows the agent to route notifications to the correct corporate office rather than just the local site contact. By linking these two data points, Ceven can generate aggregate reports that show which organizations are struggling with compliance across multiple sites, providing a high level view of systemic risk across your entire property portfolio.
Currently, the integration focuses on read operations to pull compliance data, reports, and risk models into your workflows. The agent cannot write new audit responses or change the status of a checklist item directly within 21RISK. The intended workflow is for Ceven to identify a gap in 21RISK and then trigger a task in a tool like Jira or Monday dot com for a human to fix the issue. Once the human fixes the issue and updates 21RISK, the agent will see the updated compliance status during the next sync and can then close the external task.
The Get Items Per Month tool accesses a specific fact table that provides a snapshot of one row per question per site per month. This is different from the real time compliance tool as it is optimized for longitudinal analysis. Use this when you want the agent to calculate if a site is improving or declining in its risk score over a six month period. The agent pulls these monthly slices and can then perform calculations to find the percentage of compliance growth. This is ideal for quarterly business reviews where you need to prove that risk mitigation efforts are working.
Ceven uses secure authentication to connect to the 21RISK odata api, ensuring that all data in transit is encrypted. The agent operates under the permissions of the authenticated user, meaning it can only access the sites, reports, and organizations that the user has permission to see within 21RISK. We do not store your raw credentials in plain text and all access tokens are encrypted at rest. Because the integration relies on a read heavy flow, the risk of accidental data modification is eliminated. You can audit every request the agent makes through the Ceven activity log to see exactly what data was pulled.
For organizations with hundreds of risk model categories, Ceven utilizes the select and filter parameters of the odata api to avoid overloading the workflow context. Instead of pulling every category at once, the agent queries for specific categories based on the context of the current audit. If a workflow requires a full list, the agent handles the pagination automatically, walking through the pages of results until the full set is retrieved. This prevents the model from becoming confused by too much irrelevant data and ensures that the most pertinent risk categories are used to categorize the audit findings.

Alternatives to 21risk

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

AuditBoard logoAuditBoardMetricStream logoMetricStreamDiligent logoDiligent

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect 21risk and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free