Watchers, and the record
Set a watcher on any area and it acts when something changes; every action anyone takes is recorded under one taxonomy; and there is now one place that says what Kabaido tells your team and what your organisation tells its customers.
20 September 2026. Things that matter happen while nobody is looking. A line falls under its reorder point on a Friday afternoon, a quote goes unanswered for a fortnight, a customer who used to order every month quietly stops, a delivery misses the window you promised. Until today Kabaido could switch on exactly four things and nothing else, and the only record of what anybody did was a list of pages they had opened. This release is about both.
Monitors
- A monitor is a watcher you save against an area: a condition, a schedule and what to do when it becomes true. There is a Monitors button in the toolbar of every area that has kinds worth watching, and a summary of all of them in Settings then Notifications.
- Thirteen kinds: stock below a level, a reorder point reached, a customer gone quiet, a customer come back, a quote unanswered, a quote expiring, an order overdue, a delivery late, a service due, a machine idle, a supplier price moved, a signal on a company you are tracking, and any saved list crossing a number you set.
- Watching costs nothing. Every check is a plain query over your own rows, never a model call, and a test fails the build if an evaluator ever reaches for one.
- A monitor cannot tell you the same thing twice. Each kind decides what counts as the same event, and the database refuses the second one rather than the code remembering to.
- Every monitor has a daily limit. When it is reached it stops, records what it would have done and tells you once. A watcher can never mail a customer forty times.
- What it can do: raise a notification, send your customer one of your own templates, draft a purchase order in Source, chase a quote, add a company to an Inspect list, or call your own webhook.
Integrations, honestly
- The catalogue now carries every system this market actually runs, grouped by the product it belongs to, and every entry carries one of four labels: works today, template, via automation, or roadmap.
- Works today means Kabaido code talks to that provider, and the entry names the file that does it. A test reads the disk and fails the build if one of them is a claim with nothing behind it.
- A template is a prepared recipe on one of the open paths with that provider's fields filled in, and it says what you still have to do. A roadmap entry says it is not built and offers a meeting.
- No integration and no API is gated by your plan any more. Plans gate usage and scale. Every plan can connect anything.
- New: your own calendar, so a delivery window or a site visit lands in the diary of the person who has to keep it. An accounting path that raises a draft invoice from an accepted quote or a confirmed order and reads the reference and the paid state back. The wizard embed key and the Commerce site connection, which existed and were nowhere to be found.
- The contact finders are ordinary connections now, in the same list as everything else, with their credentials in a store no member of your workspace can read.
Everything is recorded
- One event name for everything anyone does, in every area, written by one function at the moment it happens.
- No gaps, and that is a fact rather than a promise: a test walks every action in the platform and fails the build on one that records nothing. Anything genuinely exempt is listed with a reason, and the list is capped by a number a reviewer watches move.
- The activity page's team view is no longer pages only: a control chooses pages, actions or everything.
- With Commerce on there is a Customers view, which is the first time you can see what your own customers did on your customer area.
Notifications, both ways
- Settings then Notifications: every kind Kabaido raises to your team, with in app on or off, email straight away or in the daily digest, and an override for any one person.
- Every message your organisation sends its own customers, with its subject and its body editable, a palette of the fields you can drop in, and a preview against a real record of yours rather than a made up one.
- A notification stores what happened and its details rather than a sentence written at the time, so editing a template changes what people read, including on messages already raised.
- With Commerce on, a customer message carries your customer facing brand and links into your customer area. Without it, the same message still goes out under your own logo and colour with the links that already work. Nothing is hidden and nothing is refused.