Pipedream(Connect / Workflows)Pipedream(Connect / Workflows)
Pipedream 是「开发者向」的自动化平台:代码步骤(Node/Python/Bash)是一等公民,界面是搭流程的壳; Connect 线让「你的应用」成为别人工作流里的节点——被集成是它的商业主轴。
Pipedream is the developer-facing automation platform: code steps (Node/Python/Bash) are first-class citizens, the UI is a flow-building shell; the Connect line makes *your app* a node inside other people's workflows — being integrated is its commercial axis.
适合与不适合When to use it, when not to
适合:工程师做自动化、要代码级控制又想要托管运行时与 OAuth 托管;SaaS 要做集成面(Connect)。 不适合:完全不想碰代码(去 Zapier/Make);要完整自托管(官方无此形态声明)。
A fit for: engineers automating, wanting code-level control plus a hosted runtime and managed OAuth; SaaS teams building an integration surface (Connect). Not a fit for teams that never touch code (go Zapier/Make); full self-hosting (no official statement of such a form).
中文生态China availability 国产 / 国内可直接用 / 备案状态 · 快照domestic / direct access / CAC filing · snapshot 2026-10-21
- 出品属地Origin
- 国外出品foreign-made Pipedream, Inc.(美国)。Pipedream, Inc. (US).
- 国内使用Direct access
- 大陆可直连direct OK pipedream.com / docs.pipedream.com 直连实测 200(2026-10-21)。pipedream.com / docs.pipedream.com measured 200 direct (2026-10-21).
- 备案状态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
工作流步骤可接各家 LLM(官方 AI 集成文档线);具体清单未逐条核验。 特色是「代码优先的自动化」:步骤可写 Node/Python/Bash,界面主轴仍是搭流程。
Workflow steps can connect to each vendor's LLMs (official AI-integration docs line); the specific list has not been verified item by item. The signature trait is "code-first automation": steps can be written in Node/Python/Bash, while the UI's main axis is still assembling flows.
- 运行位置Where it runs
云托管运行时(官方托管执行);另有本地 CLI/SDK 开发面。无完整自托管形态的官方声明。
Cloud-hosted runtime (officially managed execution); there is also a local CLI/SDK development surface. No official statement of a full self-hosted form.
- 本地文件Local files
执行在 Pipedream 云端;本机经 CLI/SDK 开发部署。
Execution happens on Pipedream's cloud; locally you develop and deploy via CLI/SDK.
- 关机后的任务Tasks after shutdown
云托管常驻是默认形态:定时调度、webhook、队列与重试由平台承载,本机只负责开发部署; 「电脑关了还能跑」在托管形态下天然成立。
Cloud-hosted residency is the default form: scheduling, webhooks, queues and retries are carried by the platform while your machine only handles development and deployment; "keeps running when your laptop is off" naturally holds in the hosted form.
- 工具与扩展Tools & extensions
官方组件生态(apps/components)+ Connect 嵌入式集成(把你的应用接进别人工作流); MCP 支持状态未逐条核验。
Official component ecosystem (apps/components) + Connect embedded integration (plugging your app into other people's workflows); MCP support status not verified item by item.
- 上下文与记忆Context & memory
工作流状态与 store 键值是官方持久面;跨流程记忆未逐条核验。
Workflow state and store key-values are the official persistence surface; cross-workflow memory not verified item by item.
- 权限与限制Permissions & limits
OAuth 凭据由平台托管(Connect 线是其商业主轴);企业合规声明未逐条核验。
OAuth credentials are hosted by the platform (the Connect line is its commercial main axis); enterprise-compliance claims not verified item by item.
- 适合什么任务Best for
适合:开发者向自动化(代码+界面混合)、要做「被集成」的 SaaS(Connect 线)。 不适合:完全不想碰代码的团队(那是 Zapier/Make 的地盘)。
Fits: developer-oriented automation (code + UI hybrid); SaaS wanting to be "integrated into" (Connect line). Does not fit: teams that never want to touch code (that's Zapier/Make territory).
头号误解Top misconception
- 把它归「纯低代码」——它是开发者向:代码步骤是一等公民,界面是搭流程的壳Filing it under “pure low-code” — it is developer-facing: code steps are first-class, the UI is a flow shell
- Connect 与 Workflows 是两条产品线(被集成 vs 自己自动化),档案合并写但读官方要分开Conflating Connect and Workflows — two product lines (being integrated vs. automating yourself); merged in this file, read them separately in official docs
未知项清单Known unknowns
- 各仓开源许可的全量口径(source-available 细节未逐仓核验)
- MCP 支持状态(未核验到官方文档)
- 自托管形态(官方无声明——按未知处理)
- The full per-repo open-source license picture (source-available details not verified repo by repo)
- MCP support status (no official documentation found)
- Self-hosted form (no official statement — treated as unknown)
证据来源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 | Pipedream · 官方文档Pipedream · official docs | https://docs.pipedream.com |
| docs | Pipedream · 官方首页(2026-10-21 直抓 200)Pipedream · official homepage (fetched directly 200 on 2026-10-21) | https://pipedream.com |
| changelog | Pipedream · 官方社区(更新与答疑入口)Pipedream · official community (updates and Q&A entry point) | https://pipedream.com/community |
实测记录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 代码派对照:同为连接器自动化,Pipedream 把代码当一等公民。Form-style vs code-style contrast: both connector automation — Pipedream treats code as a first-class citizen.
- 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.