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

Testing a rule safely

There is no dry-run switch for automations, so test with a rule that can only reach you.

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

An active automation acts on real events, and there is no mode that evaluates a rule without running its actions. The safe way to try one is to point it at yourself first.

1. Send it to yourself

While you build the rule, send every email to A custom address - your own - or use Notify the workspace owner. For a webhook, use an address you control and can watch.

2. Make the event happen

Do the thing that raises the event, on a record of your own. A test contact is the cheapest - creating one raises Contact created. An invoice issued for a test is a real invoice with a real number, so choose the event with that in mind. Automations run in the background; give it a moment.

3. Read the run

Open View runs on the rule's row. A run marked OK did everything it was asked; a Failed run says what went wrong. No run at all means a condition did not hold - or the event was not the one you expected.

4. Point it at the real recipient

When it behaves, change the recipient and save. Disable on the row pauses a rule without losing it.

Careful: An SMS or WhatsApp message spends a credit whether it is a test or not.

Was this page useful? You will be asked to log in first.
← Previous
WhatsApp templates & SMS
Next →
Reading the run log