Make
A visual no-code platform for building multi-step automations and data flows.
Where it fits
A visual no-code platform for building multi-step automations and data flows.
Price and access
Check the current plan before paying
A free option is available for trying real tasks. Paid plans or usage can add higher limits or extra features.
- Core$12 / monthAs of 2026-09-05 · source ↗
- Pro$21 / monthAs of 2026-09-05 · source ↗
- Teams$38 / monthAs of 2026-09-05 · source ↗
Prices are collected from the official site and can change. Always confirm the current plan, taxes and regional availability before paying.
What it helps with and what to check
Good tasks to start with
- Visual multi-step workflow automation
- Teams that need to inspect each data step
Keep an eye on
- Handle partial failures and duplicate runs
- Protect credentials and personal data in scenario logs
How to start
Tick each step as you work. These checks stay on this page only; they do not verify results in the external tool.
0 of 5 steps checked
Define the rule before opening the builder
In the requirements worksheet below, write: only the exact test value approved may pass; pending, not approved and an empty value must stop. The result is a test marker, not a real approval. Use fictional values and keep this first scenario inside Make; no email, chat, webhook or work-account connection is needed.
Create two small Tools modules
Create a scenario. Add Tools > Set variable: Variable name approval, Variable value pending, Variable lifetime One execution. Add a second Tools > Set variable after it: Variable name route_result, Variable value ready_for_review. Keep that value a harmless marker; it must not send anything or update another app.
Put an exact-match filter between them
Click the line connecting the modules to add a filter. Map approval from the first module into the left operand; use the text Equal to operator and type approved on the right. Do not use Contains: not approved contains approved too. A filter passes matching bundles to the next module and stops non-matching ones.
Run four cases yourself
Set scheduling to On demand, then use Run once for each case. Start with pending: the second module should not run. Change the first value to approved: the second should output route_result = ready_for_review. Then try not approved and an empty value: neither should reach the second module. Inspect each run separately; an old output is not evidence that the current run passed. These are authored expected results, not a recorded Make trial.
Repair the rule and keep the limits
If not approved passes, check for Contains or a condition joined with OR. If every case passes, check whether the left side is typed text instead of the mapped first-module output. Repair and repeat all four cases. Record the checked rule in the requirements worksheet and review the policy Task before adding real actions. Keep On demand for practice; it still permits Run once or an API-triggered run. This example does not implement real approval, duplicate prevention, recovery or a production automation.
Platforms
Privacy and human checks
Before you upload
- Remove customer names, passwords, identifying details and company secrets.
- Read the provider’s current retention, training and workspace settings.
Before you use the result
- Verify facts, sources, calculations and code against the original material.
- Have a person review important content or actions before publishing, sending or running them.
Related tasks and guides
Prepare inputs or review results in these AhaDo workflows. Copy permitted material yourself when using an external tool.
Alternatives
A no-code automation platform with AI workflow and agent features across many software services.
View comparison option n8nA workflow automation platform with cloud and self-hosted options for technical teams.
View comparison option Microsoft Power AutomateMicrosoft’s low-code platform for business workflows, desktop automation and approvals.
View comparison optionOfficial source and research status
Guide published · Official Make documentation checked on 7 September 2026. This fictional filter exercise has authored expected results; no provider run or production automation is verified.
Listed means a published directory entry. Guide published means it also includes dedicated start steps and sourced prices. Neither status means real-user results have been verified.
- Official product source
- Open source ↗
- Last researched
- 2026-09-07
- Real-user evidence
- Not collected yet
Report a correction
Has a tool's information, price or signup changed? Tell us and help the next beginner.
