Skip to content
Notis

Connect Zendesk to Callingly

When something happens in Zendesk, Notis takes the next step in Callingly. 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 Callingly

View example

Create a Callingly client for every new Zendesk user

Turn each newly created Zendesk user into a Callingly client record so onboarding starts with a complete calling profile.

View example

Register a Callingly agent from a new Zendesk user

Create a Callingly agent when a new Zendesk user represents a support or sales operator who needs calling access.

View example

Call a lead when a Zendesk ticket needs urgent follow-up

Use new Zendesk tickets to create outbound Callingly calls for leads who need a fast human response.

View example

Find the Callingly lead behind a new Zendesk ticket

Retrieve the matching Callingly lead for a new Zendesk ticket so an operator has the right context before responding.

View example

Retrieve call history for a new Zendesk ticket

Look up a related Callingly call when a new Zendesk ticket arrives and include the useful call context in the run report.

View example

Review recent Callingly calls for a new Zendesk ticket

List recent Callingly calls related to a new ticket so the team can see the latest outreach before deciding what to do next.

View example

List matching Callingly leads for a new ticket

Search Callingly leads related to a new Zendesk ticket and present the strongest matches for quick triage.

View example

Review Callingly clients when a Zendesk user is created

List Callingly clients when a new Zendesk user appears so you can detect an existing account before creating anything new.

View example

Review Callingly teams for a new Zendesk user

List Callingly teams when a Zendesk user is created so onboarding can identify the best destination for that person.

Supported Triggers and Actions

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

Zendesk triggers

Callingly actions

Recurring trigger

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

TriggerScheduled

Activate/Deactivate Client Account

Tool to activate or deactivate a client account. use when you need to toggle client access after onboarding or offboarding. example: "activate client 123" or "deactivate client 456".

ActionInstant

Webhook trigger

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

TriggerInstant

Create Agent

Tool to create a new agent. use when you need to register an agent in callingly after gathering their account id and contact details.

ActionInstant

New User Created

Triggered when a new user is created in Zendesk.

TriggerInstant

Create Outbound Call

Tool to create a new outbound call record. use after gathering call and lead details.

ActionInstant

New Zendesk Ticket

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

TriggerPolling

Create Client

Tool to create a new client. use when adding a new client to your callingly account.

ActionInstant

Create Team

Tool to create a new team. use when setting up a team configuration before adding agents.

ActionInstant

Create Webhook

Tool to create a new webhook for call or lead events. use when you need to receive real-time notifications on specific events. example: "create a webhook for call completed events to http://example.com/callback".

ActionInstant

Delete Agent

Tool to delete an agent. use when permanently removing an agent after confirming the agent id.

ActionInstant

Delete Client

Tool to delete a client. use when you need to remove an existing client from your account after confirming its id.

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 Callingly

Connect any two apps with Notis in the middle.

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