Overview
This lesson is part of the n8n AI Automation - Zero to Hero course, Section: 1. Introduction.
Watch the video above for the full tutorial, or read the written guide below.
What is n8n and how does it compare to Zapier and Make.com?
n8n connects hundreds of apps, builds multi-step workflows, and runs AI agents without writing a single line of code, all on a source-available platform you self-host or deploy to the cloud. Three features separate it from Zapier and Make.com: workflow-based pricing (one charge per complete execution, not per step or operation), full self-hosting with no vendor lock-in, and native support for complex AI automations using conditional logic nodes, a code node, and an HTTP node.
How do you build a Gmail-to-Google Drive attachment-saver in n8n?
The Gmail attachment workflow chains four nodes in sequence: a Gmail trigger, a Filter node, a Google Drive node, and a Discord node. The Gmail trigger wakes the workflow when a new email arrives and outputs all email properties including binary attachments. The Filter node checks whether an attachment exists and passes only matching emails forward. Google Drive uploads the file, and Discord posts a confirmation message using the email subject.
n8n nodes fall into three categories, all visible in this four-node demo. Trigger nodes start execution: the Gmail trigger fires on new email, but a new Google Sheet row, a CRM entry, or a scheduled time like every Monday at 7:00 a.m. all work as triggers too. Data-transformation nodes handle the middle: the Filter node evaluates a binary condition (attachment present or not) and routes only matching emails into the "kept" branch. Action nodes close the chain: the Discord node constructs a message from an expression that pulls the email subject directly from the Gmail trigger's output.
The Gmail trigger node exposes its settings panel when you double-click it on the canvas. The left side shows incoming data, the right side shows output; clicking "Fetch test event" pulls a real email and displays its full payload, including ID, subject, labels, and binary attachments. The Google Drive node accepts saved Google account credentials, sets the operation to "upload," references the binary attachment from the Gmail trigger, and targets a named folder such as "hands-on labs." Clicking "Test workflow" at the bottom of the canvas runs all four nodes in sequence and marks each with a green check mark on success.
Key Takeaways
- n8n charges one fee per complete workflow execution, not per step, so a workflow with hundreds of nodes costs the same as a two-node one, making monthly costs predictable.
- n8n runs on a local machine, a private cloud server, or an enterprise instance, eliminating the vendor lock-in that applies to cloud-only tools like Zapier and Make.com.
- Every n8n workflow uses three node categories: trigger nodes that start execution, data-transformation nodes that filter and route data, and action nodes that complete tasks like uploading files or sending messages.
- The Gmail attachment workflow demonstrates the core pattern: Gmail trigger fires on new email, Filter node checks for a binary attachment, Google Drive node uploads the file, Discord node sends a subject-based confirmation.
- Mapping a business process in plain English before building in n8n makes the logic transferable: swap Gmail for Apple Mail, Google Drive for OneDrive, or Discord for Slack without changing the underlying workflow structure.
Related Lessons
- Lesson 1: n8n AI Automation Course Introduction | Build AI Workflows (Zero to Hero)
- Lesson 2: What is Automation | Why It Matters | Your First n8n Automation Demo
- Lesson 17: n8n vs Zapier vs Make.com Comparison
Next Steps
Continue your n8n journey with the full n8n AI Automation - Zero to Hero course.
