In n8n, a project is a way to group related workflows, credentials, and variables for easier organization, management, and team collaboration. [Example] Imagine you run an AI automation agency and have three clients: a shoe store, a real estate company, and a restaurant. Each client has different workflows, credentials, and variables. You could create a separate n8n project for each client. This keeps each client's related resources organized and separated from the others. For the shoe store, the project could contain workflows for customer emails, order updates, and refunds, along with the credentials and variables those workflows need. For the restaurant, you could have a separate project containing workflows for reservations, customer inquiries, and review requests, along with the restaurant's related credentials and variables. Now, when you need to manage a client, the client's related workflows and project resources are grouped together instead of being mixed with resources for other clients. That's the main idea of an n8n project: group related resources together so they are easier to organize, manage, and collaborate on.

An n8n workflow is a collection of nodes that automate a process. A workflow begins execution when a trigger condition occurs and then executes sequentially to complete a task.

In n8n, a trigger node starts a workflow when a specific event or condition occurs, such as receiving an email, reaching a scheduled time, or receiving a webhook request.

n8n templates are pre-built workflows created by n8n or the community that you can import, configure, and customize for your own needs. To find these templates, go to Google and search for "n8n templates." Then, open the official n8n templates page and start using them in your n8n instance.

In an n8n cluster node, a sub-node is a supporting node connected to a root node that provides a specific capability or resource, extending the root node's functionality. [Example] Imagine you build an AI Agent in n8n. The AI Agent is the root node. To perform its job, it may need additional capabilities, such as an AI model, memory, or tools. You connect a Chat Model to the AI Agent. The Chat Model acts as a sub-node because it provides the language model the agent needs to process information and generate responses. You can also connect a Memory sub-node. Memory allows the AI Agent to retain and use information from previous interactions when needed. You can then connect a tool, such as Google Sheets. This allows the AI Agent to interact with Google Sheets when needed. So, the AI Agent is the root node, while the Chat Model, Memory, and tools are sub-nodes. Together, they form a cluster that extends what the AI Agent can do.