Connect Zendesk to Dpd2

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

View example

Match new Zendesk tickets to DPD customers

When a Zendesk ticket arrives, find the corresponding DPD customer and include account context in the run report.

View example

Check DPD purchases for a new Zendesk ticket

Review DPD purchase history when a Zendesk ticket is created and summarize relevant order activity.

View example

Review DPD storefronts when support tickets arrive

Use new Zendesk tickets to retrieve DPD storefronts and highlight the storefront context relevant to the request.

View example

Check DPD subscribers for new Zendesk tickets

When a ticket arrives, look up relevant DPD subscribers and summarize subscription context for support review.

View example

Enrich new Zendesk users with DPD customer context

When a Zendesk user is created, search DPD customers for a matching record and report account context.

View example

Review purchase history for new Zendesk users

When a Zendesk user is created, retrieve relevant DPD purchases to help identify existing customer activity.

View example

Check DPD API status before ticket enrichment

Ping DPD when a Zendesk ticket arrives so the run report confirms whether account lookups can proceed.

View example

Inventory DPD storefront context for new Zendesk users

When a Zendesk user is created, list DPD storefronts and summarize likely context for the new relationship.

View example

Verify a DPD notification during Zendesk triage

When a Zendesk ticket references a DPD notification, verify its signature and payload and report the result.

Supported Triggers and Actions

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

Zendesk triggers

Dpd2 actions

Recurring trigger

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

TriggerScheduled

Get Storefront

Tool to retrieve details of a specific storefront by its id. use when you need storefront metadata after you have its id.

ActionInstant

Webhook trigger

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

TriggerInstant

List DPD Customers

Tool to list customers in your dpd account. use when you need a filtered or paginated list of customers for reporting or synchronization.

ActionInstant

New User Created

Triggered when a new user is created in Zendesk.

TriggerInstant

List DPD Purchases

Tool to list all purchases made through your dpd account. use when you need to retrieve purchase records with optional date filters and pagination for reporting or analysis.

ActionInstant

New Zendesk Ticket

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

TriggerPolling

List Storefronts

Tool to list all storefronts in your dpd account. use after authenticating to fetch storefront details before managing products or purchases.

ActionInstant

List Subscribers

Tool to list subscribers for a given storefront. use when you need a paginated and filtered list of subscribers after storefront setup.

ActionInstant

DPD: Ping API

Tool to ping the api to check its status. use when verifying api connectivity before further operations.

ActionInstant

Verify DPD Notification

Tool to verify a webhook notification's authenticity by posting back the original signature and payload. use after receiving a notification to confirm it originates from dpd.

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.