Unit 3 Review Video Script
Cold Open
ON SLIDE | NARRATION
Unit 3 Review | You have the building blocks now. In this unit, you move from simple ideas to working automations. You connect apps, move data, add logic, and fix problems when a workflow does not run as planned.

3a
ON SLIDE | NARRATION
Trigger → Action → Result | To build a basic workflow, you start with a trigger and add one or more actions. Free no-code platforms give you visual tools so you can create these steps without writing code. The key idea is to set up a clear flow from event to result. [3.1 Getting Started with No-Code Platforms]

To review, see: [3.1 Getting Started with No-Code Platforms]
3b
ON SLIDE | NARRATION
Connect applications | A workflow becomes more useful when you connect applications. You can send information from one app to another and map fields so the right data goes into the right place. This helps you build an end-to-end process that moves work across tools with less manual effort. [3.2 Connecting Applications and Moving Data]

To review, see: [3.2 Connecting Applications and Moving Data]
3c
ON SLIDE | NARRATION
Conditional logic | Workflows often need choices. Conditional logic lets your automation take different paths based on the data it receives. You can also handle data by checking values, using them in later steps, and sending the right outcome for each case. [3.3 Adding Conditional Logic]

To review, see: [3.3 Adding Conditional Logic]
3d
ON SLIDE | NARRATION
Troubleshoot workflow issues | When a workflow fails, you can troubleshoot by checking platform history, logs, and testing tools. These features help you see what happened, where the process stopped, and what data moved through each step. Careful testing makes it easier to find and fix workflow construction issues. [3.4 Troubleshooting Common Workflow Issues]

To review, see: [3.4 Troubleshooting Common Workflow Issues]
Close
ON SLIDE | NARRATION
Unit 3 complete | You have now reviewed the core skills for building no-code automations in this unit. Keep practicing with simple workflows first, then add connections, logic, and testing as you grow. Return to the unit readings and video resources to strengthen each step.

Last modified: Thursday, 18 June 2026, 1:28 PM
Callback before_footer in local_aigrade component should be migrated to new hook callback for core\hook\output\before_footer_html_generation
  • line 7225 of /lib/moodlelib.php: call to debugging()
  • line 7292 of /lib/moodlelib.php: call to {closure}()
  • line 71 of /lib/classes/hook/output/before_footer_html_generation.php: call to get_plugins_with_function()
  • line 987 of /lib/classes/output/core_renderer.php: call to core\hook\output\before_footer_html_generation->process_legacy_callbacks()
  • line 94 of /mod/page/view.php: call to core\output\core_renderer->footer()