Bring related 21risk checklist gaps together
Turn a scattered list of checklist gaps into a few coherent themes your team can review and assign.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Teams lose time when similar compliance gaps appear under different checklist labels and are handled separately.
- Group similar gap descriptions for a clearer review.
- Help teams spot recurring themes across a submitted checklist.
- Make remediation planning easier to discuss.
Setup
Build it in a few focused steps.
- 1Connect 21risk and Codeinterpreter once in the Notis portal.
- 2Create an automation and name it for checklist gap grouping.
- 3Tell Notis to cluster the supplied checklist gaps by meaning and return each group with its source items.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test with one real checklist example and verify the groups preserve the original gap details.
Questions about this workflow
Does clustering change the checklist in 21risk?
No. This workflow analyzes the supplied data in Codeinterpreter and returns grouped findings. It does not update 21risk.
Can the groups be treated as official categories?
They are suggested groupings from the input text. Review them before using them as formal compliance categories or remediation decisions.
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.