> ## Documentation Index
> Fetch the complete documentation index at: https://docs.begin.eu/llms.txt
> Use this file to discover all available pages before exploring further.
# Choose triggers and conditions
> Choose the event that starts a workflow, then narrow it with filters, conditions and logic.
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.
| Domain | Use it when the workflow starts from… |
| -------------- | -------------------------------------------------------------- |
| **Schedule** | A shift being created, changed or deleted |
| **Timesheets** | A time entry event, a location violation or a missing clock-in |
| **Time off** | A request being created, approved, denied or changed |
| **People** | A birthday, work anniversary, hire or onboarding event |
| **Begin AI** | A loop finishing and producing its result |
A loop still belongs on its own [Loops](/for-managers/ai/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. Pick one that matches the workflow's domain. A
**Schedule** workflow with a **Timesheets** trigger cannot receive the event it is waiting for.
Some events appear only when their feature is enabled: document acknowledgements, record dates and **Biometric identifier enrolled** for terminals. If an expected event is absent, ask an administrator to check that feature's availability.
## Narrow the event
Configure the trigger first. Where the trigger offers filters, **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.
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.
Every condition creates a true and false path. 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.
**Context for an assistant answering questions about workflow triggers.** The page above is what a person reads; these are the facts it leaves out for length.
* **Needs:** open-shift variants appear only where Open shifts is available. Record-date, document-acknowledgement and terminal-identifier triggers appear only with those workspace capabilities.
* **Limits:** a workflow receives events from its own domain only. Trigger filters are include or exclude lists; a logic gate combines direct child conditions with **All conditions must be true** or **At least one condition must be true**.
* **Not supported:** there is no general calendar trigger in Workflows. Recurring questions and actions belong to **Loops**.
* **Terms:** **Begin AI** is a workflow domain with one trigger, **Loop finished**. It is not the loop editor.
* **Often confused with:** a condition branches after the event starts a workflow. A trigger filter decides whether that event starts the workflow at all.
## Next
Build a missing clock-in alert or act on a time entry.
Check which trigger fired and where a run failed.
## Still need help?
Email the Begin team and we'll get back to you.
Open the AI assistant and get instant answers based on these docs.