Connect Zendesk to Cutt ly

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

View example

Review recent short links when a Zendesk user is created

When Zendesk creates a user, retrieve recent Cuttly links and prepare a quick inventory for relevant onboarding or support work.

View example

Add recent link context to every new Zendesk ticket

When a Zendesk ticket arrives, retrieve recent Cuttly URLs and summarize which links may matter for the support response.

View example

Check recent short links before a support escalation

Start a webhook when a Zendesk case is escalating, retrieve recent Cuttly URLs, and produce a link check for the handoff.

View example

Send a daily Cuttly link review for support

On a schedule, retrieve recently shortened Cuttly URLs and send a concise review to the support team.

View example

Review recent links before drafting a ticket response

For each new Zendesk ticket, retrieve recent Cuttly URLs and flag links that need human verification before a reply.

View example

Audit welcome links when a Zendesk user is created

When a new Zendesk user appears, retrieve recent Cuttly URLs and identify which links could support a welcome or onboarding note.

View example

Build a link context brief during a support incident

Trigger a Notis webhook during an incident to retrieve recent Cuttly URLs and compile context for the Zendesk response team.

View example

Run a weekly support link cleanup review

Once a week, retrieve recent Cuttly URLs and ask Notis to identify links that deserve a support documentation review.

View example

Prepare link follow-up context for new tickets

When a Zendesk ticket is created, retrieve recent Cuttly URLs and produce a follow-up brief for the next support action.

Supported Triggers and Actions

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

Zendesk triggers

Cutt ly actions

Recurring trigger

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

TriggerScheduled

View Last Shortened URLs

This action retrieves a list of recently shortened urls from your cutt.ly account. it allows users to view their latest shortened links and their details. note: due to api limitations, this action may not return all historical urls. for complete history, please use the cutt.ly dashboard.

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.