Connect Box to 21risk
When something happens in Box, Notis takes the next step in 21risk. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Box to 21risk
Track Box Sign completion in 21risk reports
Use a Box Sign status change to review 21risk reports for the corresponding compliance audit.
Check compliance data when a Box task is resolved
When a Box task assignment changes state, retrieve 21risk compliance data for a quick review of related checks.
Check monthly 21risk item history after a Box file update
When a new Box file version arrives, retrieve monthly 21risk item data to support a quick history review.
Look up 21risk sites when a Box folder gains a collaborator
When a Box folder collaboration is created, retrieve 21risk sites and summarize possible location context for access review.
Find 21risk reports when new Box evidence is uploaded
A new file in a Box evidence folder triggers a 21risk report lookup and a short summary for follow-up.
Review 21risk organizations when a Box Sign request starts
Use a new Box Sign request to retrieve 21risk organizations and summarize which one may be relevant.
Check 21risk property details when a Box link changes
A change to a Box file shared link prompts a review of 21risk property details that may inform the document's handling.
Review 21risk categories when a Box folder receives new items
When a Box folder gains a new item, retrieve 21risk risk model categories to help classify incoming compliance material.
Review 21risk items when a Box task changes
A Box task update prompts a filtered 21risk item lookup and a summary of records for review.
Supported Triggers and Actions
Notis builds workflows that link Box to 21risk. A trigger fires from one place; an action lands in another.
Box triggers
21risk actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Compliance
Tool to retrieve compliance data for sites, categories, or questions. use when you need odata-based compliance data for analytics or reporting.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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).
Collaboration Details Changed
Triggers when a collaboration's details change (e.g., role, status, expiration). This trigger monitors a specific collaboration and detects when any meaningful field changes, such as role, status, expiration date, access type, or acknowledgment status.
Get Items Per Month
Tool 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).
Comment Changed
Triggers when a comment's content or details change in Box. This trigger monitors a specific Box comment and detects when any meaningful field changes, such as message text edits, tagged message changes, or modification timestamp updates.
Get Organizations
Tool 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.
New File Comment Added
Triggers when a new comment is added to a file in Box. This trigger monitors a specific Box file and fires when new comments are detected.
Get Properties
Tool 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.
File Metadata Changed
Triggers when a file's metadata or properties change in Box. This trigger monitors a specific Box file and fires when changes are detected in key fields like name, description, size, modification time, parent folder, or status.
Get Reports
Tool to retrieve audit reports, including draft, published, and scheduled reports. use when you need a paginated list of reports with optional odata filtering.
File Shared Link Changed
Triggers when a file's shared link settings change in Box. This trigger monitors a specific Box file's shared link and fires when changes are detected in the shared link configuration, such as access level, permissions, password protection, expiration date, or vanity URL.
Get RiskModel Categories
Tool 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).
New File Version Uploaded
Triggers when a new file version is uploaded to a file in Box. This trigger monitors a specific Box file and fires when new versions are detected.
Get Risk Models
Tool to retrieve risk models used for audits and compliance. use when you need to list available risk models with optional odata queries.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Box and 21risk
Connect any two apps with Notis in the middle.
Box and 21risk, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business 21risk.