How automations work

Automations are if/then rules that run your busywork: When something happens, If it matches your conditions, Then Vivotics acts. Admins manage them under Work > Automations.

The three parts of a rule

1. Trigger (When): a task is created, a status changes, a task is assigned, a task comes due within 24 hours, a deal changes stage, a ticket arrives, an invoice goes overdue, or a form is submitted.
2. Conditions (Only if, optional): narrow by project, priority, status or deal stage. A rule with no conditions fires every time its trigger does.
3. Actions (Then): one or more things to do, executed in order. See Triggers, conditions and actions for the full list.

An example

When a task status changes, if priority is high, then email the project client and add a comment.

Build it in the visual builder in under a minute: no code, just dropdowns.

The run log

The Automations page shows every rule with its run count and last run, plus a Recent runs table (which rule fired, on what record, success or failure). If a rule seems quiet, check the log first.

Safety rails

• Rules are company-scoped: your rules never touch another workspace.
• A rule fires at most once per record per event, and chains cap at a safe depth, so two rules cannot ping-pong forever.
• Toggle any rule off with its switch; nothing is deleted.

Time-based triggers

"Due within 24 hours" and "invoice overdue" are evaluated hourly by the scheduler, and fire at most once per day per record. Self-hosting? Make sure cron is running.