> ## Content Index
> Fetch the complete content index at: https://linuxhandbook.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Chapter 1: Introduction to AIAutomation
- URL: https://linuxhandbook.com/courses/n8n/n8n-intro/
- Published: 2026-11-20T14:20:27.000Z
- Updated: 2026-11-20T14:20:27.000Z
- Author: Yash Kiran Patil
- Tags: n8n, #lessons-col, #lesson-duration-10m

Today, AI can help with many kinds of work, but routine tasks still take time when they are handled manually. AI automation combines AI with a repeatable process so that some of those tasks can run with less hands-on effort.

In this series, we’ll learn how to use AI automation for work that would otherwise take time to complete. You create the automation, let it run, and use the time it saves for other work. We’ll begin with the basic ideas and then use n8n to build practical Linux and open-source examples.

## What is AI automation?

AI automation uses an AI system as part of a process that performs a task. For example, a workflow can check incoming email, look for a particular kind of request, and prepare a response. The workflow connects the steps and determines what happens with the information.

Two terms help explain how these systems work: **workflow** and **agent**. A workflow is a sequence of tasks arranged to reach a goal. Its designer defines the steps and conditions in advance. An agent can use an AI model to decide which tool to use or what step to take next, based on its goal and the information it receives. Anthropic describes this distinction in its guide to building effective agents.

Both can include AI, and both can include safeguards or human approval. The difference is who directs the next step: a workflow follows a predefined path, while an agent gives the model more control over the process and tool use.

For example, a content workflow might take an idea, generate a draft, and return it for review. It follows the steps that you designed. A marketing agent might be given the goal of planning a campaign, research the market, choose an audience, and select tools or actions based on what it finds. The agent has more freedom to decide how to reach the goal.

The illustration below compares a predefined workflow with an agent that can choose its next step.

![Diagram contrasting an AI agent choosing tools and actions with a workflow that follows predefined steps](https://linuxhandbook.com/content/images/2026/11/image66-1.png)

Use a workflow when the task is predictable and you want its steps to be easy to inspect. Consider an agent when a task requires the system to choose among tools or actions as it works. An agent can still pause for approval before an important action.

## Automation platforms

Automation platforms provide a place to connect services and define how information moves between them. n8n is one such platform. Make and Zapier are other options. These platforms connect to applications and services such as email, databases, payment systems, and APIs, so a task in one service can trigger an action in another.

n8n provides a visual canvas where you arrange and connect steps. It also includes integrations for common services and an HTTP Request node for working with APIs. This lets you start with a visual workflow and add code when a project needs it.

## Platform comparison

For this series, we’ll use n8n to explore automation. It suits Linux users who want to learn how workflows are built and who may prefer to run the service on infrastructure they control.

n8n’s source code is available under the Sustainable Use License, and n8n describes its model as fair-code. The self-hosted Community edition can be used without a software subscription for permitted personal or internal use. The license limits some commercial uses, so check the current license terms if you plan to use n8n for a business or offer it as a service.

Self-hosting gives you control over the server and configuration, but you are responsible for updates, backups, access control, and keeping the service available. The visual editor also makes it possible to see how the workflow steps connect without writing the entire process as code.

The source illustration compares n8n, Make, and Zapier. Their integrations, hosting choices, limits, licensing, and prices can change. Make and Zapier also offer free plans, so use the comparison as a visual overview and check each service’s current feature and pricing pages before choosing.

![Comparison of n8n, Make, and Zapier, including their approaches to integrations, hosting, and workflow automation](https://linuxhandbook.com/content/images/2026/11/image11.png)

All three platforms automate your work. The difference lies in how they do it and in certain features, such as the applications they support and the way they operate.

In this series, as mentioned earlier, we will use n8n because it is free and open source. We do not need to pay anything to start building automations, unlike some of the other platforms that require a paid subscription.

In the next chapter, we’ll set up n8n and explore its interface. Then we can use those basics to build workflows for Linux and open-source users.