Loading tutorials…
Loading tutorials…
Make.com (formerly Integromat) is more flexible than Zapier but more punishing if you skip foundations. This walks the setup that prevents 90% of "why is this broken" questions later.
Who this is forOwners and operators new to Make.com who want to build automation without the foundation problems that take days to untangle. Especially valuable if you are migrating from Zapier and expect Make to "just work" similarly.
What you'll need
Step 1
Sign up at make.com. Choose the right region (EU vs US) — affects data residency, latency, and which version of Make you land on.
Open make.com → "Sign Up." Use a team email (automation@yourdomain.com), not a personal Gmail.
Choose the region: EU (eu1.make.com) for EU data residency, US (us1.make.com) for US-based.
Note: once you pick, you cannot easily move between regions. Pick based on where your customers and team are primarily located.
Verify the email. You land in the default Organization.
Set 2FA immediately under Profile → Security → Two-Factor Authentication. Make has full access to every app you connect — 2FA is non-negotiable.
Step 2
Organization → Settings. Set the legal name, billing email, time zone, and team display name. Every scenario inherits this context.
Click your avatar (top-right) → Organization Settings.
Fill in: Organization Name (your company), Billing Email (accounting@yourdomain.com — NOT a personal email), Default Timezone.
Pick the timezone carefully. All scenario schedules ("run every X hours starting at Y") use this timezone. Wrong timezone = scenarios firing 3 hours off for months.
Under "Billing," confirm payment method and plan. The Free plan gives 1,000 operations/month and 2 active scenarios.
If you anticipate over 1,000 operations/month, upgrade to Core ($9/mo for 10K operations) BEFORE building. Hitting the free limit pauses all scenarios with no warning.
Step 3
Organization → Teams → + New Team. Separate teams keep scenarios, connections, and data stores isolated.
For solo operators, the default team is fine. Skip team setup.
For multi-person operations: create teams per project or per client. "Marketing Automation," "Client Onboarding," "Internal Ops" etc.
Each team has its own scenarios, connections, data stores. A team member added to "Marketing" cannot see "Client Onboarding."
Invite team members → Organization → Users → + Invite User → select role (Admin, Member, Limited Member) and team(s).
Limited Members can run/edit scenarios but cannot change connections or billing. Use this role for VAs and contractors.
Step 4
Connections are reusable OAuth/API credentials. Add the apps you will reuse: Gmail, Slack, Google Sheets, Stripe, etc.
Open Team → Connections → + New Connection.
For each app you will reuse across multiple scenarios: create the connection once here, before building scenarios. Connections are reusable.
Name each connection descriptively. "Gmail — automation@yourdomain.com" NOT "Gmail." Future you with 30 connections will need to know which is which.
For OAuth connections (Google, Slack, etc.), complete the OAuth flow in a separate browser tab/window. If the popup closes, the connection is half-saved and will fail later.
For API-key connections (custom services), use scoped, read/write-specific keys. Never use master keys.
Test each connection after creating by clicking "Verify." Failed verifications are easier to fix now than during scenario building.
Step 5
Templates → New Scenario → before building, set the scheduling, max execution time, and error-handling defaults.
When you create a scenario, the default schedule is "On Demand" (manual). Most production scenarios should run on a schedule or webhook trigger.
Under Scenario Settings → Scheduling, set the cadence: every 15 min for time-sensitive flows, daily for batch jobs, on webhook for event-driven.
Under "Advanced Settings" → Max execution time. Default is 40 minutes; lower it to 10-15 min for most flows. Long-running scenarios silently consume operations on retries.
Set "Error Handling" to "Resume" — if an operation fails mid-scenario, the rest still runs. Default "Stop" loses partial data.
Set "Allow stored data" to ON if scenarios will use Data Stores. (More on Data Stores in tutorial 6.)
Step 6
Profile → Notifications. Configure email/Slack alerts when scenarios fail or hit limits.
Open Profile → Notifications.
Enable email notifications for: "Scenario errors," "Scenario disabled (limit reached)," "Connection issues."
For multi-person teams, route notifications to a shared Slack channel via the Make → Slack notification integration. Otherwise alerts hit one inbox and get missed.
Set "Operations usage alert" at 80% of monthly limit. Gives you 2-3 days warning before scenarios auto-pause.
Test by triggering a scenario error intentionally (disconnect a module, run). Verify the email arrives.
Step 7
Open a Notion/Google Doc. List planned scenarios, expected ops/month each. Tells you what plan tier you actually need.
Create a doc: "Make Automation Inventory."
For each planned scenario: name, trigger type, expected runs/month, modules per run, total ops/month.
Example: "New Lead → CRM → Email — webhook, 200 runs/mo, 4 modules = 800 ops/mo."
Sum across all scenarios. Add 30% buffer for testing, retries, errors.
Pick the plan that covers that total: 10K ops = Core $9/mo, 50K ops = Pro $26/mo, 200K ops = Teams $69/mo.
Revisit this doc monthly. Operations growth is silent — you do not notice until you hit the limit.
Common mistakes
Not understanding operations consumption
What goes wrong: You build scenarios assuming Zapier-style 'task per workflow run.' Make charges per MODULE per run. A 10-module scenario running 100 times = 1,000 ops, not 100. You burn the Free tier in days and scenarios pause.
How to avoid: Read Make documentation on operations BEFORE building. Design scenarios with the minimum module count needed. Use Iterators carefully — they multiply operations.
Using a personal Gmail as the Org email
What goes wrong: Billing emails, scenario failure alerts, and team invitations all go to your personal inbox. When you leave / change company / change personal email, the org is orphaned. Recovering admin access is painful.
How to avoid: Use a team alias (automation@yourdomain.com, ops@yourdomain.com) from day one. Forward to whoever owns it currently.
Building scenarios without naming connections clearly
What goes wrong: You end up with 5 'Google Sheets' connections in the list, all OAuth from different accounts. You cannot tell which is which. Picking the wrong one mid-build causes silent failures or writes data to the wrong sheet.
How to avoid: Name connections "App — Account/Purpose" from the start. "Google Sheets — Marketing Lead Tracker" NOT "Google Sheets 3."
Setting max execution time to default (40 min)
What goes wrong: A scenario with an infinite loop or stuck API call runs for 40 minutes consuming operations the whole time. You waste 1,000-5,000 operations on a broken scenario before noticing.
How to avoid: Set Max Execution Time to 10-15 min for normal flows. Long-running batch jobs only need it higher, and they should be carefully designed.
Not setting up operations usage alerts
What goes wrong: Scenarios pause silently when you hit the monthly limit. You discover this 3-4 days later when a customer complains automations are not firing. By then you have lost real revenue.
How to avoid: Set the 80% alert under Profile → Notifications. Gives 2-3 days warning to either upgrade or audit scenarios before pause.
Recap
Done — what's next
How to build your first Make.com scenario from scratch
Read the next tutorial
Hand it off
Make.com rewards careful operations design. A specialist will build the foundation AND design your first 5-10 scenarios with operations efficiency in mind. From $14-16/hr — most setup + first scenarios projects land at $400-1,200.
See specialist rates
An operation is one module execution in a scenario. A scenario with 10 modules that runs 1 time = 10 operations. A task in Zapier is one workflow run regardless of step count. This pricing difference often surprises owners migrating from Zapier — Make can be 2-5x more expensive per workflow if scenarios have many modules.
Free for testing only — 1,000 operations is gone in days for any real automation. Core ($9/mo, 10K ops) is the entry point for production. Most businesses land on Pro ($26/mo, 50K ops) within 3-6 months.
No direct migration tool. You rebuild each Zap as a Make scenario manually. Plan 1-3 hours per Zap depending on complexity. Worth doing if Zapier task pricing is breaking your budget.
Unlimited within Make. Each is a separate OAuth or API key. Useful if you connect multiple Google accounts, multiple Stripe accounts, etc. Cost is in operations consumed, not connection count.
Pick based on data residency rules for your customers and which region your team is in. EU for EU customers (GDPR). US for US customers. Once you pick, migrating regions is impractical — choose carefully.
Make
You signed up for Make and the scenario builder is staring at you. This walks through one real, working scenario end-to-end — without the marketing fluff.
Make
Routers and filters are how scenarios stop being linear toy automations and start handling real-world conditionality. This is the structure that prevents 1,000-line debug sessions.
Zapier
You signed up for Zapier and the dashboard is staring at you. This walks through one real, working Zap end-to-end — trigger app, action app, sample data, test, turn on — without the marketing fluff.
Make
DIY Make is a great idea — until it is not. This is the honest framework: when the cost of self-managing exceeds the cost of hiring, and how to tell which side you are on.