Connect Zendesk to Dynamics365
When something happens in Zendesk, Notis takes the next step in Dynamics365. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Zendesk to Dynamics365
Turn new Zendesk tickets into Dynamics cases
Create a Dynamics365 case whenever a new Zendesk ticket needs tracked support ownership.
Add Zendesk requesters as Dynamics contacts
Create a Dynamics365 contact from the requester on each new Zendesk ticket when no matching contact exists.
Create Dynamics accounts for new Zendesk users
Use new Zendesk user events to create Dynamics365 account records for organizations that are not yet in the CRM.
Create contacts from new Zendesk users
Add each newly created Zendesk user to Dynamics365 as a contact after checking for an existing match.
Convert qualifying Zendesk tickets into leads
Create a Dynamics365 lead when a new Zendesk ticket signals buying interest or an expansion opportunity.
Create opportunities from expansion requests
Open a Dynamics365 opportunity when a Zendesk ticket describes an upgrade, expansion, or related purchase.
Update Dynamics cases with Zendesk follow-up
Find the related Dynamics365 case and update it with a new Zendesk ticket summary or customer development.
Update Dynamics leads after qualification tickets
Use a Zendesk ticket to update a related Dynamics365 lead when support reveals qualification or disqualification information.
Create leads for promising new Zendesk users
Create a Dynamics365 lead for a new Zendesk user when their profile or organization matches your prospect criteria.
Supported Triggers and Actions
Notis builds workflows that link Zendesk to Dynamics365. A trigger fires from one place; an action lands in another.
Zendesk triggers
Dynamics365 actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get all invoices action
Get all invoices action
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Account
Creates a new account entity record in dynamics crm using the web api.
New User Created
Triggered when a new user is created in Zendesk.
Create Case
Creates a new case (incident) entity record in dynamics crm using the web api.
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
Create Contact
Creates a new contact entity record in dynamics crm using the web api.
Create Invoice
Creates a new invoice entity record in dynamics crm using the web api.
Create Lead
Creates a new lead entity record in dynamics crm using the web api.
Create Opportunity
Creates a new opportunity entity record in dynamics crm using the web api.
Create Sales Order
Creates a new sales order entity record in dynamics crm using the web api.
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.
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.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
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.
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.
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:
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.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Zendesk and Dynamics365
Connect any two apps with Notis in the middle.
Zendesk and Dynamics365, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Dynamics365.