Skip to main content

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
Use case: Flag low-confidence documents, create cases for review, move documents to folders, notify your team.

πŸ“‹ 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-approve
When a document extracts at 65% confidence, Rule 1 creates a High-priority case. An accountant reviews the document, resolves the case. Rule 2 fires and auto-approves the document. Rule 3 fires and exports to QuickBooks.

Loop 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:
The system logs a warning and stops execution at depth 5. No infinite loops are possible.

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
The Automation Flow graph in each document’s detail view shows the visual chain of events for that specific document.

API

Rules can also be managed via the REST API. See API Reference β†’ Rules for full endpoint documentation.