Check audit data files before analysis
Catch file format and parsing problems early so your audit analysis starts with usable input.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
A data review can stall when a file has an unexpected format, delimiter, or unreadable structure.
- Inspect supplied files before deeper analysis begins.
- Identify common format or parsing problems early.
- Return concise diagnostics to guide the next step.
Setup
Build it in a few focused steps.
- 1Connect 21risk and Codeinterpreter once in the Notis portal.
- 2Create an automation and name it for audit file checks.
- 3Tell Notis to inspect each supplied audit data file with a terminal command and report its format and any parsing errors.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test with one real file and confirm the diagnostics are useful for your team.
Questions about this workflow
Will this action retrieve a file from 21risk?
No. The file must be supplied to the Codeinterpreter sandbox or made available to the automation as input.
Can it fix malformed files?
The instruction can ask for diagnostic output, but this workflow is framed as a check. Review any proposed corrections before relying on them.
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.