Automation triggers, conditions, and actions reference

Concept · Audience: tenant-admin · Permissions: automation.view, automation.create · Route: /dashboard/automation

The complete, exact list of what an automation can currently watch for and do.

What this does

Lists every trigger and action Staffintra's automation engine currently supports, and exactly how the optional condition filter works.

Who can do this

Anyone with automation view/create access.

Triggers (4, event-based — no time/schedule trigger exists)

• User Created — a new staff member is added.

• Onboarding Started — an onboarding instance is initiated.

• Asset Unreturned — checked at the moment offboarding is initiated for someone, if they still have assets assigned.

• Task Overdue — a background check finds a task past its due date (detected periodically, not instantly).

Actions (5)

• Notify User — in-app notification, with email, to the specific person from the trigger.

• Notify Admin — the same, sent to every active admin/super-admin in your workspace, capped at 10 people.

• Assign Onboarding Template — creates a real onboarding instance from a template you specify by its ID.

• Assign Asset — assigns a specific asset, by ID, to the person — only works if that asset is currently in "available" status.

• Block Offboarding — records a log entry noting the offboarding was blocked; the actual block already happens automatically when unreturned assets are found — this action's value is the log trail and optional admin notification.

Condition Filter

A single optional field/value check — a rule only fires if that one field in the triggering event matches the value you set (for example, department = Engineering); leaving it blank means the rule always fires when its trigger occurs.

Important notes

• A rule only ever checks ONE condition field — there is no way to combine multiple conditions (AND/OR) currently.

• Assigning a template or an asset requires typing its exact ID — there is no picker to search by name in the automation form itself; find the ID from the Onboarding Templates list or the Assets list first.

• Automations execute immediately in-process when their trigger fires (except Task Overdue, which depends on a periodic background check) — there is no separate queue or delay.

• The engine automatically ignores a duplicate firing of the same rule for the same person within a 10-second window, so a rapid double-trigger doesn't produce two notifications or two assigned assets.

• A failed action is logged as an error and does not automatically retry.

• At most 5 active rules are evaluated per trigger event — if you have more than 5 rules on the same trigger, only the 5 oldest (by creation date) run.