用 AI 搭建工作流
把业务规则写成可以保存和检查的流程，再决定什么时候运行。这里用 Airtable 的联系人备注更新 Notion，不新建联系人。
下方提示词和代码保留原文。复制后，把示例中的占位值换成自己的资料。
开始前
在工作台的「连接」里授权 Airtable 和 Notion。Airtable 需要能访问源 base 和表，Notion 需要能访问目标数据源。先找出两边对应的 Email 和 Notes 字段。
可以用工作台助手，也可以在兼容客户端使用已授权的 B Square MCP 连接。下面的示例是给助手的提示词，不能当作 JSON 工作流导入。
1. 把业务规则说清楚
替换方括号里的名称，再粘贴：
Build and save an AgentOS workflow draft named “Sync contact notes”.
Source: Airtable base [BASE NAME], table [TABLE NAME].
Destination: Notion data source [DATA SOURCE NAME].
Trigger: a source record update.
Read the changed record. Match its Email to the Notion Email property using an exact match after trimming whitespace and lowercasing both values. Do not match by a person's name. Treat a blank email as no match.
If the complete search finds exactly one matching Notion page, update only its Notes property with the source Notes value. Preserve the source Notes text without rewriting it. If the source Notes is blank, skip the write. If the trimmed Notes text equals “REVIEW”, ask for my approval before writing. Rejecting approval must stop that write.
If there are zero or multiple matches, or the result set is incomplete, skip the write and notify me in AgentOS. Do not create a page or change any other property.
Read the current workflow catalog, action contracts, connection status, and actual resource schemas first. Ask if any named resource is ambiguous. Show the saved revision, validation, trigger, connections, and external writes. Do not publish, enable, or run it yet.明确匹配键、空值怎么处理，以及找不到唯一匹配时该怎么办。这些规则由你定。
2. 检查保存下来的工作流
打开实际保存的工作流。确认源和目标指向正确的 Airtable base、表和 Notion 数据源。只允许改 Notes，不创建联系人或页面。匹配规则要考虑分页和结果不完整的情况。例外写入前要先审批，拒绝后应停止。缺权限或字段有误，要能看到明确的报错。
需要修改时，在原对话里说明：
Update the same workflow draft. Change the approval keyword from “REVIEW” to “CHECK”. Preserve every other rule and connection. Validate it and show the new saved revision. Do not publish or run it.3. 分开处理发布、试跑和启用
保存、发布、启用自动触发和试跑是四项操作。刚发布时，自动触发处于暂停状态。确认版本后，用真实 ID 和版本号发布：
Publish workflow [WORKFLOW ID], saved revision [REVISION], with the trigger and external writes I just reviewed. Keep future triggers paused.选一条允许改动的记录试跑，测试也可能写入真实连接的应用：
Run the reviewed published version once using [TEST RECORD ID] and the required input schema. This test may update only the matching test page's Notes property. Show me the run ID and actual result. Do not enable future triggers.结果正确后，再决定是否启用后续触发：
Enable future triggers for workflow [WORKFLOW ID], published revision [REVISION]. Keep the reviewed matching, approval, and write limits unchanged.第二个例子：先制作，再审核发布
流程支持用模板生成海报和视频、人工审核，以及受支持的 Instagram 操作。从完整、已批准的模板输入开始。只有工具目录明确提供了准备步骤，才可以让定时流程自动写解说或选图。
Build a manual workflow draft named “Review listing campaign”.
Use my selected poster template [POSTER TEMPLATE ID] and video template [VIDEO TEMPLATE ID]. Accept separate, complete posterInputs and videoInputs matching those templates, plus my approved captions. Read the current template bodies and workflow node contracts before mapping them.
Generate the poster and video, wait for their delivered results, and present them for my approval. Only after approval, publish the poster and reel to my explicitly selected Instagram connection [CONNECTION NAME]. Use the stable image artifact reference and video delivery reference supported by the Instagram actions, not stored expiring download URLs. If generation fails or I reject the review, do not publish anything.
Show the real saved draft, validation, inputs, review step, and publishing effects. Do not publish, enable, render, or run this draft yet.Instagram 需要一个已授权且可用的专业账号连接。工具目录里有这项功能，并不代表你的账号已经授权。
查看运行结果
请助手返回完成的步骤、跳过的分支、审核记录和目标应用的实际结果。流程校验通过或成功发布，只能确认流程本身。Notion 有没有更新、Instagram 有没有发出，要看运行结果。写入结果不明时，先查原运行，再决定是否重试。
2026 年 11 月 9 日核对了工作流目录、人工输入、媒体制作规格及相关技能说明。示例没有在真实客户数据上启用或运行。