Skip to content
Notis

Connect Zendesk to Botstar

When something happens in Zendesk, Notis takes the next step in Botstar. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Examples

Ways Notis can move work from Zendesk to Botstar

View example

Sync New Zendesk Users to BotStar Sessions

When a Zendesk user is created, update the active BotStar conversation with the user's available profile details.

View example

Refresh BotStar Widget for New Zendesk Users

Reinitialize the BotStar widget with safe user context whenever Zendesk creates a new user.

View example

Announce New Zendesk Users in BotStar

Register a BotStar open callback that surfaces a concise greeting or context note for newly created Zendesk users.

View example

Load New Zendesk Ticket Context into BotStar

When a ticket is created, update the active BotStar session with a concise issue summary and customer context.

View example

Reinitialize BotStar After Ticket Creation

Refresh BotStar with the newly created Zendesk ticket context so the widget starts from a consistent state.

View example

Open BotStar for Priority Ticket Review

Open the BotStar live chat widget when a new Zendesk ticket meets the priority condition you describe.

View example

Close BotStar for Resolved Intake Tickets

Hide the BotStar widget when a newly created Zendesk ticket indicates the intake conversation is already resolved.

View example

Read BotStar Parameter for Ticket Routing

Retrieve a BotStar webview parameter when a new Zendesk ticket arrives and use it to guide the next support step.

View example

Send New Ticket Summary Back to BotStar

Send a concise summary of a newly created Zendesk ticket from the webview back to the BotStar chatbot.

Supported Triggers and Actions

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

Zendesk triggers

Botstar actions

Recurring trigger

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

TriggerScheduled

BotStar LiveChat onClose Callback

Tool to register a callback when the chat window is closed. use after the widget is initialized. example prompt: "register an onclose handler that logs 'goodbye!' to the console."

ActionInstant

Webhook trigger

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

TriggerInstant

Get BotStar Application IDs

Tool to retrieve the botstar application id (`appid`). use when initializing or reinitializing the live chat widget.

ActionInstant

New User Created

Triggered when a new user is created in Zendesk.

TriggerInstant

Livechat boot

Tool to reinitialize the live chat widget with provided data. use after initial load to reset or update widget configuration.

ActionInstant

New Zendesk Ticket

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

TriggerPolling

Close BotStar Livechat Widget

Tool to hide the live chat window. use when the chat widget is configured in livechat or popup mode.

ActionInstant

Livechat on open

Tool to register a callback when the chat window is opened. use after widget initialization.

ActionInstant

Livechat open

Tool to show the live chat window. use after the widget has been bootstrapped with botstarapi('boot') to programmatically open the chat window (mode must be 'livechat' or 'popup').

ActionInstant

Livechat update

Tool to update user details on the current live chat session. use when you need to modify user profile attributes during an active conversation.

ActionInstant

Get BotStar Webview Parameter

Tool to retrieve a parameter value passed from the botstar chatbot to the webview. use inside onchatbotready after your page loads in modal mode with bs:input meta tags.

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.

Notis

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.

  • 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

All12Manager5Telegram1Messages0Whatsapp2Email4Slack8

Migrate background jobs to a durable queue You can cancel it through Stripe

3 days

Notis v3 release update This one’s v3: Notis Manager (desktop app with …

8 days

Add multi-tenant RBAC User initiates a voice call

13 days

Draft pricing v (tiers, limits, overages) and sanity-check margins

2 weeks

Verify analytics events for new features That’s a really interesting automat…

1 month

Everything 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.

Related pairs

More ways to connect Zendesk and Botstar

Connect any two apps with Notis in the middle.

Zendesk and Botstar, 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 Botstar.