Courses Curriculum Cities Blog Enroll Now
AI Automation No-Code · Day 2 of 5 ~40 minutes

Day 2: Make.com: Visual Automation with More Power

Zapier is simple. Make.com is powerful. Learn how to build branching, looping automations that handle complex business logic — still no code.

1
Day 1
2
Day 2
3
Day 3
4
Day 4
5
Day 5
What You'll Build

A Make.com scenario that monitors a Google Drive folder for new documents, runs AI analysis on each one, and posts a structured Slack summary with executive brief, key findings, and action items.

1
Section 1 · 8 min

Zapier vs Make.com vs n8n

Three tools, same category, different tradeoffs. Pick the right one for each use case.

textTool Comparison
Zapier
  + Easiest to learn, largest app library
  + Best for simple 2-3 step workflows
  - Expensive at scale ($49+/mo for more than 5 Zaps)
  - Limited branching logic

Make.com
  + Visual canvas with branches, loops, filters
  + 1,000 free operations/month (vs Zapier's 100 tasks)
  + Much cheaper at scale
  - Steeper learning curve than Zapier

n8n
  + Open source, self-hostable (unlimited free)
  + JavaScript code nodes for custom logic
  + Best for technical users who want full control
  - Requires server setup for self-hosting

Rule of thumb: Start with Zapier for simple automations. Move to Make.com when you need branching or loops. Use n8n when you need to self-host or write custom code.

2
Section 2 · 12 min

Make.com Fundamentals

Create a free account at make.com. What Zapier calls a "Zap," Make calls a Scenario. What Zapier calls a "step," Make calls a Module.

The big visual difference: Make shows you data flowing between modules. You can see exactly what data enters and leaves each module, which makes debugging much easier.

Key Make concepts:

  • Router: The diamond shape. Creates branches — like an if/else statement. Different branches run based on conditions you set.
  • Iterator: Processes a list of items one by one. Zapier handles this with "line items" — Make makes it explicit and visual.
  • Aggregator: Collects multiple outputs and combines them into one. Useful after an iterator.

Operations budget: In Make, every module that runs costs one operation. A scenario with 5 modules running on 10 items uses 50 operations. The free tier gives 1,000/month — plan accordingly.

3
Section 3 · 20 min

Build: Document Watch → AI Analysis → Slack

Create a new scenario in Make.com. Here's the flow:

Module 1: Google Drive — Watch Files in a Folder. Point it at a "Reports to Review" folder. Set the schedule to every 15 minutes. This triggers whenever a new file appears in that folder.

Module 2: Google Drive — Get a File Content. Use the file ID from Module 1 to get the text content. For Google Docs, use "Download a Document" in text format.

Module 3: OpenAI — Create a Completion. Add the OpenAI module. Set the model to gpt-4o-mini (fast and cheap for document analysis). Write this prompt:

textDocument Analysis Prompt
Analyze this document and return a structured summary.

Executive Summary: (2-3 sentences)

Key Findings:
- (bullet 1)
- (bullet 2)
- (bullet 3)

Action Items: (explicit next steps, or "None identified")

Risk Flags: (anything that needs attention, or "None")

Document:
{{2.data}}

Map {{2.data}} by clicking the field and selecting the text output from Module 2.

Module 4: Slack — Create a Message. Add the Slack module, connect your workspace, and choose a channel like #reports or #team-digest. In the message body, map the OpenAI completion output and add the file name as a header. The final message will look like a clean professional brief every time a new document lands in the folder.

Emoji headers help. Ask the AI to format with emoji headers: "📋 Executive Summary:", "🔑 Key Findings:", "⚡ Action Items:", "⚠️ Risk Flags:". Slack renders these beautifully and the message is scannable at a glance.

What You Learned Today

  • The differences between Zapier, Make.com, and n8n — and when to use each
  • How Make.com's visual scenario editor works (modules, routers, iterators)
  • How to chain AI analysis to app actions in Make.com
  • How to write AI prompts that produce scannable, structured output
Your Challenge

Go Further on Your Own

  • Add a Router between the trigger and the AI step. Branch 1: documents smaller than 200 characters skip the AI and post 'File too small to analyze.' Branch 2: full analysis for larger documents
  • Add a condition: if the AI output contains the word 'urgent' or 'critical,' send an additional direct message to yourself
  • Try rebuilding this same scenario in n8n's cloud version — compare the experience and note what's different
Day 2 Complete

Nice work. Keep going.

Day 3 is ready when you are.

Continue to Day 3
Course Progress
40%

Want live instruction and hands-on projects? Join the AI bootcamp — 3 days, 5 cities.

Finished this lesson?