Connect Zendesk to Devin MCP

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

View example

Check codebase impact for every new Zendesk ticket

Ask Devin which repositories and components a new support ticket may affect.

View example

Ask Devin for a likely resolution path

Use Devin to suggest where a new Zendesk ticket should be investigated and what to inspect first.

View example

Check new tickets against repository history

Ask Devin whether a new Zendesk issue resembles known code patterns or previously addressed areas.

View example

Read repository wiki context for a new ticket

Fetch relevant Devin wiki documentation so support and engineering share the same technical background.

View example

Map documentation topics for incoming tickets

Ask Devin for the wiki structure of the repository most relevant to each new Zendesk ticket.

View example

Review onboarding readiness from the codebase

When a Zendesk user is created, ask Devin what product documentation or setup surfaces may matter for onboarding.

View example

Find repository documentation for new user guidance

Use Devin wiki contents to prepare product guidance when a Zendesk user is created.

View example

Answer a repository question from a support escalation

Send a structured support escalation webhook to Devin for a context-grounded repository answer.

View example

Audit available Devin repositories weekly

Run a weekly check of the repositories your Devin account can query and share the result.

Supported Triggers and Actions

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

Zendesk triggers

Devin MCP actions

Recurring trigger

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

TriggerScheduled

Ask question

Ask any question about a GitHub repository and get an AI-powered, context-grounded response. Args: repoName: GitHub repository or list of repositories (max 10) in owner/repo format question: The question to ask about the repository

ActionInstant

Webhook trigger

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

TriggerInstant

List available repos

List all repositories available to query with your Devin account. Only available in private mode (via devin.ai endpoints).

ActionInstant

New User Created

Triggered when a new user is created in Zendesk.

TriggerInstant

Read wiki contents

View documentation about a GitHub repository. Args: repoName: GitHub repository in owner/repo format (e.g. "facebook/react")

ActionInstant

New Zendesk Ticket

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

TriggerPolling

Read wiki structure

Get a list of documentation topics for a GitHub repository. Args: repoName: GitHub repository in owner/repo format (e.g. "facebook/react")

ActionInstant

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.