Connect Zendesk to Dromo

When something happens in Zendesk, Notis takes the next step in Dromo. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Zendesk to Dromo

View example

Check Dromo uploads when a Zendesk ticket arrives

Review Dromo upload history whenever a new Zendesk ticket is created, then summarize relevant recent uploads for the support team.

View example

Send ticket data to a Dromo headless import

Turn structured details from a new Zendesk ticket into a file and upload it to a Dromo headless import.

View example

Review Dromo uploads for every new Zendesk user

When Zendesk creates a user, check Dromo upload history and return a concise activity brief for onboarding or support.

View example

Create a Dromo onboarding import from a new Zendesk user

Build a structured onboarding file from a newly created Zendesk user record and upload it to a Dromo headless import.

View example

Scan Dromo uploads for possible ticket duplicates

Use a new Zendesk ticket to inspect Dromo uploads and flag likely duplicate imports for review.

View example

Upload a Zendesk ticket attachment to Dromo

When a new ticket includes a usable data attachment, prepare it for a Dromo headless import and report the result.

View example

Check whether a new Zendesk user already has Dromo uploads

Look up Dromo uploads when a Zendesk user is created and flag existing activity for onboarding review.

View example

Upload a new Zendesk user roster row to Dromo

Create a one-row structured file from each new Zendesk user and upload it to a Dromo headless import for downstream processing.

View example

Add Dromo upload context to new ticket triage

List recent Dromo uploads for each new Zendesk ticket and summarize status clues that help route the request.

Supported Triggers and Actions

Notis builds workflows that link Zendesk to Dromo. A trigger fires from one place; an action lands in another.

Zendesk triggers

Dromo actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

List Uploads

Tool to retrieve a list of all uploads stored by dromo for your organization. use when you need to paginate or filter uploads.

ActionInstant

Webhook trigger

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

TriggerInstant

Upload File To Headless Import

Tool to upload a file to a headless import. use after obtaining a signed upload url from dromo. performs an http put of raw bytes to the provided signed url.

ActionInstant

New User Created

Triggered when a new user is created in Zendesk.

TriggerInstant

New Zendesk Ticket

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

TriggerPolling

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.