Skip to content
Notis

Spot recurring support themes as tickets arrive

See patterns in customer language before they become a backlog problem.

Trigger

New Zendesk Ticket

Triggers when a new ticket is created in a specified Zendesk view.

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

Recurring issues stay hidden when tickets are handled one by one.

  • Identify repeated customer problems
  • Inform product and documentation priorities
  • Reduce manual tagging effort

Setup

Build it in a few focused steps.

  • 1Connect Zendesk and Codeinterpreter once in Notis.
  • 2Create an automation named Ticket theme signal.
  • 3Tell Notis to extract themes, sentiment cues, and possible product or documentation gaps from each ticket.
  • 4Pick the New Zendesk Ticket trigger and choose where run reports go.
  • 5Test with one representative ticket and review the signals.

Questions about this workflow

Is this a replacement for Zendesk reporting?

No. It provides qualitative analysis of ticket text to complement existing reporting.

Can it compare against historical tickets?

Only if historical data is supplied to the workflow or made available in the ticket context.

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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

New User Created

Triggered when a new user is created in Zendesk.

TriggerInstant

Get File

Get a file from the sandbox and returns the file. the files should be read from /home/user folder.

ActionInstant

New Zendesk Ticket

Triggers when a new ticket is created in a specified Zendesk view.

TriggerPolling

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.

ActionInstant

Upload File

Upload a file to the sandbox environment. the files should be uploaded to the /home/user folder.

ActionInstant

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.