MakeMake
Make(原 Integromat)是「流程图派」的可视化自动化平台——分支、迭代、路由器在画布上比表单派更直白; AI 是它众多模块之一,自动化才是身份。纯云托管,无自托管。
Make (formerly Integromat) is the flowchart school of visual automation — branches, iterations and routers read more directly on the canvas than the form school; AI is one module among many, automation is the identity. Pure cloud hosting, no self-hosting.
适合与不适合When to use it, when not to
A fit for: visual scenarios with complex branches/data transforms, cross-SaaS automation as the main axis. Not a fit for self-hosting; wanting an “AI platform” positioning (that is the Dify/Coze narrative).
中文生态China availability 国产 / 国内可直接用 / 备案状态 · 快照domestic / direct access / CAC filing · snapshot 2026-10-21
- 出品属地Origin
- 国外出品foreign-made Make(原 Integromat,捷克)。Make (formerly Integromat, Czechia).
- 国内使用Direct access
- 直连未核验direct unknown 首页 200、terms/whats-new 403(CF)——整体直连性标 unknown。homepage 200, terms/whats-new 403 (Cloudflare) — overall directness marked unknown.
- 备案状态CAC filing
- 未见于备案名单not in filing list:未见于网信办公示名单(2026-10-21 检索);该产品未面向大陆公众提供服务,备案不适用。not in the CAC public registry (searched 2026-10-21); the product does not serve the mainland public, so filing does not apply.
备案信息以网信办《生成式人工智能服务已备案信息》公示名单为准(按批次滚动更新,本站只抄编号不解读);「大陆可直连」是本站从大陆网络直连实测的结果,不是厂商承诺。GitHub 类站点当日实测有波动,口径写在依据里。Filing status is quoted from the CAC public registry (updated batch by batch; this site copies the number and does not interpret it). "Direct access" is this site's own reachability measurement from a mainland network, not a vendor promise. GitHub-hosted sites fluctuated on the measurement day — the note says so.
固定坐标系Fixed coordinate system
8 个维度dimensions, 与同分区其他对象逐项可比each comparable item by item against others in the same section.
- 模型与开放条件Model & openness
AI 模块经平台接各家模型(OpenAI 等连接器);具体清单未逐条核验。 主轴仍是可视化场景(scenario)编排,AI 是模块之一。
AI modules reach each vendor's models through the platform (OpenAI and other connectors); the specific list has not been verified item by item. The main axis remains visual scenario orchestration — AI is one of the modules.
- 运行位置Where it runs
纯云托管:场景(scenario)跑在 Make 云端执行引擎上;无自托管形态的官方声明。 执行历史与队列都在平台内。
Pure cloud hosting: scenarios run on Make's cloud execution engine; no official statement of a self-hosted form. Execution history and queues all live inside the platform.
- 本地文件Local files
不承载本机文件运行时;数据经模块在各 SaaS 服务间流转、临时文件在云端处理。 要「AI 读写本机文件」的形态在这里不存在(如实记)。
It hosts no local-file runtime; data flows between SaaS services via modules and temporary files are processed in the cloud. The "AI reads/writes local files" form does not exist here (recorded honestly).
- 关机后的任务Tasks after shutdown
云托管常驻是默认形态:定时排程、webhook 触发、错误重试队列都是官方原生能力, 电脑关了场景照跑——这是托管形态与自托管的本质差别。
Cloud-hosted residency is the default form: scheduled timing, webhook triggers and error-retry queues are all native official capabilities — scenarios keep running when your laptop is off; that is the essential difference between hosted and self-hosted forms.
- 工具与扩展Tools & extensions
模块(apps)生态是核心资产(官方口径数千集成,未逐条核验);MCP 支持状态未逐条核验。
The module (apps) ecosystem is the core asset (official framing: thousands of integrations, not verified item by item); MCP support status not verified item by item.
- 上下文与记忆Context & memory
场景内数据路由与迭代器是官方上下文组织方式;跨场景记忆未逐条核验。
In-scenario data routing and iterators are the official context-organization scheme; cross-scenario memory not verified item by item.
- 权限与限制Permissions & limits
团队/组织角色与凭据 vault 是官方权限面;企业合规声明未逐条核验。
Team/organization roles and the credentials vault are the official permission surface; enterprise-compliance claims not verified item by item.
- 适合什么任务Best for
适合:可视化流程图式自动化、复杂分支/迭代逻辑比 Zapier 表单更直白。 不适合:要自托管;要 AI 是产品主轴(它是自动化主轴)。
Fits: visual flowchart-style automation; complex branching/iteration logic reads more directly than form-style tools. Does not fit: self-hosting; wanting AI to be the product's main axis (automation is its identity).
头号误解Top misconception
- 用旧名 Integromat 搜现文档——2022 已更名 MakeSearching current docs under the old name Integromat — renamed to Make in 2022
- 按操作(operation)计费模型下低估高频场景——看官方 pricing 页(D9 不采数字)Underestimating high-frequency scenarios under operation-based billing — see the official pricing page (no numbers stored here)
- 官网部分页直抓 403(CF)——核验走浏览器可达口径Treating connector availability as guaranteed — third-party APIs change
未知项清单Known unknowns
- AI 模块接入的模型清单(未逐条核验)
- 官方集成数量的现值口径(未逐条核验)
- MCP 支持状态(未核验到官方文档)
- The model catalog connected by AI modules (not verified item by item)
- The current official integration-count framing (not verified item by item)
- MCP support status (no official documentation found)
证据来源Evidence sources
判断可回到以下一手源复核。本站核验日Every judgement can be rechecked against the primary sources below. Verified on 2026-10-30,内容更新日content updated on 2026-10-21。
| 类型Type | 名称Name | 链接Link |
|---|---|---|
| docs | Make · 官方首页(2026-10-21 直抓 200)Make · official homepage (fetched directly 200 on 2026-10-21) | https://www.make.com |
| docs | Make · 官方 Terms(直抓 403=CF 拦截,浏览器可达)Make · official Terms (direct fetch 403 = Cloudflare block; reachable via browser) | https://www.make.com/en/terms-and-conditions |
| changelog | Make · What's new(changelog 入口,直抓 403=CF 拦截,浏览器可达)Make · What's new (changelog entry point; direct fetch 403 = Cloudflare block, reachable via browser) | https://www.make.com/en/whats-new |
实测记录Measured runs
本档未跑工作流搭建实测;结论只覆盖平台能力与权限边界。
This site has not completed measured runs. The closest test protocol is the code-side protocols/framework/_protocol.md (the tool-calling and credential-boundary sections are reusable; no workflow-platform-specific protocol exists on this site yet).
相关条目Related entries
- ZapierZapier表单派 vs 流程图派对照:同为连接器生态自动化,画布表达力是分野。Form-style vs flowchart-style contrast: both connector-ecosystem automation — canvas expressiveness is the divide.
- OpenAI Agents SDKOpenAI Agents SDK另一层 · 框架与运行时Other layer · Frameworks & runtimes
本页由This page is generated from the ai-handbook 数据层生成(CC BY 4.0)。data layer (CC BY 4.0).
方法论与坐标系定义见仓库内For the methodology and coordinate definitions, see METHODOLOGY.md.