Automation engine feature
Automation instances form the operational core of the Pulse automation engine. They are created from predefined templates, inheriting their structure and default settings to ensure consistent and scalable workflows. Users with the required permissions can quickly generate new instances from any template, enabling a fast start for course-wide automations.
At the instance level, all template values can be adjusted to meet specific course or activity needs. Once configured, automation instances are triggered automatically based on their defined conditions.
The overview interface provides full transparency by allowing users to view, sort, and manage all existing instances. Key actions include editing settings, duplicating instances, accessing reports, controlling visibility, and removing outdated or unused instances.
Each automation instance can be named, annotated with internal notes, configured with a frequency limit, disabled when not needed, tagged for easier organization, and – when using Moodle Workplace – made available to selected tenants.

Course creators can search for automation templates, use them as their own instances, and modify them to fit their needs.