Automations in Elementum are event-driven rules that execute programmatic actions in response to data changes, workflow state transitions, or time-based triggers. Configure triggers, conditions, and actions to automate record updates, system integrations, notifications, and AI invocations.

​
Why Automations Matter

Consistency & Reliability

Rules run the same way every time—enforcing business policies and reducing human error.

Speed at Scale

Process high volumes automatically with consistent execution times and parallel processing capabilities.

Cross-System Orchestration

Connect apps and data sources using APIs and prebuilt actions to keep systems in sync.

Human-in-the-Loop

Blend automation with approvals, forms, and assignments where judgment is required.

​
Core Building Blocks

Triggers

Start automations on record changes, status transitions, comments, file events, or schedules.

Conditions

Target the right scenarios with filters, comparisons, and Branch (if/else) logic.

Actions

Update fields, create related records, send notifications, request approvals, call webhooks, or invoke AI.

Schedules & SLAs

Time-based triggers and deadline tracking to escalate or remind when work is overdue.

Error Handling

Built-in retries and failure paths keep processes resilient; log outcomes for audits.

Observability

View automation runs, success rates, and bottlenecks to improve reliability.

​
Implementation Examples

SLA Escalation

Trigger: Scheduled (hourly)
Condition: Status = “Open” AND Assigned = null AND Created > 2 hours ago
Actions: Send notification to team, update priority to “High”, assign to manager

System Integration

Trigger: Field change (Status → “Approved”)
Condition: Record type = “Contract”
Actions: HTTP POST to ERP webhook, Teams notification with contract details, update audit log

Validation Pipeline

Trigger: Record submission
Condition: Required fields populated
Actions: Run AI classification, validate against business rules, block progression if validation fails

Data Processing

Trigger: File upload event
Condition: File type = PDF
Actions: Extract text via OCR, populate structured fields, create follow-up task with extracted data

​
Automation Patterns

​
Design Principles

  • Single responsibility: Each automation should handle one specific business rule or process step
  • Idempotency: Design actions to be safely repeatable—multiple executions produce the same result
  • Observability: Log execution details, measure success rates, and monitor performance metrics
  • Failure resilience: Implement retry policies, error handling, and dead letter queues for failed operations
  • Testability: Use staging environments and test data to validate automation behavior before production
Performance tip: Batch similar operations and use conditional logic to minimize unnecessary executions. Monitor automation frequency to avoid overwhelming system resources.

​
Technical Implementation

​
Next Steps

Automation System

Deep dive into triggers, conditions, and actions.

Automation Triggers Reference

Browse all available triggers with configuration examples and use cases.

Automation Actions Reference

Browse all available actions (updates, integrations, AI, and more).

API Reference

Trigger workflows and actions from external systems.

Collaboration & UX

Design human-in-the-loop steps that pair with your automations.

Core Concepts

See how Automations fit with Apps, Elements, AI, and Collaboration.