Make

Make is a hosted visual automation platform. Scenarios connect application modules with filters, routers, iterators, and transformations. It is useful when an operations team needs to inspect how records branch between services, such as splitting an incoming order into line items and sending exceptions for review.

Follow each bundle of data

Build a scenario with a small sample before importing a full dataset. Inspect the bundles entering every module, especially after searches and iterators. One incoming order can produce many downstream module runs. Confirm the required connector action, authentication scope, attachment handling, and destination API limits.

Make provides execution history and error-handling mechanisms, but you still need a policy for retries and duplicate writes. Test a timeout after the destination has accepted a record. Without a stable external ID, rerunning the scenario may create another record.

Credits are the billing unit

The Free plan currently supplies 1,000 credits per month. Credits replaced operations as the billing unit. Most non-AI operations use one credit, but some AI and advanced capabilities use different fixed or dynamic rates. Operations remain an execution measure and are not a universal price conversion.

With your own model connection, provider token fees can sit alongside Make credits. Check scheduling, active-scenario limits, data transfer, history retention, and team controls on the selected plan. Compare monthly and annual billing for the same credit allowance. Review behavior when credits run out and any automatic extra-credit purchases. Use the module-level consumption history to budget your real scenario under Make’s service terms.

Official sources checked on October 23, 2026. Pricing, credit accounting, and service terms.