Browse all topics

Clientish Automations: Triggers, Steps and Ready-Made Rules

4 min read

See what automations can start from and do in your workspace: 40 triggers, up to 8 steps, ready-made rules and a safe test run.

Automations in Clientish handle the routine follow-ups for you: when something happens, such as an overdue invoice or a new lead, the next steps run automatically. You pick what starts a rule, add checks if you need them, and choose up to 8 steps, from emailing the client to posting in your team chat.

Applies to: Growth, Pro and Enterprise, up to 200 automations per workspace
Who can do it: the workspace owner and admins, and team members whose role has Edit Company Settings

How Do Automations Work in Clientish?

Every automation has three parts: an event that starts it, optional checks that decide whether it should run, and the steps it then takes in order.

Part	What it does
When this happens	The trigger: one of 40 events across orders, invoices, tickets, clients, leads, proposals, subscriptions and incoming messages. Timed triggers wait a set time first, for example 3 days after an invoice is overdue.
Only if	Optional checks, up to 5, such as the service, order status, amount, client, ticket priority, lead source or rating. Leave it empty and the rule runs every time.
Then do this	Up to 8 steps that run in order, chosen from 18 step types. Two of them shape the flow: If / otherwise splits the rule in two, and Wait pauses it for up to 90 days.

What Can Trigger an Automation?

Any of 40 events can start an automation, grouped into eight areas of your workspace, from a new order to a WhatsApp message.

Area	Triggers
Orders (12)	New order, status changes, intake form submitted, delivery approved, changes asked on a delivery or a proof file, client message, client rating, order late, order coming due, order stuck in one status, task overdue
Invoices (4)	New invoice, invoice paid, invoice overdue, invoice coming due
Tickets (5)	New ticket, client reply, ticket waiting for your reply, client rating, ticket closed
Clients (4)	New client, client has not ordered for a while, client has not signed in for a while, and a weekly or monthly schedule for every active client
Leads (6)	New lead, no contact yet, stage change, call booked, call canceled, call missed
Proposals (5)	Accepted, opened for the first time, declined, expired unanswered, no answer yet
Subscriptions (3)	Renews soon, canceled, renewal not paid on time
Live Chat (1)	A WhatsApp, SMS or Telegram message comes in

What Can Clientish Automations Do?

They can email clients and your team, assign work, change statuses, post to your team chat and send messages, without anyone doing it manually.

Email the client or a team member, or notify someone with a bell notification, in the app or in the client portal.
Assign the work, change the order status, move a lead to another stage, change a ticket’s priority, add a tag or an internal note.
Create a task on the order or a to-do for your team.
Post to Slack, Microsoft Teams, Discord or Telegram, send the client an SMS or WhatsApp message, or message them from a WhatsApp, SMS or Telegram number connected in Live Chat.
Send the details to another tool through a webhook.

Ready-Made Automation Templates

The Ready-made gallery has 18 rules you can use as they are or change first, for example Chase an overdue invoice, Welcome a new client, Ask for a review a week after delivery and Escalate a waiting ticket. Each one shows what starts it and what it does before you pick it.

Ready-made automations gallery with search, category filters and rules such as Client asks for changes, each with Preview and Use this

How to Test an Automation Before It Runs

Use Test run: it tries the rule on a real record and shows what would happen, without sending or changing anything.

Test run tries a rule on one of your 25 latest records and shows what each step would do, without sending or changing anything.
Run history keeps the last 100 runs for 30 days, each marked Done, Part failed, Failed or Skipped, with what every step did.
Rules that wait a set time after something, such as an overdue invoice or a quiet lead, only act on what reaches that point after you turn them on, never on what was already waiting.
If the same rule fires on the same record more than 5 times in an hour, the extra runs are skipped, so two rules can’t keep feeding each other.

Automation Not Working? Common Fixes

An automation didn’t run⌄

Open its Run history. A Skipped run shows which check didn’t match; no run at all usually means the rule is paused or the event happened before you turned it on.

One step failed but the others ran⌄

Each step is recorded on its own, so a failed step doesn’t stop the ones after it, and the run is marked Part failed. Failed steps are not retried, so fix the cause, such as a disconnected Slack channel, and the next run will go through.

A webhook step shows an error⌄

The receiving tool has 10 seconds to answer. The run history shows the code it sent back, or that it didn’t answer; check the web address and that the other tool is online.

Create an Automation: build a rule step by step
Email Templates: the emails your workspace sends
Send Events with Webhooks
Workflow automation for agencies