Analyze webhook data with Codeinterpreter
Send a request to Notis and let Python turn the attached or accessible dataset into useful findings.
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
Dataset checks often stall while you download files, open a notebook, and remember which questions to ask.
- Run a repeatable analysis from an HTTP request.
- Summarize results in plain language.
- Save charts or other outputs in the sandbox for retrieval.
Setup
Build it in a few focused steps.
- 1Connect Ably and Codeinterpreter once in the Notis portal.
- 2Create an automation in the portal or tell Notis in plain language from any channel.
- 3Describe the analysis and expected output in one instruction, including where the dataset can be found.
- 4Choose notis_webhook as the trigger and select where run reports should go.
- 5Test with one real webhook request and dataset.
Questions about this workflow
Does Ably provide the trigger for this workflow?
No. Ably has no trigger events in this setup. A Notis webhook starts the automation, and Notis can use Ably as the connected source when your instruction needs its capabilities.
Can the workflow analyze any file included with the request?
The request needs to make the data available to the sandbox, such as through an accessible file or data source. Specify its location and format in your instruction.
Where do the analysis files go?
Codeinterpreter runs Python in a sandbox. Instruct it to save output files in the sandbox, then use an appropriate file retrieval step if you need a file returned.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ably to Codeinterpreter. A trigger fires from one place; an action lands in another.
Ably 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.
Ably 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.