Zapier Triggers help you start automations when something happens inside Kayse.
A Trigger is like a doorbell. 🔔 When a certain event happens (like a new case being added), the Trigger “rings,” and Zapier starts your workflow automatically.
This means you do not need to copy data by hand or remember to update another system. Kayse can notify your other tools right away, so your team stays organized and moves faster. ✅
Below are the main Triggers you can use, plus a few common Zaps we recommend starting with.
This Trigger runs any time a new case is created in Kayse. This can happen from:
Kayse sends Zapier case details like:
Why this matters: You can track new work right away without manual steps.
Example: When a case is created, Zapier can add it to a Google Sheet or post a Slack message to your team.
This Trigger runs when something changes on a case already in Kayse. For example:
Why this matters: It keeps your systems synced so everyone sees the same info.
Example: If a case status changes in Kayse, Zapier can update the matching record in another tool.
This Trigger runs when a case is removed from Kayse.
Why this matters: It helps clean up your other systems so you do not keep old or wrong records.
Example: If a case is deleted, Zapier can remove the matching row in a spreadsheet.
This Trigger runs when a new client is added to Kayse.
It includes client info like:
Why this matters: New clients can be synced everywhere automatically.
Example: When a client is created in Kayse, Zapier can add them to your CRM or contact list.
This Trigger runs when client details are updated in Kayse. For example:
Why this matters: It keeps contact data clean across all tools.
Example: When a phone number changes in Kayse, Zapier updates the same client record in another system.
This Trigger runs if a client is removed from Kayse.
Why this matters: It lets your other tools stay clean, too.
Example: If a client is deleted, Zapier can remove them from a spreadsheet or contact workflow.
This Trigger runs when a case is added to a specific Case List in Kayse.
Why this matters: Lists are often used for campaigns. This Trigger helps you start workflows tied to campaign lists.
Example: When a case is added to a campaign list, Zapier can start a follow-up workflow in another system.
This Trigger runs when a new call is created in Kayse. This includes:
Zapier receives details like:
Why this matters: Call tracking becomes automatic.
Example: When a call starts, Zapier can log it in a spreadsheet or notify your team in Slack.
This Trigger runs when call details change. This usually happens when:
Why this matters: You can automate what happens after calls without chasing updates.
Example: When a call ends, Zapier can send the transcript to storage or alert the case owner.
This Trigger runs when a client uploads a document to a task in Kayse.
Zapier gets:
⚠️ The download link only works for 15 minutes, so your Zap should save the file right away.
Why this matters: Documents get stored automatically, without extra staff work.
Example: When a document is uploaded, Zapier can save it into Dropbox, OneDrive, or Google Drive.
When a document is uploaded, Zapier also sends the file name. Sometimes that name needs cleanup.
✅ Use Formatter by Zapier
Invoice_12345.pdf)_ with - or another format your team likesYou can also add:
This makes files easier to search later. 🔍
If you are just getting started, these are the most useful workflows firms usually set up first:
New Case → Add to Spreadsheet or CRM
Case Updates → Keep Systems in Sync
Case Added to List → Start a Campaign Workflow
Call Finished → Save Transcript and Notify Staff
Client Uploads a Document → Auto-Save It
These Zaps handle the biggest “busy work” tasks and usually create value right away. ✅
Zapier Triggers let Kayse start workflows automatically when key events happen.
👉 Next: check out the 🛠 Zapier Actions Guide to see what you can do once a trigger fires.