Overview
With automations you create if-then rules without programming: a trigger — such as patrol missed or incident created — starts the rule, optional conditions narrow it down, and actions notify the right people or start follow-up steps. In the graphical workflow editor you connect the building blocks on a canvas; a test run shows before saving what would happen — without anything being sent.
Triggers from day-to-day operations
Rules react to events from every part of LiteLog:
- ✓Patrols & checkpoints: missed or completed patrol, missed checkpoint
- ✓Incidents: new or classified occurrences
- ✓Forms & quality: submitted forms, detected defects, score below threshold
More than notifications: automatic follow-up actions
Rules can act directly instead of just informing:
- ✓Create task — e.g. an incident or a form defect automatically becomes a task
- ✓Assign task or change phase — tasks keep moving without manual work
- ✓Open incident — e.g. when an attendance requirement was missed
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:
- ✓Push notification
- ✓In-app notification
Created by AI, verified with a test run
Describe in your own words what should happen — the AI builds a draft rule that you review and deliberately enable. Alternatively, start from ready-made templates. The editor continuously validates every rule, the test run simulates it without side effects, and the history shows every execution including recipients and deliveries.
FAQ
Frequently asked questions about LiteLog
Do I need programming skills for the automations?
No. Rules are assembled from cards in the graphical editor or created by AI from a text description. You pick conditions from lists that match the respective trigger.
Which channels can LiteLog notify on automatically?
Email, push notification, and in-app notification are included in all packages. SMS and automated calls are available with the SMS add-on.
Can LiteLog create tasks automatically?
Yes. A rule can automatically create a task from an incident or a detected form defect, assign it to a person, or change its phase. These follow-up actions are part of the larger packages.
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.