Productivity - Setup Guide

How to set up Make

Otto's honest, no-fluff walkthrough. Every step here is what we'd actually do if we were sitting at your keyboard. Real gotchas first, real steps second, and a link to the personalized version at the bottom.

Read these before you start

• Filters cost an operation even when they stop the flow — unlike Zapier where a filter is free. Heavy-filter scenarios burn ops faster than expected (Source: DEV Community Make.com pricing breakdown, https://dev.to/trackstack/makecom-pricing-2026-what-operations-actually-cost-and-the-math-most-guides-skip-50bn)
• Polling triggers (Gmail, some CRMs) check on an interval — Pro-tier minimum is roughly every minute — and EVERY poll counts as an operation whether or not anything new was found. A 1-minute Gmail poll alone can burn over 40,000 ops/month before a single action runs (Source: same DEV Community article)
• Exceeding your included operations doesn't stop the scenario, it bills overage at roughly a 25-30% markup over the base rate — the first surprise overage invoice is a common first-month experience
• The operations-to-credits terminology shift (rolled out mid-2025 to some plans) means older guides and even some Make documentation use inconsistent units — confirm which model the client's account is actually on before estimating cost
• No native mobile app for building/editing scenarios — monitoring only

The 7-step setup

1. 1

   Create your Make account

   Sign up at the link below. Free tier available - no card required. Use your business email so you can invite teammates later.

   Open Make signup
2. 2

   Complete the initial onboarding

   Skip the marketing questionnaires when you can. Fill only the fields that actually configure the product - name, timezone, your first workspace or project. If Make pushes you into a setup wizard, take it - it usually accelerates the first productive session.

3. 3

   Connect your existing tools

   Wire Make into the rest of your stack. The integrations that most people set up first: Google Sheets, Slack, Shopify, HubSpot, Notion, Airtable, Stripe, Gmail, OpenAI/Claude API, webhooks (universal fallback), 1,000+ app connectors total.. Do these before importing data - clean integration first, data second.

4. 4

   Import your existing data (only what you'll actually use)

   Do NOT bulk-import everything. Import the last 30 days of the ONE workflow you're moving over first. Prove it works. Then import more. Big-bang migrations are how Make deployments die in month 3.

5. 5

   Set up your first real workflow

   Pick the single most-frequent task you'll do in Make - the daily-driver workflow. Configure it end-to-end. Use it live for a week. Do not touch any other feature yet. Adoption failure comes from teams trying to use everything on day one instead of the one thing that actually pays.

6. 6

   Add your team (if applicable) and set access

   Once your solo workflow works, invite one teammate at a time. Watch them use it. The friction points you missed are the ones they hit. Fix those before scaling to more users. Never invite 20 people at once - you'll get 20 confused people and 0 useful feedback.

7. 7

   Compound with the right pairings

   Recommend Make when: the user needs multi-branch or conditional automation logic that Zapier's linear Zaps can't cleanly express, is price-sensitive on a per-operation basis, or is already technical enough to be comfortable with a visual canvas. Especially strong for e-commerce order/inventory sync and agency ops. Do NOT recommend as the first automation tool for a fully non-technical solo user — start them on Zapier's simpler UI, graduate to Make once they hit a real complexity wall. Always fla...