Make
“Automation / mind-map style” — a designer who sketches your workflow as a diagram
What is Make?
Make is a workflow automation service where you draw the flow between apps as a map of circles joined by lines, not a list, so you can see conditions and branches at a glance as you build.
- 1Build automations by drawing a map, not writing a list
- 2Handles complex flows that branch and loop back
- 3Costs stay relatively low for the same workload
What sets it apart
These are the differences we found by running the same material through several tools in our training sessions.
See the flow as a diagram
You connect round modules with lines, split paths by condition, and merge branches back together, following the flow on screen. It’s easy to spot what went wrong and where, which makes Make especially strong when you’re fixing and scaling automations.
Handles conditions and loops
Judgments people used to make only in their heads, like “send to approval above a certain amount” or “go through the list one row at a time,” go right into the flow. It has the features you need to move beyond simple connections and build your business rules directly into the workflow.
Relatively low pricing
The free plan includes 1,000 credits a month, and paid plans start at $9 a month for Core with 10,000 credits. You can run the same work for less, so costs stay low while you build and test several automations.
⚖️ The weaknesses are clear, too
The screen is blank when you first open it and you have to start by placing circles, so the first hurdle is higher than with “pick one option at a time” tools. It doesn’t offer the most app connections either, and the interface and help docs are mostly in English, so you often have to connect Korean services yourself.
💡 In plain EnglishA tool that carries over the habit of sketching a workflow on a whiteboard. The diagram you draw becomes the automation that actually runs.
Work in an organization rarely flows in a single line. Branches appear, like “if the amount is over a threshold, send it for approval; otherwise, process it right away.” Being able to design those branches visually is what people grasp fastest in a training session.
Same job, different approach
Every quote request gets handled differently
The old way
- Read the email and estimate the amount range in your head
- Small requests get an immediate reply; big ones go to the CEO
- Relies on memory to track which items are done and how far each one got
- When the owner leaves, those rules go with them
With Make
- When a request comes in, the first circle of the flowchart receives it
- Splits into two paths on an amount condition
- Small requests get an automatic reply; big ones go out as approval alerts
- The rules stay visible as a diagram anyone can read
Common uses
Intake that branches on conditions
Assign different owners based on inquiry amount, region, and type, and collect items that match no condition in a separate list. It turns a person’s judgment rules into a diagram.
Reconciling data across systems
It goes through lists scattered across sheets, databases, and email one row at a time, compares them, and reports only the items that don’t match.
Content publishing flow
Once a draft is approved, it reformats the images and body text and posts them to multiple channels in order. Each step’s success or failure shows on screen.
Who it’s for
Best for
- ✓Anyone in the habit of sketching flowcharts to organize their work
- ✓Anyone automating work with many conditions and exceptions
- ✓Anyone who wants to build and test several automations
Better served by other tools
- –Anyone who only needs a simple one- or two-step connection
- –Anyone who feels daunted by a blank screen
- –Work that mostly relies on Korean service integrations
Can we use it at work?
The questions that adoption leads and security teams ask first.
Note: Please check the official documentation for where data is stored, for how long, and whether you can choose European or US servers. We recommend a security review before company-wide adoption.
10-minute quick start
- 1
Sign up at make.com and start on the free plan.
- 2
Place the first circle (the trigger module) on a blank canvas and choose the event that starts the flow.
- 3
Attach the next circle, then click “Run once” to see for yourself how real data passes through.
- 4
Add just one conditional branch. Once you get past this step, the rest is just variations.
Copy-and-paste prompts
Replace only the [bracketed] parts, then paste it in.
When a new request comes in on the web form [Quote Request] → if the amount is KRW 5 million (≈ US$3,740) or more, send an approval request to the CEO by email and to Slack [#management]; if it’s less, send an automatic reply email to the contact person. In both cases, also log the route taken in the Google Sheet [Quote Log].
From the Google Sheet [Student Roster], pick only the rows where the “Completed” column is empty and process them one by one. For each row, calculate the attendance rate; if it’s 80% or higher, mark it “Completed” and send a completion email, and if it’s lower, mark it “Not completed” and collect those into a list for the contact person.
Every Monday at 8 a.m., compare the Google Sheets [Payment Ledger] and [Training Schedule] and pull only the entries that have a scheduled session but no payment record. Put the results in a table and email it to the contact person, and if there are 5 or more, also notify Slack [#management].
When Gmail receives an email with [Proposal] in the subject → save the attached PDF to Drive → use an AI step to write a three-line summary of “request, amount, deadline” → post it to the Slack [#sales] channel with the file link.
If an error occurs at any step of this flow → record the error details and the data received at that moment in the Google Sheet [Error Log] → notify the contact person just once. Only if the same error occurs more than 3 times in a day, send an additional alert.
Using it with other tools
Linking two or three tools changes your work more than any single tool does.
Receive → Decide → Reply
Data collection → Weekly report
Before you start
- Don’t build several branches into your first flow. Run it end to end as a single line first, then split it. It’s faster.
- If you switch it on without a test run first, bad data can spread to several systems at once.
- Credits are used up with every step, so cutting unnecessary intermediate steps cuts costs.
- Without an error-handling path, you may not notice for days that a workflow has quietly stopped.
Pricing: personal use and work use
Plans that individuals pay for are different from plans that organizations contract for by member.
For individual use
Up to 1,000 credits/month
A starting point for always-on automation you run yourself
Individual users who need advanced features
Using it at work
For teams, with multiple people using it together
Custom features, year-round support, advanced security
Checked on 21 Sep 2026 · Prices are as shown on the official pricing page, based on 10,000 credits a month. If you raise the volume, the price rises with it, even within the same plan. Prices change without notice, so check the official page before you pay. Make official pricing ↗
Agentic AI — the version that does the work itself
Besides automations that follow a fixed flow, there are AI agents that decide which tools to use once you give them a goal.
Make AI Agents
It isn’t a chatbot that only answers questions. It makes a judgment, then runs the actual business workflow. Attach automations you have already built as tools, and the agent picks the right one when needed. The official introduction highlights that the reasoning behind each choice is recorded step by step on screen.
- No installation — log in at make.com, build an agent, and connect the automations you want it to use as tools.
- To use your own key, add the key from your chosen AI model provider in the connection settings.
Setup steps and conditions follow the official documentation. Make AI Agents official overview ↗ · Make official pricing ↗
Where Make falls short
We don’t just list the positives. Here is what fell short when we used it.
- Costs can rise even on the same plan
Choosing a plan isn’t the end of it: if you raise throughput, the price rises even within the same plan. The more you automate, the more you end up recalculating next month’s invoice.
- Long flows get cluttered
The visual layout is its strength, but past twenty steps the lines tangle and the flow is hard to take in at a glance. Inheriting a flow someone else built means spending a long time just reading it.
- Few Korean-language examples
When you search for the on-screen terms that trip you up, English articles come up first. There aren’t many Korean examples tailored to your kind of work, so at first you end up translating as you follow along.
Tools to compare
ZapierThe world’s largest workflow automation tool→
n8nAutomation with AI integrations→
OpalAI app builder, strong at automation→FAQ
Last updated 22 Sep 2026 · The ratings on this page come from John Kim, CEO of Nanum Consulting, who has used these tools firsthand in training and real work.
Make, Built into Your Team’s Skills
Send us a message and we’ll reply within 24 hours. We’ll propose a curriculum tailored to your industry and job roles.
Courses in this fieldAI Agents & Work Automation: Hands-On Training