Connect Zendesk to Bolna
When something happens in Zendesk, Notis takes the next step in Bolna. 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 Bolna
Call a customer when a new Zendesk ticket needs a fast response
Turn a new Zendesk ticket into an outbound Bolna call with a concise context brief for the agent.
Schedule a Bolna follow-up batch for new tickets
Group new Zendesk tickets into a Bolna calling batch for a planned support window.
Set up an inbound Bolna line for new Zendesk users
When a Zendesk user is created, prepare a Bolna agent for inbound support calls.
Review Bolna agents when a new Zendesk user arrives
Use each new Zendesk user event to retrieve the current Bolna agent inventory for routing decisions.
Check Bolna phone capacity for new ticket callbacks
Retrieve available Bolna phone numbers when a new Zendesk ticket arrives so callback planning uses current capacity.
Route new Zendesk tickets to a suitable Bolna agent
Retrieve Bolna agents for every new ticket and recommend the best fit from the ticket context.
Inspect a Bolna agent before an urgent ticket callback
Retrieve a selected Bolna agent profile when a new Zendesk ticket needs a verified callback setup.
Prepare phone options for new customer onboarding
Retrieve Bolna phone numbers when a Zendesk user is created and summarize viable onboarding contact options.
Review Bolna agent activity for new ticket follow-up
Retrieve all executions for a Bolna agent when a new Zendesk ticket arrives and summarize relevant activity.
Supported Triggers and Actions
Notis builds workflows that link Zendesk to Bolna. A trigger fires from one place; an action lands in another.
Zendesk triggers
Bolna actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete agent by id
Delete an agent
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete batch by id
Delete a batch
New User Created
Triggered when a new user is created in Zendesk.
Fetch all batches by agent id
List all batches for agent
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
Get all agents
List all agents
Get all phone numbers
List all phone numbers for your account
Get execution by id
Retrieve specific execution by `execution id`
Make a phone call from agent
Initiate calls
Retrieve agent by id
Retrieve an agent
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 Bolna
Connect any two apps with Notis in the middle.
Zendesk and Bolna, 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 Bolna.