Make

What Make does

Make builds scenarios: visual workflows in which modules read, create, update or transform data across apps. Every plan, including Free, has the visual builder, routers and filters and access to 3,500+ apps. It suits a team that wants to see and branch the data flow on a canvas and is willing to count module actions.

How credits are counted

Make bills in credits. Each module action, such as reading a record, writing a spreadsheet row or posting a message, uses one credit, because one operation equals one credit by default. A module runs once per bundle of data, so a trigger that returns 10 new records makes each later module run 10 times. Router and error-handler modules use no credits, and code steps use 2 credits per second of execution.

Trigger checks count too. A polling trigger such as Watch New Rows uses one operation every time it checks. A scenario that checks every 15 minutes makes 4 × 24 × 30 = 2,880 checks in a 30-day month, almost three times the Free plan's 1,000 credits, before it moves any data. Checking every minute on a paid plan makes 60 × 24 × 30 = 43,200 checks.

What you pay

Free costs nothing for 1,000 credits a month, with no time limit. Core is shown at USD 9 a month, Pro at USD 16 and Teams at USD 29, each for 10,000 credits a month, with credit tiers up to 8M. The pricing page does not say whether these figures are the monthly or the annual-billing rate; annual prepayment is advertised as saving 15% or more. Enterprise is priced by sales. Taxes are not stated.

Make's own AI tools charge credits by tokens: on the Large tier (GPT-5 mini) one credit covers 3,616 input tokens or 452 output tokens. If you connect your own OpenAI or Anthropic account on a paid plan, Make charges credits per operation and the provider bills the tokens.

Limits that change the choice

Free runs at most two active scenarios, no more often than every 15 minutes, for up to 5 minutes per run. Paid plans allow unlimited active scenarios, schedules down to one minute and runs of up to 40 minutes. Credits expire at the end of the term; with yearly billing they last 12 months.

When credits run out, scenarios stop until you add more. You can buy bundles of 1,000 or 10,000 credits, or let Core, Pro and Teams buy 10,000 automatically before you run out. Overage protection that keeps scenarios running is an Enterprise feature.

What the documentation leaves open

The price of an extra credit bundle is not published; Make calls it "the fixed price defined in your subscription". The pricing page lists 3,500+ apps in the plan cards but "more than 1,000" standard apps in its FAQ. Which plan includes the on-prem agent for local networks is not clear from the pricing page.

When to compare alternatives

Zapier does not charge for polling checks, which matters if you watch several apps on a short schedule. n8n counts a whole workflow run as one execution and Activepieces counts a flow run as one credit, so a long scenario with many modules is metered as a single unit there.

Before you buy

Sketch the scenario, count modules and records per run, and add one credit for every scheduled check. Multiply by runs per month and compare the total with the credit tier. Ask Make whether the price you see is the monthly or the annual rate and what an extra 10,000-credit bundle costs. The Free plan is enough to measure what one real scenario uses.