Unit 1: Foundations of No-Code Automation
1a. Differentiate no-code automation from traditional development and summarize its productivity benefits.
How does no-code automation differ from traditional development?
What kinds of work can no-code automation help you do faster?
Why can these tools increase productivity for individuals and teams?
Which approach would you choose when a task changes often, and why?
No-code automation lets you build workflows without writing code, while traditional development usually requires programming. In the unit reading and video, the main idea is that no-code tools make it easier to connect tasks, apps, and data so you can automate repeated work more quickly. Traditional development can be more flexible, but it usually takes more time and technical skill. No-code automation is useful when you want to build or change a workflow faster and with less technical effort.
A key productivity benefit is that no-code automation can reduce manual work. Instead of doing the same steps over and over, you can set up a workflow once and let the tool repeat it for you. That saves time and can also reduce mistakes caused by manual entry. For example, if a process has the same steps every time, automation helps you complete it more consistently. Students often get this wrong by thinking no-code means "less powerful" in every case, but the materials present it as a faster and more accessible way to solve many routine tasks.
Can you see why the best choice depends on the task? If you need speed, ease of use, and simple updates, no-code automation is often a strong option. If a project needs custom code or very complex behavior, traditional development may still be better. The point of this LO is to compare the two approaches clearly and recognize when no-code automation improves productivity.
To review, see:
[1.1 Understanding No-Code Automation]
[1.1 Video What is No-Code Automation? A Beginner’s Guide]
1b. Distinguish among rule-based automations, AI-enhanced workflows, and AI agents.
What makes a rule-based automation different from an AI-enhanced workflow?
How does an AI agent go beyond a workflow that follows fixed rules?
Which type would you use for a task with clear steps, and which for a task with changing content?
If a process must decide what to do next, which type fits best, and why?
Rule-based automations follow fixed instructions: when a trigger happens, the system performs actions you already defined. An AI-enhanced workflow is a workflow that uses AI to help with part of the process, such as creating or changing content, while the rest of the flow still follows set steps. An AI agent is more independent than either of these because it can make decisions and act across a task rather than only following a single fixed path. These three types build on one another, so the main difference is how much judgment and flexibility the system has.
A rule-based automation works best when the task is predictable. For example, if one event always leads to one specific response, fixed rules are enough. An AI-enhanced workflow is useful when the task includes dynamic content, because generative AI can add intelligence where the content must change. By contrast, an AI agent is better when the system must decide among options or handle a task with more open-ended steps. Students often mix up AI-enhanced workflows and agents, but the materials separate them by decision-making: the workflow uses AI inside a controlled process, while the agent can take a more active role.
When you choose among them, ask what must stay fixed and what must adapt. If the process is simple and repeatable, a rule-based automation is enough. If part of the work needs content generation or flexible responses, an AI-enhanced workflow fits better. If the task needs more independent judgment, the agent model is the strongest match. The video and reading in this section make the contrast clear, and the later unit on agents builds on this difference.
To review, see:
[1.2 Types of Automations: Rule-Based, AI-Enhanced, and Agents]
[1.2 Video Types of No-Code Automation: Rule-Based, AI-Enhanced, and Agents]
1c. Identify free tools for building no-code automations, process maps, and AI agents.
Which free tools do the unit materials point you toward for no-code automation work?
What free tool would you use first if you need to map a process before building it?
Which tools help you explore AI agents without paying for a platform?
If you are just starting, how would you choose the right free tool for the job?
The unit materials introduce free tools in three general categories: tools for building no-code automations, tools for creating visual process maps, and tools for working with AI agents. The key point is not to memorize a long list from outside the course, but to recognize that the materials point you toward free options for each stage of the automation process. You first map the work, then build the workflow, and later explore AI behavior if needed.
A free tool is a tool you can use without paying, at least for the basic version or the course activity described in the materials. A process map is a visual picture of the steps in a task, so you can see what happens first, next, and last. These tools matter because they help you plan before you build. If you skip the map, you may miss a step or connect the wrong trigger to the wrong action. Students often get stuck by trying to build too early, so the materials encourage you to identify the right tool for the right stage.
If you are choosing a tool, match it to the task. Use a mapping tool when you need to understand the process. Use a no-code automation platform when you need to connect apps and steps. Use an AI agent tool when the course asks you to experiment with more independent behavior. This LO is about recognition, so focus on identifying the tool type and its purpose, not on inventing features that are not in the materials.
To review, see:
[1.3 Exploring Free No-Code Tools]
[1.3 Video Exploring Free No-Code Tools for Automation]
1d. Describe how generative AI adds intelligence to automated workflows.
How does generative AI change a workflow that would otherwise follow fixed rules?
What kind of tasks become possible when AI is added to automation?
Why does a workflow become more responsive when it uses generative AI?
In a mixed workflow, where should AI help, and where should fixed rules stay in control?
Generative AI adds intelligence by helping a workflow create or adapt content instead of only repeating fixed actions. In a basic automation, the path is usually set in advance. With generative AI, the system can produce text or other content as part of the process, which makes the workflow more flexible. That is why the unit calls these systems AI-enhanced workflows: AI adds a layer of smart behavior inside a larger automated sequence.
This matters most when the task is not fully static. For example, a workflow may need different content depending on the input, so AI can help make the output more useful or more specific. The main idea is that the workflow still uses automation, but AI helps it respond to changing needs. A common pain point is assuming AI replaces the whole workflow. The materials present it differently: AI supports the workflow, and the surrounding automation still manages the steps, triggers, and actions.
So, where should AI help? It should handle the parts that need flexible language or dynamic response, while fixed rules should keep control of the routine steps. That balance is the core idea in this section and also helps you distinguish AI-enhanced workflows from AI agents in 1b. If you remember that generative AI adds intelligence to selected parts of a workflow, you will have the main concept.
To review, see:
[1.4 How Generative AI Powers Automation]
[1.4 Video How Generative AI Powers No-Code Automation]
Unit 1 Vocabulary
This vocabulary list includes terms you will need to know to successfully complete the final exam.
AI agent
AI-enhanced workflow
free tool
generative AI
process map

Last modified: Thursday, 18 June 2026, 1:29 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()