The Tools Landscape

There are three dominant no-code automation platforms and choosing the wrong one early is an expensive mistake. Let's be direct about the tradeoffs. Zapier is the oldest and most polished. It has 6,000+ integrations, excellent documentation, and the lowest learning curve. If you can describe the automation in plain English, Zapier probably has a template for it. The downsides: it's expensive at scale (pricing is per task), it's less flexible for complex logic, and the free tier is extremely limited. Best for: founders who need automation running fast, aren't technical, and are automating standard SaaS-to-SaaS workflows. Make (formerly Integromat) is the power user's Zapier. The visual editor is genuinely excellent — you can see your entire automation flow on one canvas. It handles complex branching, data transformation, and loops far better than Zapier. Pricing is per operation (not per task), which is typically cheaper. Learning curve is steeper. Best for: founders comfortable with logic and data who want more power without writing code. n8n is the developer-first option and where we'll spend most of our time. It's self-hostable (runs on your own server), open-source, and free for self-hosted deployments. It has 400+ integrations and lets you drop into JavaScript or Python at any node. The cloud version costs money but self-hosting on a $6/month DigitalOcean droplet is common. Best for: technical founders who want full control, no per-task pricing, and the ability to run custom code inline. For this course, we'll primarily use n8n for complex workflows and reference Zapier/Make where they're genuinely better choices.

One of the most common mistakes is building everything in a no-code tool when Python would take 30 minutes and be infinitely more maintainable. Here's the decision framework. Use no-code tools when: the automation connects two or more SaaS products via their official APIs, the logic is relatively linear, non-technical team members need to maintain or modify it, and you need it running within hours. Use Python when: you're processing data at scale (thousands of rows), you need custom logic that no-code tools struggle with, you're building something you'll reuse across multiple workflows, or you're interacting with APIs that don't have pre-built integrations. Use Claude API or other LLMs when: you need to read unstructured text and extract structured data, you're classifying, summarizing, or generating content, or you need to make a decision based on natural language input. The best automation stacks often combine all three. A common pattern: n8n orchestrates the workflow, Python handles data transformation, Claude API reads emails and extracts action items, and the result posts to Slack. For the rest of this week, we'll build our first automation using n8n. By Friday you'll have a working workflow running. By the end of the course, you'll know when to reach for each tool and how to combine them effectively.