Connect Zendesk to Bonsai
When something happens in Zendesk, Notis takes the next step in Bonsai. 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 Bonsai
View exampleCheck Bonsai cluster details for every new Zendesk user
When Zendesk creates a user, retrieve the selected Bonsai cluster details and send a concise readiness report.
View exampleInventory Bonsai spaces when a Zendesk ticket arrives
When a new Zendesk ticket is created, list available Bonsai spaces and report relevant regions or server groups.
View exampleReview Bonsai space metadata for new Zendesk users
Retrieve details for a specified Bonsai space when a new Zendesk user is created and summarize its metadata.
View exampleList all Bonsai spaces for support triage
When a ticket is created, retrieve the full list of Bonsai spaces and summarize options for the support team.
View exampleGenerate a Bonsai cluster brief from a webhook
Use an HTTP request to start a cluster detail lookup and return a concise status brief for your operations channel.
View exampleReview Bonsai space availability on a schedule
On a recurring schedule, list Bonsai spaces and summarize geographic regions and server groups for planning.
View exampleSend a recurring Bonsai space inventory digest
Run a scheduled workflow that retrieves all available Bonsai spaces and sends a digest to your chosen channel.
View exampleFetch Bonsai space details when review starts
Start a space detail lookup from a webhook and return metadata for an operational review.
View exampleAdd Bonsai cluster context to new ticket reviews
For each new Zendesk ticket, retrieve a specified Bonsai cluster's details and summarize relevant context for responders.
Supported Triggers and Actions
Notis builds workflows that link Zendesk to Bonsai. A trigger fires from one place; an action lands in another.
Zendesk triggers
Bonsai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Bonsai Cluster Details
Tool to retrieve details for a single bonsai cluster by slug. use when you need to inspect a cluster's configuration and status.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Bonsai Spaces
Tool to retrieve a list of all available spaces. use when you need to see the server groups and geographic regions available to your account.
New User Created
Triggered when a new user is created in Zendesk.
Retrieve Space Details
Tool to retrieve details for a single space by its path. use when you need metadata for a space before provisioning a cluster. use after confirming this detail exists. e.g., 'omc/bonsai/us-east-1/common'.
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
List Spaces
Tool to retrieve a list of all available spaces. use when you need to see the server groups and geographic regions available for your account.
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 Bonsai
Connect any two apps with Notis in the middle.
Zendesk and Bonsai, 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 Bonsai.