Connect Zendesk to Draftable

When something happens in Zendesk, Notis takes the next step in Draftable. 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 Draftable

View example

Review Draftable comparisons when a Zendesk ticket arrives

Use the newest Zendesk ticket to find relevant Draftable comparisons and give the agent a concise change summary for the reply.

View example

Spot change risks behind new Zendesk tickets

When a new ticket arrives, inspect Draftable comparisons for material changes and flag risks that need careful handling.

View example

Find duplicate document comparisons for support tickets

Use new ticket context to identify repeated or overlapping Draftable comparisons before agents repeat existing review work.

View example

Prepare onboarding document context for new Zendesk users

When a Zendesk user is created, review relevant Draftable comparisons to prepare a concise onboarding brief for the team.

View example

Check release related document regressions from tickets

Review Draftable comparisons when tickets mention a release, version, or update and flag unexpected regressions for follow up.

View example

Create a daily Zendesk document review digest

On a schedule, review recent Zendesk context supplied to Notis and summarize the Draftable comparisons that need attention.

View example

Review Draftable comparisons from a custom support webhook

Send a support review request to a Notis webhook and receive a focused list of relevant Draftable comparisons and findings.

View example

Gather comparison evidence for escalated Zendesk tickets

For new tickets marked by your process as escalated, inspect Draftable comparisons and prepare evidence for the handoff.

View example

Set a document version baseline for new Zendesk users

When a user is created, identify the relevant Draftable comparison baseline and summarize what the team should treat as current.

Supported Triggers and Actions

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

Zendesk triggers

Draftable actions

Recurring trigger

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

TriggerScheduled

List Comparisons

Tool to retrieve a paginated list of document comparisons. use when you need to browse comparisons across pages.

ActionInstant

Webhook trigger

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

TriggerInstant

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.