最近将一个客户端从 make 迁移到 n8n。这是他们向您计费的实际差异(操作与执行)
为客户把线索分配从 Make 迁到 n8n,原因是多行数据和循环 API 调用会放大逐操作计费;帖子用实际迁移说明平台选择如何影响交付后的运行成本。
Reddit 原帖
在 Reddit 查看migrated a client from make to n8n recently. here is the actual difference in how they bill you (operations vs executions)
hey guys, seeing a lot of questions about switching from make to n8n. i build these workflows for a living and just migrated a client's lead routing system, so i wanted to drop some real-world context on the pricing differences since it confuses a lot of people.
the biggest trap with Make is that they charge per \*operation\*. if you have a workflow that pulls 50 rows from google sheets and runs them through an http request, Make charges you 1 operation for the sheet pull, and 50 operations for the http loop. your quota evaporates instantly.
n8n charges per \*execution\*. that same workflow running 50 rows through an http node counts as ONE workflow execution on their cloud tiers (or free if you self-host).

















