Check Ably event payloads against your schema
Catch missing or differently shaped payload fields with a repeatable check against your own expectations.
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
Payload shape changes can break downstream work when required fields are not checked consistently.
- Compare payload structure with a user-provided schema or checklist.
- Summarize missing or unexpected fields.
- Run validation from a simple HTTP request.
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 payload source and provide the schema or required-field checklist.
- 4Choose notis_webhook as the trigger and select where run reports should go.
- 5Test with one valid and one intentionally incomplete sample.
Questions about this workflow
Does this know the correct schema automatically?
No. Provide the schema or required-field checklist that defines a valid payload.
Can it compare payload versions?
Yes, if you provide the expected version or prior schema and describe the comparison.
Will it modify the event payload?
This workflow checks and reports on the payload. It does not publish or alter Ably messages.
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.