Skip to content
Notis

Connect Zendesk to Clientary

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

View example

Turn New Zendesk Users into Clientary Clients

Create a Clientary client whenever a new Zendesk user appears, using available company and contact details.

View example

Add Zendesk User Contacts to Clientary

Create a Clientary contact for a matching client when a Zendesk user is created.

View example

Capture New Zendesk Users as Clientary Leads

Create a Clientary lead from a new Zendesk user when the person may represent a sales opportunity.

View example

Start Clientary Projects for New Accounts

Create a Clientary project when a new Zendesk user signals a new account or engagement.

View example

Create Clientary Onboarding Tasks from New Users

Create a Clientary task for onboarding follow-up when a new Zendesk user is created.

View example

Turn Zendesk Tickets into Clientary Tasks

Create a Clientary task from each new Zendesk ticket so operational follow-up is visible outside support.

View example

Record Ticket Related Costs in Clientary

Create a Clientary expense when a new Zendesk ticket contains a documented customer related cost.

View example

Send Clientary Invoice Messages from Zendesk Tickets

Send an invoice message through Clientary when a new Zendesk ticket requests billing information or payment follow-up.

View example

Look Up Clientary Invoices for Zendesk Billing Tickets

Retrieve the relevant Clientary invoice details when a new Zendesk ticket asks about billing or payment status.

Supported Triggers and Actions

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

Zendesk triggers

Clientary actions

Recurring trigger

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

TriggerScheduled

Create Client

Tool to create a new client record in Clientary. Use when you need to add a new client to the system with company details and contact information.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Contact

Tool to create a new contact within a specified client. Use when you need to add a contact to a client account with name and email as required fields.

ActionInstant

New User Created

Triggered when a new user is created in Zendesk.

TriggerInstant

Create Expense

Tool to create a new expense record in Clientary to track expenditures within your account. Use when you need to record expenses, optionally assigning them to specific clients or projects. Requires an amount field.

ActionInstant

New Zendesk Ticket

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

TriggerPolling

Create Lead

Tool to create a new lead record in Clientary. Use when you need to add a new lead to the system with company details and contact information.

ActionInstant

Create Project

Tool to create a new project in Clientary with name and rate. Use when you need to set up a new project for tracking time, expenses, or managing client work.

ActionInstant

Create Task

Tool to create a new task in Clientary. Use when you need to create a task with a title, optionally associating it with a project and assignee.

ActionInstant

Delete Client

Tool to remove a client and all associated projects, invoices, estimates, and contacts. Use when you need to permanently delete a client from Clientary. WARNING: Deletions are permanent and not reversible.

ActionInstant

Delete Lead

Tool to permanently delete a lead and all associated Estimates and Contacts. Use when you need to remove a lead that is no longer needed. Warning: This action is irreversible.

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 Clientary

Connect any two apps with Notis in the middle.

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