Automations

Automations run work that would otherwise need someone to remember it. You set a trigger and an action, and eFirm does the rest whenever the trigger fires.

Triggers and actions

An automation is a pair: something that happens in the firm, and something HAQQ does in response. The release that introduced them gives the shape as when a task is created → send a notification. Once an automation is active it runs on its own, without anyone opening it.

Test before you activate

An automation can be tested before it is switched on, so the first time it runs is not on a live matter. This matters more than it sounds: an automation that fires on the wrong trigger is not a silent failure — it does something, to real records, repeatedly.

Enable and disable at any time

Automations can be turned off and back on without being deleted, so a workflow that is wrong for one month of the year does not have to be rebuilt for the other eleven.

Runs

Automations has a second tab, Runs, holding the history of what each automation has actually done. An automation that is quietly failing looks identical to one that has had nothing to react to — the run log is what separates them.