Skip to main content
A Long time entry workflow linking Time entry stopped, Duration over 8h and Notify manager A Long time entry workflow linking Time entry stopped, Duration over 8h and Notify manager A trigger is the event that starts a workflow. Filters and conditions then decide whether the event should reach an action, such as sending a notification or requesting approval.

​
Match the trigger to its domain

Choose the domain when you create the workflow, then add a trigger from the same part of Begin. A loop still belongs on its own Loops page. A workflow in the Begin AI domain reacts after that loop finishes; it does not choose what the loop asks, when it runs or who can see it.
The trigger picker shows events from every domain, and a workflow only hears events from its own domain. When a new workflow gets its first trigger, it takes that trigger’s domain. Replacing the only trigger with one from another domain asks before it changes the workflow’s domain, and a published workflow then needs publishing again. Adding a trigger from another domain beside the ones already there is refused, because all of a workflow’s triggers share one domain. Pause an active workflow first, and note that a built-in workflow keeps its domain.
Some events appear only when their feature is enabled: document acknowledgements and Biometric identifier enrolled for terminals. If an expected event is absent, ask an administrator to check that feature’s availability. Record date approaching is always listed, but it fires only for record dates your workspace has set up.

​
Narrow the event

Configure the trigger first. Where the trigger offers filters, open Advanced in its settings: Include runs it only for matching people or work, while Exclude runs it for everything else. The available filters can include positions, locations, departments, roles and named members. A department filter reads a shift or time entry by its position’s departments, and anything without a position by the person’s own departments. Add a condition when the event itself is not enough. Conditions can check schedule facts such as shift duration or member position, and timesheet facts such as entry status, duration, clocking location or the difference between scheduled and actual time. To act on one kind of change, trigger on the update and add Field changed. Shift updated with Field changed on Start time runs only when the start moved, not when somebody edited a note. To catch a move of either end, put Start time and End time in a Logic gate with Pass when set to Any. Every condition creates a true and false path. Under Advanced, turn on Only continue when true when the false path should stop there. Use a Logic gate when all of several checks must match, or when any one of them is enough. Block settings for a time-entry duration condition and its true and false paths Block settings for a time-entry duration condition and its true and false paths

​
Next

Timesheet workflows

Build a missing clock-in alert or act on a time entry.

Execution history

Check which trigger fired and where a run failed.

​
Still need help?

Contact support

Email the Begin team and we’ll get back to you.

Ask Begin AI

Open the AI assistant and get instant answers based on these docs.