Put ticket evidence where analysis can happen
Make logs and exports available to your analysis workflow immediately.
Trigger
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
Action
Upload File
Upload a file to the sandbox environment. the files should be uploaded to the /home/user folder.
Why this helps
Attachments and diagnostic files are scattered across support conversations and local downloads.
- Centralize evidence for investigation
- Reduce manual downloading and reuploading
- Start analysis with the original context
Setup
Build it in a few focused steps.
- 1Connect Zendesk and Codeinterpreter once in Notis.
- 2Create an automation named Ticket evidence upload.
- 3Tell Notis to upload available ticket files to /home/user and report filenames, missing files, and any upload errors.
- 4Pick the New Zendesk Ticket trigger and choose where reports should go.
- 5Test with one ticket containing a diagnostic file.
Questions about this workflow
What files are uploaded?
The workflow uploads files available from the ticket context and reports anything unavailable.
Can the workflow analyze the files too?
This package focuses on upload; you can add analysis instructions after the files are present.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Zendesk to Codeinterpreter. A trigger fires from one place; an action lands in another.
Zendesk 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.
New User Created
Triggered when a new user is created in Zendesk.
Get File
Get a file from the sandbox and returns the file. the files should be read from /home/user folder.
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
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.
Zendesk 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.