Skip to content
omnismith docs

Automations Workflow

Automations allow you to build event-driven workflows that execute automatically whenever entity records are created, updated, or when specific metric thresholds are breached.

1. Automation Architecture: Trigger → Condition → Action

Section titled “1. Automation Architecture: Trigger → Condition → Action”

Every automation rule consists of three core components:

flowchart LR
    A["Event Trigger\n(Entity Created / Updated)"] --> B["Condition Evaluation\n(e.g. Status = Degraded)"]
    B -->|Match True| C["Action Execution\n(Webhook / Telegram / Push)"]

1. Triggers

Section titled “1. Triggers”
  • On Entity Created: Fires immediately when a new entity is created under a specified template.
  • On Entity Updated: Fires whenever an entity record is modified.
  • On Attribute Changed: Fires only when a specific attribute value changes (e.g. when Status changes from Online to Offline).

2. Conditions

Section titled “2. Conditions”

Filter rule evaluation using logical operators:

  • Equals, Not Equals
  • Greater Than, Less Than, Greater or Equal, Less or Equal
  • Contains, Not Contains
  • Is Empty, Is Not Empty

3. Actions & Channels

Section titled “3. Actions & Channels”
  • Telegram Channel: Sends formatted messages to Telegram chats/groups via a bot.
  • Webhook Channel: Sends HTTP POST JSON payloads to external APIs, Zapier, or microservices.
  • Push Notification Channel: Sends instant push notifications to team members’ Android mobile devices via Firebase Cloud Messaging (FCM).

2. Step-by-Step Automation Setup

Section titled “2. Step-by-Step Automation Setup”
  1. Navigate to Automation → Search.
  2. Click + Create Automation.
  3. Basic Settings: Enter a name (e.g., Critical Server Offline Alert) and select the target Template (e.g. Server Node).
  4. Select Trigger: Choose On Attribute Changed and select Status.
  5. Add Conditions: Set rule Status Equals Offline.
  6. Configure Action:
    • Select notification target channel (e.g. DevOps Telegram Bot or Mobile Push).
    • Custom template message using dynamic field placeholders (e.g. Alert: Server {hostname} status changed to {status}!).
  7. Click Save & Enable.

Automation builder screen showing trigger, condition, and action setup

3. Execution Logs & Monitoring

Section titled “3. Execution Logs & Monitoring”

Under the Executions tab of any automation rule, you can inspect execution logs:

  • Success: Action delivered successfully.
  • Failed: Action failed (e.g. HTTP 500 from Webhook URL or invalid Telegram chat ID). Inspect raw error payloads for troubleshooting.
  • Partial Failure: Some target channels succeeded while others failed.

💡 Developer Architecture Note

Section titled “💡 Developer Architecture Note”

[!NOTE] Asynchronous Kafka Event Bus: Automation triggers are evaluated asynchronously over a distributed Kafka consumer bus (consumer-audit-log, consumer-mailer). This ensures zero latency impact on user API requests or entity save operations.

Next Steps

Section titled “Next Steps”

[!TIP]