Keep ticket research in one Apify dataset
Build a growing evidence base from every relevant ticket.
Trigger
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
Action
Store Data in Dataset
Tool to store data items in a dataset. use after collecting data when you want to batch-append or update items in an existing dataset.
Why this helps
Research gets scattered across tickets, chats, and local documents.
- Centralizes recurring research
- Makes prior findings reusable
- Avoids manual copy and paste
Setup
Build it in a few focused steps.
- 1Connect Zendesk and Apify once.
- 2Create an automation for dataset updates.
- 3Tell Notis what findings to store and identify the destination dataset.
- 4Select New Zendesk Ticket and where reports should go.
- 5Test by processing one real ticket.
Questions about this workflow
Does this create a new dataset?
No. It appends data to the existing dataset you specify.
What if the dataset is missing?
Name the missing dataset in the instruction and review the run report before changing the workflow.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Zendesk to Apify. A trigger fires from one place; an action lands in another.
Zendesk triggers
Apify actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Actor
Tool to create a new actor with specified configuration. use when you need to initialize a fresh actor programmatically before publishing or running it.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Dataset
Tool to create a new dataset. use when you need to initialize or retrieve a dataset by name.
New User Created
Triggered when a new user is created in Zendesk.
Create Actor Task
Tool to create a new actor task with specified settings. use when you need to configure or schedule recurring actor runs programmatically.
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
Create Task Webhook
Tool to create a webhook for an actor task. use when you need external notifications about task run events (e.g., completion or failure) in downstream systems.
Delete Actor
Tool to delete an actor permanently. use when you need to remove an actor by its id or username~actorname. confirm before calling.
Delete Webhook
Tool to delete a webhook by its id. use when removing a webhook after confirming the webhook id.
Get Actor Details
Tool to get details of a specific actor. use when you need actor metadata by id or username/actorname.
Get all webhooks
Tool to get a list of all webhooks created by the user. use when you need to enumerate webhooks before filtering or maintenance.
Connect any two apps with Notis in the middle.
Zendesk and Apify, 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 Apify.