Automation & Workflows
If the patrol is missed, then SMS to the on-call team; if a report has severity “high”, then a task for the site manager: you build such if-then rules in the graphical editor without programming — on request, the AI creates the rule from a single sentence.
Overview
With automations you set up if-then rules without programming. A trigger such as patrol missed or incident created starts the rule. Optional conditions narrow it down. Actions notify the right people or start follow-up steps. In the graphical workflow editor you connect the building blocks on a canvas. The fastest start is a ready-made recipe from the template catalog – or you describe to the AI in one sentence what should happen. A test run shows what would happen before saving – without sending anything.
Ready-made recipes: adopt proven chains with one click
Triggers from day-to-day operations
Rules react to events from all areas of LiteLog:
- ✓Operations: missed or completed patrols, missing checkpoints, new or classified incidents, submitted forms
- ✓Staff: missing check-in or check-out, missed attendance requirement, scheduled shift start and end, absences
- ✓Safety & tasks: welfare check with pre- and main alarm, SOS emergency call, overdue or completed tasks, breached service levels
More than notifications: automatic follow-up actions
Rules can not only inform but act directly:
- ✓Create a task, assign it, or change its phase — e.g. an incident or a form defect automatically becomes a task
- ✓Open an incident — e.g. when an attendance requirement was missed
- ✓AI classification — incidents are automatically triaged by severity and category, and rules react to the triage
Escalation chains that never sit idle
For critical events you build multi-level chains: first, a group is offered the takeover — the first acceptance wins. If nobody reacts, the rule waits a defined time, checks the current state, and only then notifies the next level. These channels are available:
- ✓Email, push, and in-app notification in all plans
- ✓SMS and automatic call with the SMS add-on
- ✓Before each level: waiting time and a fresh check of the current state
Create an automation with AI – one sentence is enough
Describe in one sentence what should happen – for example: “When a patrol is missed, notify the property manager via SMS.” Via Create automation with AI, the AI builds a complete rule draft with trigger, conditions, and actions. You review the draft and activate it deliberately. The editor continuously checks every rule for errors, the test run simulates it without side effects, and the history shows every execution including recipients and deliveries. How the AI triages incoming incidents is shown by AI incident categorization.
FAQ
Frequently asked questions about LiteLog
Do I need programming skills for automations?
No. Rules are assembled from cards in the graphical editor or created by the AI from a text description. Conditions are picked from lists that match the selected trigger.
Are there ready-made automation templates?
Yes. The template catalog contains ready-made recipes for incidents, attendance, patrols, safety, quality, and tasks – from AI triage with escalation to the call and SMS chain on a welfare-check main alarm. One click adopts the template as a draft, which you adapt to your properties and recipients and then activate.
Through which channels can LiteLog notify automatically?
Email, push notification, and in-app notification are included in all plans. SMS and automatic calls are available with the SMS add-on.
Can LiteLog create tasks automatically?
Yes. A rule automatically creates a task from an incident or a defect detected in a form. It can also assign the task to a person or change its phase. These follow-up actions are part of the larger plans.
What happens if nobody reacts to an alarm?
That is what escalation chains are for: the rule first offers the takeover to a group — the first acceptance wins. If nobody reacts, the rule waits a defined time, checks the current state, and only then notifies the next level.
Are notifications sent twice when data is synchronized multiple times?
No. The same event triggers a rule only once, and failed deliveries are retried automatically.