Connect Zendesk to Cults
When something happens in Zendesk, Notis takes the next step in Cults. 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 Cults
Turn new Zendesk tickets into a Cults model shortlist
When a customer asks for a 3D model, find relevant Cults models and summarize the best options for a reply.
Research Cults designers from new Zendesk tickets
Identify designer storefronts on Cults that match a customer's requested style, category, or creator preference.
Check Cults download history for support tickets
Use a new Zendesk ticket to investigate relevant Cults download history and prepare useful context for support.
Curate a Cults collection from recurring ticket requests
Group model requests from new Zendesk tickets into a proposed Cults collection for review.
Check Cults approved origins for new integration tickets
When a ticket concerns sharing or integration access, retrieve approved Cults sharing origins for a precise support response.
Prepare a Cults share link from a Zendesk request
For a qualifying ticket, generate a French locale Cults Share on Create link for a 3D file.
Build a Cults model guide for every new Zendesk user
When a user is created in Zendesk, prepare a tailored Cults model discovery guide for onboarding.
Start a Cults starter collection for new users
Use new Zendesk user events to find models and propose a personalized Cults starter collection.
Recommend Cults designers to new Zendesk users
After a new Zendesk user is created, identify Cults designer storefronts that fit the provided onboarding profile.
Supported Triggers and Actions
Notis builds workflows that link Zendesk to Cults. A trigger fires from one place; an action lands in another.
Zendesk triggers
Cults actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Approved Origins
Tool to retrieve approved sharing origins from Cults. Use when you need to infer the allowed domains for the Share on Create action. Use after authenticating with Cults.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Cults GraphQL POST
Tool to execute a GraphQL operation against the Cults API. Use when you need to fetch or mutate data via the Cults GraphQL endpoint.
New User Created
Triggered when a new user is created in Zendesk.
Share on Create (FR)
Tool to prefill a new creation on Cults (French locale). Use when you need to generate a one-click share link for a 3D file. Use after your site is approved by Cults.
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
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 Cults
Connect any two apps with Notis in the middle.
Zendesk and Cults, 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 Cults.