Skip to content Start from ₹499/year for your first year
Contact us
Nothing fits?
Build a custom pack

Pick modules, wire your own actions and automations. Live in two weeks.

  • Modules The screens your trade needs, switched on.
  • Your words Customers, orders and bills called what you call them.
  • Automations Reminders and follow-ups that run by themselves.
For example
Laundry & dry cleaning
Order Laundry ticket
Talk to us about yours Browse all 32 packs →
ERP packs
Classes & coaching Corporate training Schools & colleges Clinics Diagnostic lab / pathology Vet clinic & pet shop Contractors & site projects Event & wedding planner Gym & coaching Professional practice Property broker Rental & hire Repairs & field service Salon & spa Security & manpower agency Services & appointments Travel agency & tour operator Website Bakery & sweet shop Caterer & tiffin service E-commerce Hotel / guest house PG & student housing Restaurant Shops & counters Association & club Exporter Farmer producer organisation Housing society & RWA Manufacturing Trusts & non-profits Wholesale & building materials
Modules Pricing Desktop & mobile apps Documentation Blog Partners About
Contact us Sign in
Theme

Triggers, conditions, actions

The three parts of every automation, and how they fit together.

Automations Updated 14 September 2026 · 6 min read · Requires: Owner or Admin role

An automation is one event, any number of conditions and one or more actions. When the event happens in your workspace and every condition holds, the actions run. Automations are kept under Workspace → Automations.

Triggers

The trigger is an event the platform raises: an order placed, an invoice issued, a payment received, a contact created, an approval decided - and dozens more from the modules you have switched on, such as a quotation accepted, a lab result verified or a fee falling due. Only events your workspace can actually produce are offered.

Some events come from the calendar rather than a click. A regular check raises them when their moment arrives: a contact's birthday or anniversary, a follow-up falling due, a quotation about to expire, an appointment coming up, or stock below its threshold.

Conditions

A condition compares one field of the event - the invoice total, the contact's name - with a value you type, using equals, does not equal, contains, is greater than, is at least, is less than or is at most. Every condition must hold for the automation to run; with none, it runs every time. To say “this or that”, write two automations.

Actions

  • Send an email - to the contact on the event, the workspace owner or an address you type, with a subject and body that can quote the event's fields.
  • Notify the workspace owner - an in-app notification.
  • Call a webhook - sends the event to a URL of yours as JSON.
  • Text a payment link or WhatsApp a payment link - for invoice events, with the Payment links add-on and an SMS or WhatsApp add-on.

Each action runs on its own: if one fails - a webhook that is down, say - the others still run, and the failure is recorded on that run.

Before you switch one on: There is no dry-run mode. An active automation acts on real events, so point it at yourself first - Testing a rule safely shows how.

Was this page useful? You will be asked to log in first.
← Previous
Full module reference
Next →
Writing a rule