Catch missing details in 21risk audit evidence
Run a consistent completeness check on supplied evidence records and get a clear list of items to verify.
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
Evidence gaps are easy to miss when records are reviewed manually across a large audit.
- Check records against a completeness checklist you define.
- Identify missing or inconsistent values for human review.
- Make recurring evidence reviews more consistent.
Setup
Build it in a few focused steps.
- 1Connect 21risk and Codeinterpreter once in the Notis portal.
- 2Create an automation and name it for evidence completeness review.
- 3Tell Notis to check supplied audit evidence records against your required fields and report missing or inconsistent details.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real evidence sample and confirm the required fields and checks.
Questions about this workflow
Does this workflow validate whether evidence is legally sufficient?
No. It checks the data against requirements you provide and flags issues for review. Have the appropriate reviewer judge evidence sufficiency.
What if the records do not include required fields?
Provide the required field list in the instruction. If a field is unavailable in the input, the result should identify it as missing rather than infer a value.
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.