Automation Engine

Real automation. No Zapier in between.

Every 5 minutes, scheduled rules check trigger → optional condition → action against your tasks. Reassign overdue work. Notify on QC requirement. Escalate blocked tasks. Built into the database, not bolted on.

Read-only demo · no signup · realistic seeded records

Automation engine panel showing scheduled rules with trigger, condition, action, and dry-run toggles
Captured from a real seeded Azora workspace.

How it works

Trigger → Condition → Action → Notify.

A cron worker on the same VPS as your app runs every 5 minutes. It scans your active rules, evaluates each rule's trigger and optional condition against the current task table, and applies the configured action. No webhook duct tape. No 30-second polling. No third-party service hosting your automation logic.

01

Rich triggers

Field changes (status, priority, assignee, project). Time-based (overdue by N days). Aggregate (sprint with > 80% blocked).

02

Compound conditions

Optional secondary check after trigger fires. AND-combined with trigger for precise targeting.

03

Three action types

update_status, reassign, notify (in-app + email). All one DB transaction. update_priority and add_label are on the roadmap.

04

QC gate respected

Engine never auto-Done's a task with requires_qc=true unless it's already Under Review. Same rule the UI enforces.

05

Per-tenant isolation

Rules are scoped to tenant. Engine groups by account_id and processes each tenant's tasks separately.

06

Dry-run + caps

AUTOMATION_DRY_RUN env flag for safe testing. 100-action-per-rule-per-tick cap so a misconfigured rule can't empty your table.

Connected workflow

Automation Engine works better when the context travels with it.

Azora keeps project work, quality evidence, people, suppliers, units, documents, and customer context on one shared operating core—without a sync job between every team.

  1. 01
    Rich triggers

    Field changes (status, priority, assignee, project). Time-based (overdue by N days). Aggregate (sprint with > 80% blocked).

  2. 02
    Compound conditions

    Optional secondary check after trigger fires. AND-combined with trigger for precise targeting.

  3. 03
    Three action types

    update_status, reassign, notify (in-app + email). All one DB transaction. update_priority and add_label are on the roadmap.

  4. 04
    QC gate respected

    Engine never auto-Done's a task with requires_qc=true unless it's already Under Review. Same rule the UI enforces.

“We had Zapier zaps falling over silently for months. Now our automation runs on the same DB as our work — when it fires it actually fires, and when it doesn't I can see why in the logs.”
Hassan · AI/Software Engineer at Azora Optical Solutions — the team that built Azora
5 minTick interval
100Action cap per rule per tick
0Third-party automation services required
Open beta nowFree, demo-first, and sales-provisioned within 24 hours.

At GA: one plan, every module—$29/paid editor/month annually or $35 monthly, 30-day full-feature trial, unlimited free read-only viewers, and a 5-editor minimum. Open-beta design partners lock $20/editor/month annually for 24 months from GA.

See it before you talk to sales

Automation that lives in your DB.

The demo tenant includes sample rules and a dry-run dashboard so you can see triggers fire without writing data.