Make
Visual no-code platform for building automated workflows that connect apps and move data between them.
RecommendedLast reviewed July 17, 2026
What Make actually is.
Make is a visual platform for wiring apps together so data moves between them without a developer writing glue code. You drag steps onto a canvas, connect triggers to actions, and set a schedule or an event to run it. No code needed to start. It also supports building the same automation through a prompt or with custom code, so you're not locked into one method.
The catch is how it's billed. Every operation inside a scenario draws down one shared credit pool, so a handful of complex, high-frequency workflows can burn through a month's allotment faster than ten simple ones ever could. It's cloud-only, too. There's no self-hosted version, so anything sensitive runs on Make's own servers instead of your own infrastructure.
What it does
- Visual scenario builder using drag-and-drop, no code required to start.
- Connects to more than 3,000 apps and data sources.
- Also buildable through a natural-language prompt or written code.
- Runs on a set schedule or in response to a trigger.
- Keeps execution logs so you can see what happened and why.
- Supports custom code steps in JavaScript or Python when needed.
- Hosted only in Make's cloud, with no self-hosted option.
Both matter more once usage scales up.
Where it sits in the pipeline.
- AI & Intelligence
- Data & Enrichment
- Scraping & Custom Data
- Email Infrastructure & Deliverability
- Outreach & Sending
- LinkedIn & Multichannel
- Signals & Intent
- Calls & Meetings
- CRM & Pipeline Ops
Runs well with
The tools we'd run next to Make, and what each pairing covers.
Pricing, without the fiction.
From the Make pricing page · verified July 17, 2026
- 1,000 credits/month
- 2 active scenarios
- 15-minute minimum run interval
- 5 MB file size
- 7-day log retention
- 10,000 credits/month
- Unlimited active scenarios
- Minute-level scheduling
- 100 MB file size
- Make API access
- 30-day log retention
- 10,000 credits/month
- Priority execution
- Up to 1,000 MB file size
- 30-day log retention
- 10,000 credits/month
- Team/collaboration features
- 30-day log retention
Make's entry paid plan is Core at $12/month for 10,000 credits, which is really the first usable tier since Free caps at 2 active scenarios and a 15-minute minimum run interval. Credits don't scale up with the higher tiers (Pro at $21, Teams at $38 all still start at 10,000/month); those upgrades buy priority execution, bigger file size limits, and team features (log retention stays flat at 30 days through Core, Pro, and Teams), not more automation volume. Heavy or frequent scenarios burn through the credit pool fast, so the real cost driver is usage intensity, not seat count. Annual billing saves 15% or more. Enterprise is custom-priced and adds overage protection, which matters once credit overruns become routine.
Choose it, or skip it.
Choose it if
- Small GTM teams that want to connect two or three apps and see a live automation the same afternoon, no engineer required.
- Teams already running Clay, SmartLead, or a CRM that need a visual layer to route data between them on triggers and schedules.
- Anyone who wants automations built three ways: drag-and-drop, a natural-language prompt, or custom code, without picking one method upfront.
- Ops-minded operators who want per-scenario visibility (execution logs, error handling) instead of a black-box automation.
Skip it if
- Teams that need an agent to build or edit scenarios unattended; Make's own AI Agents act inside a workflow, they don't design the workflow for you.
- High-volume shops that will blow past 10,000 credits/month fast: heavy scenarios burn credits per operation, not per run.
- Anyone wanting API-first automation with no UI at all; Make is built around its visual scenario builder first.
If not Make, then what.
- n8nFree self-hosted Community Edition; cloud plans from ~€20/mo (Starter)
Pick n8n if the team wants self-hosting, code-level nodes, or wants to avoid per-credit billing entirely.
- ZapierFree forever tier (100 tasks/mo, 2-step Zaps); paid from $19.99/mo (Professional)
Pick Zapier for the largest app library and simplest linear automations when branching logic isn't needed.
Asked in real client work.
What's the difference between Make's Free plan and Core?
Free caps out at 1,000 credits a month, 2 active scenarios, a 15-minute minimum interval between runs, and 5 MB file sizes. Core ($12/mo, 10,000 credits) removes the scenario cap entirely, lets scenarios run on minute-level schedules, raises file size to 100 MB, and adds Make API access. For any team running more than a couple of live automations, Core is the real starting point.
How does Make's pricing actually work?
Make bills on credits consumed per scenario execution, not a flat per-automation fee. Every paid tier (Core, Pro, Teams) starts at 10,000 credits/month at increasing prices ($12, $21, $38), so the credit allotment doesn't grow with the plan; what changes is execution priority, file size limits, log retention, and team/collaboration features. Heavier or more frequent scenarios eat the credit pool faster and are what forces an upgrade to a higher credit-cost plan or add-on.
How does Make compare to Zapier or n8n for a small GTM team?
Make's visual, node-based canvas gives more control over branching logic and error handling than Zapier's linear zaps, at a similar no-code learning curve. n8n is the closer technical peer (both use visual flow canvases) but leans more toward self-hosting and code-level customization; Make stays cloud-hosted and prioritizes ease of setup, which suits teams that want automations live fast without managing infrastructure.
Can Make run AI agents, not just app-to-app automations?
Make ships AI Agents that can take actions and orchestrate steps across its 3,000+ app integrations inside a scenario, plus a library of ready-made agents. That's agent behavior embedded in a workflow you still design visually (or via prompt/MCP), not a standalone agent that plans and builds scenarios on its own without a human setting up the flow first.
What happens if a scenario needs more than the plan's file size or log retention limits?
File size caps rise by tier: 5 MB (Free), 100 MB (Core), 250 MB (Pro), 500 MB (Teams), up to 1,000 MB (Enterprise), and execution log retention goes from 7 days (Free) to 30 days (Core/Pro/Teams) to 60 days (Enterprise). A team hitting these ceilings has to move up a tier rather than pay an add-on for just that limit.