Set the rule. Skip the follow-up.

Any major HR event: a review cycle opening or closing, a goal check-in becoming overdue, an onboarding milestone passing, a competency rating being submitted, a development plan milestone reaching its due date, or a custom date offset from any of the above. New trigger types ship continuously as the engine matures.

Send an in-app notification or email, create a task assigned to a specific person or role, update a goal's status flag, append an agenda item to an upcoming 1:1, or send a webhook payload to an external URL. Multiple actions can be chained to a single trigger.

Yes. Rules can be saved in draft mode and run against a dry-run test that previews which records would be affected and what actions would fire — without executing anything. The run history log shows actual vs. dry-run executions separately.

Only Admin and HR roles can create, edit, enable, or disable rules in the Automation admin panel. Managers can view the run history for rules that affected their direct reports. Employees see the outcomes (notifications, tasks) but not the rule configuration.

Yes. Every rule execution is logged with a timestamp, the trigger event, the records it matched, and each action's outcome (success, skipped, or error). Admins can view the full run history filtered by rule, date range, or employee. Employees can see automations that ran on their behalf in their personal activity feed.

No. The automation engine runs asynchronously and never blocks the main request path. Actions execute in the background. If an action fails (e.g., a webhook timeout), it retries automatically and logs the failure — the underlying HR workflow is unaffected.