See where 21risk actions are getting stuck
Get a regular, data-based view of overdue actions and aging patterns so follow-up starts with the biggest risks.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Execute Code
Execute python code in a sandbox and return any result, stdout, stderr, and error. use /home/user folder to write/read files. try to not use plt.show() as the code is executed remotely. use files for image/chart output instead.
Why this helps
Overdue compliance actions can quietly accumulate when nobody has time to scan each task individually.
- Summarize overdue counts and action age from each supplied snapshot.
- Spot patterns that may deserve attention before the next review.
- Reduce manual scanning of long action lists.
Setup
Build it in a few focused steps.
- 1Connect 21risk and Codeinterpreter once in the Notis portal.
- 2Create an automation and name it for action backlog review.
- 3Tell Notis to analyze the supplied 21risk action records, calculate aging, and summarize overdue work.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real action data example and review the date and aging assumptions.
Questions about this workflow
Will this workflow fetch action records from 21risk by itself?
No. It runs on a Notis schedule, but the 21risk records must be made available to the automation as input. No 21risk trigger event is available here.
How does it decide an action is overdue?
The input needs a due date and your definition of overdue. If those are missing, the report should state that it cannot calculate overdue status reliably.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 21risk to Codeinterpreter. A trigger fires from one place; an action lands in another.
21risk triggers
Codeinterpreter actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Sandbox
Create a sandbox to execute python code in a jupyter notebook cell. this is useful for agents to communicate, execute code, see output, read files, write files, etc. it's like you own personal computer, but in the cloud. use /home/user folder to write/read files.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Execute Code
Execute python code in a sandbox and return any result, stdout, stderr, and error. use /home/user folder to write/read files. try to not use plt.show() as the code is executed remotely. use files for image/chart output instead.
Get File
Get a file from the sandbox and returns the file. the files should be read from /home/user folder.
Run Terminal Command
Run a command in the terminal and returns the stdout, stderr, and error code. use /home/user folder to write/read files.
Upload File
Upload a file to the sandbox environment. the files should be uploaded to the /home/user folder.
Connect any two apps with Notis in the middle.
21risk and Codeinterpreter, 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 Codeinterpreter.