Make.com Guide

What Make is

Make is a visual workflow platform for connecting apps and automating multi-step processes. Its workflows are called scenarios. A scenario normally starts with a trigger, processes one or more bundles of data, and passes the result through modules that read, transform, or write data. Make's official pricing page lists more than 3,000 standard apps plus routers, filters, webhooks, data stores, and AI features.

Building a scenario

A scenario can run on a schedule, respond to an incoming webhook, or use an app trigger. Scheduled options include regular intervals, daily, weekly, monthly, specified dates, and on-demand runs. Webhooks are useful when an external service can notify Make immediately instead of waiting for a polling interval.

Routers split a workflow into routes. Filters decide which route receives a bundle, and a fallback route can handle data that does not match the other conditions. Route order matters when more than one condition could match.

Data stores retain information between runs and can support simple deduplication, state tracking, or handoffs between workflows. Make says storage allowance scales with plan credits and that each data store has a minimum size of 1 MB.

Understand the credit model

Make calls its billing unit a credit. Most module actions consume one credit, but the number of actions grows with the number of bundles. The operations guide explains that downstream modules normally run once for every returned item. A trigger returning ten records followed by three modules can therefore create 30 downstream module runs.

Before choosing a plan, write down the expected records per run, the modules each record touches, the schedule, and an allowance for retries or spikes. Inspect execution details after running a representative batch. Aggregating records before an expensive downstream step can reduce repeated actions when the destination supports a combined request.

Reliability and recovery

Make documents error handlers including skip, retry, resume, commit, and rollback behavior. The correct choice depends on whether a failed item can be discarded, retried safely, substituted, or reverted. A production scenario should also record terminal failures somewhere an operator will review them; a scheduled trigger alone is not proof that every downstream action completed.

AI features and review boundaries

Make lists AI applications, AI Content Extractor, AI Web Search, and Make AI Agents. These tools can classify sources, extract structured fields, or prepare private drafts. They do not establish that generated claims are true or that a tool was personally tested. Keep source URLs, retrieval dates, and human approval attached to consequential editorial output.

Plans and fit

As retrieved on 2026-09-19, the Free plan includes 1,000 credits per month, two active scenarios, a 15-minute minimum schedule interval, a five-minute maximum execution time, and seven days of detailed execution logs. Core adds unlimited active scenarios, minute-level scheduling, higher transfer limits, and API access. Pro and Teams add execution and collaboration features. Select the needed credit volume and billing term on the live pricing page before comparing monthly cost. Check current pricing before publishing a budget.

Shortlist Make when you need to connect several services and want to inspect the workflow visually. Evaluate it by the monthly bundles and module actions the workflow will process, not only by the number of supported apps.