21RISK is a web application that simplifies working with checklists, audits, and actions, facilitating compliance and risk management processes.
21RISK is a web application that simplifies working with checklists, audits, and actions, facilitating compliance and risk management processes. On Nagent, 21risk is exposed as a fully-configurable business intelligence integration that any agent can call — 8 actions, and API key authentication. No code is required to wire 21risk into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use 21risk to automate the kinds of tasks business intelligence teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire 21risk into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against 21risk, with input parameters and output schema. Drop these into any step of an agent built in Helix.
_21RISK_GET_COMPLIANCETool to retrieve compliance data for sites, categories, or questions. Use when you need OData-based compliance data for analytics or reporting.
Input parameters
Maximum number of records to return (minimum 1).
Number of records to skip for paging (minimum 0).
Whether to include a total count of matching records.
Comma-separated list of related entities to expand.
OData filter expression to narrow results (e.g., 'Rank gt 5').
Comma-separated list of properties to include in the response (e.g., 'Name,Rank').
OData orderby clause to sort results (e.g., 'Rank desc').
Server-driven pagination token from previous response.
Max size in MB for each request, between 1 and 450 (default is 50).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
_21RISK_GET_ITEMSTool 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).
Input parameters
Maximum number of items to return (>=1).
Number of items to skip (offset) for pagination.
Navigation properties to expand.
OData $filter expression, e.g., 'Item Cost gt 100'.
Comma-separated list of properties to include in the response, e.g., 'Item Cost,Item Date'.
Comma-separated ordering of properties, e.g., 'Item Date desc'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
_21RISK_GET_ITEMS_PER_MONTHTool to retrieve fact table data for ItemsPerMonth, one row per question per site per month. Use when querying monthly item data with OData parameters ($filter, $top, $skip, $select, maxPageSizeInMb).
Input parameters
Maximum number of records to return
Number of records to skip for pagination
OData filter expression, e.g. siteId eq '123' and year eq 2023
Comma-separated list of properties to include, e.g. 'siteId,questionId,month,year'
Maximum payload size per request in MB (1–450)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
_21RISK_GET_ORGANIZATIONSTool to retrieve organizations from the 21RISK OData API. Use when you need to list, filter, or paginate organizations via OData parameters after authentication is confirmed.
Input parameters
Maximum number of organizations to return (>=1).
Number of organizations to skip (offset) for pagination.
OData $filter expression to filter organizations, e.g., 'Status eq 1'.
OData $orderby expression to sort results, e.g., 'Name desc'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
_21RISK_GET_PROPERTIESTool to fetch a list of properties related to sites, including COPE information and other relevant data. Use when you need property insurance details via OData API after authentication.
Input parameters
Maximum number of records to return (>=1).
Number of records to skip for pagination (>=0).
OData $filter expression to filter properties, e.g., 'Site Status eq 'Active''.
Comma-separated list of fields to include, e.g., 'Site Name,Site Address'.
Comma-separated list of fields to order by, e.g., 'Site Name desc'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
_21RISK_GET_REPORTSTool to retrieve audit reports, including draft, published, and scheduled reports. Use when you need a paginated list of reports with optional OData filtering.
Input parameters
Number of items to include in the result (>=1).
OData filter to narrow results (e.g., `Report Status eq 'published'`).
Opaque token for server-driven pagination from previous responses.
Maximum payload size in MB for each request (1-450). Defaults to 50 if not provided.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
_21RISK_GET_RISKMODEL_CATEGORIESTool to retrieve risk model categories for grouping questions and compliance checks. Use when you need to filter, select, or paginate risk model categories via OData parameters ($filter, $select, $orderby, $top, $skip, $count).
Input parameters
Maximum number of records to return (minimum 1)
Number of records to skip for pagination (minimum 0)
Whether to include a total count of matching records in the response
Comma-separated list of related entities to expand
OData filter expression to narrow results, e.g., _KeyModelId eq 'model123'
Comma-separated list of properties to include in the response, e.g., 'Category Name,Category Level'
OData orderby clause to sort results, e.g., 'Category Level Sort Order desc'
Server-driven pagination token from previous response
Maximum payload size per request in MB (1–450)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
_21RISK_GET_RISK_MODELSTool to retrieve risk models used for audits and compliance. Use when you need to list available risk models with optional OData queries.
Input parameters
Maximum number of risk models to return (>=1).
Number of risk models to skip (offset) for pagination, default is 0.
Include total count of matching records when set to true.
OData $expand expression to include related entities inline.
OData $filter expression to filter risk models, e.g., `Name eq 'Operational Risk'`.
OData $select expression to limit fields returned, e.g., `Name,Description`.
OData $orderby expression to sort results, e.g., `CreatedDate desc`.
Opaque token for server-driven pagination from previous responses.
Maximum payload size in MB for each request (1-450). Defaults to service default if not set.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 30 agents privately built on Nagent that already use 21risk.
Build on Nagent
Connect 21risk to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find 21risk, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, 21risk is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once 21risk is connected, you configure its 8 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop 21risk steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a 21risk event fires, the agent kicks off automatically.
Every 21risk action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While 21risk ships with 8 pre-built business intelligence actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching 21risk together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build 21risk-based workflows tailored to your business.