Automation engine feature
Conditions act as triggers for automations and are based on specific user actions, course states or scheduled moments. Define the trigger conditions that activate an automation within an instance. You can select one or multiple of the following options:
- Activity completion – Triggers automation based on activity completion, including partial completion, pass/fail status, or activity count thresholds.
- Cohort membership – Triggers automation when a user belongs to a selected cohort.
- Course completion – Triggers automation when the entire course is marked as completed.
- Course dates – Trigger automations automatically on course start or end dates.
- Course due date – Triggers automation when the course due date is reached. – Requires Timetable
- Course group – Restrict automations to learners based on course group or grouping membership.
- Enrolments – Triggers automation when a user is enrolled in the course.
- Events – Triggers the automation when selected events occur. Control which events are available and restrict triggers to the entire course or a specific activity.
- Session – Triggers automation when a session is booked within the course. – Requires Facetoface
- User inactivity – Trigger automations when learners are inactive based on course access or activity completion – with optional prior activity checks.
The trigger operator defines how your selected conditions are evaluated: choose Any to activate the automation when at least one condition is met, or All to require that every selected condition occurs simultaneously.
Pro tip: Event-Based Automations
When an event is triggered by a plugin, it can serve as a condition to start an automation. You can define how often the automation should be triggered using the frequency setting.
For example, if the event occurs when a user submits a Choice activity and earns credits for it, the frequency can be set to unlimited so that the automation triggers every time the event happens. Alternatively, you can specify a numeric limit — for instance, granting credits only for the first submission, the first five, or any other defined number of occurrences.
This flexibility allows you to precisely control how frequently automations respond to recurring events, ensuring that rewards or actions are triggered exactly as intended.