Overview

This guide describes Automation Rules (event-driven automations) and Rules Event Logs (audit trail of rule runs). It reflects how the feature works in the SandsBytes application today.

In This Section

Events — what system events are and how to select event category and event type in the rule wizard.
Conditions — Active, time frame, and payload filter checks before the action runs.
Actions — Email, Webhook, and Workflow actions and how to configure them.

Introduction

Automation rules watch for specific events in the system (for example, when a record is created, updated, or deleted). When an event fires, the system:

Finds active rules that match the event’s category and type.
Checks each rule’s schedule (active days and time window).
Evaluates conditions against the event payload (the data associated with the change).
For every match, runs the rule’s action (for example: send email, call a webhook, start a workflow).

Creating or Editing a Rule

To create a rule:

In the main sidebar, select Rules (sparkles icon).
In the page header, choose Create Rule. A stepped form opens: Metadata, Triggers, then Actions.

Metadata fields are Name, Tags, Description, Active days (Sunday through Saturday), an Active checkbox, and an active window (Active start and Active end, HH:MM:SS). Defaults are all seven days, active, from 00:00:00 through 23:59:59.

Edit an existing rule: To edit a rule, open the row menu on the list and choose Edit; the same stepper loads with the rule’s saved values.

Automation Rules page: Rules selected in the sidebar, list of rules with event and action summary, and Create Rule button in the header next to Event Logs

Rules Event Logs

Purpose

Each log row is one rule execution attempt for an event:

When it started (triggered_at) and finished (resolved_at).
Event (event_category, event_type).
Rule (rule_id) and snapshot (rule_info: name, conditions, rendered action_config, schedule flags, etc.).
Payload for the matched event.
Action type and status; on failure, an error message.

Status Values

Status	Meaning
`in_progress`	Action running or interrupted before finalization (normally transitions).
`success`	Handler finished without an exception.
`failed`	Handler or config rendering failed; see `error`.

Browsing Event Logs Page

To open the list of event logs:

In the sidebar, go to Rules.
In the top right of the page header, click Event Logs.

Automation Rules list with Rules selected in the sidebar and Event Logs highlighted in the header next to Create Rule

A list of all event attempts will be shown in the table. Hover over any row and click View Details.

Rules Event Logs table listing triggered events with columns for time, rule name, trigger, action type, status, and View Details on a row

This will display the window for Event Details, which shows all the rule and event details, including the event information, conditions, and payload.

Event Details modal with rule name, status, triggered time, event trigger, action dispatched workflow JSON, and action payload JSON with copy controls