Overview
The Rules Engine lets you define conditions and actions that fire automatically β no code required. Rules can trigger on document events, case status changes, or a recurring schedule. Navigate to Rules Engine in the sidebar to manage your rules.Trigger Types
π₯ Document Event
Fires immediately after a document is processed and reaches Ready status. Available events:document_readyβ fires after every successful AI extraction
π Case Event
Fires when a case changes to a specific status. Available events:
Use case: Auto-approve documents when their linked case is resolved. Trigger webhooks to external systems on case completion.
β° Schedule (Heartbeat)
Scans all documents on a recurring timer. Configure the interval in minutes (e.g. every 60 minutes). The rule evaluates every document that matches its conditions on each scan. Use case: Alert on documents stalled in Needs Review for more than 3 days. Weekly compliance checks.Conditions
Each rule supports up to 5 conditions combined with AND logic.Actions
Multi-Step Approval Workflows
Case-event rules enable chained automation across documents and cases. Example: Low confidence β human review β auto-approveLoop Protection
The Rules Engine includes automatic loop detection. If a rule chain triggers itself recursively, execution stops after 5 levels of depth. Example of a loop that would be caught:Default Rules
Every fresh RecordEngine deployment seeds 3 default rules:
These can be edited, disabled, or deleted from the Rules Engine page.
Execution Log
Every rule firing is recorded in the Rule Execution Log at the bottom of the Rules Engine page. Each entry shows:- π₯ Document event / π Case event / β° Heartbeat icon
- Rule name and document/case it fired on
- Action taken and whether it succeeded
- Timestamp