bulk-cms-update
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseBulk CMS Update
批量CMS更新
Create or update multiple CMS items with comprehensive validation, granular approval, and rollback capability.
创建或更新多个CMS项目,支持全面验证、精细化审批和回滚功能。
Important Note
重要说明
ALWAYS use Webflow MCP tools for all operations:
- Use Webflow MCP's with action
data_sites_toolfor listing available siteslist_sites - Use Webflow MCP's with action
data_cms_toolfor listing CMS collectionsget_collection_list - Use Webflow MCP's with action
data_cms_toolfor fetching collection schemasget_collection_details - Use Webflow MCP's with action
data_cms_toolfor retrieving existing itemslist_collection_items - Use Webflow MCP's with action
data_cms_toolfor creating items (draft or published)create_collection_items - Use Webflow MCP's with action
data_cms_toolfor updating items (draft or published)update_collection_items - Use Webflow MCP's with action
data_cms_toolfor publishing draft itemspublish_collection_items - Use Webflow MCP's to get best practices before starting
webflow_guide_tool - DO NOT use any other tools or methods for Webflow operations
- All tool calls must include the required parameter (15-25 words, third-person perspective)
context
所有操作请务必使用Webflow MCP工具:
- 使用Webflow MCP的,指定action为
data_sites_tool来列出可用站点list_sites - 使用Webflow MCP的,指定action为
data_cms_tool来列出CMS集合get_collection_list - 使用Webflow MCP的,指定action为
data_cms_tool来获取集合架构get_collection_details - 使用Webflow MCP的,指定action为
data_cms_tool来检索现有项目list_collection_items - 使用Webflow MCP的,指定action为
data_cms_tool来创建项目(草稿或已发布)create_collection_items - 使用Webflow MCP的,指定action为
data_cms_tool来更新项目(草稿或已发布)update_collection_items - 使用Webflow MCP的,指定action为
data_cms_tool来发布草稿项目publish_collection_items - 在开始操作前,使用Webflow MCP的获取最佳实践
webflow_guide_tool - 请勿使用任何其他工具或方法执行Webflow操作
- 所有工具调用必须包含必填的参数(15-25个单词,第三人称视角)
context
Instructions
操作步骤
Phase 1: Site & Collection Selection
阶段1:站点与集合选择
- Get site: Identify the target site. If user does not provide site ID, ask for it.
- List collections: Use Webflow MCP's with action
data_cms_toolto show available collectionsget_collection_list - Ask user to select collection: User specifies which collection to work with
- Fetch collection schema: Use Webflow MCP's with action
data_cms_toolto retrieve:get_collection_details- All field definitions with types
- Required vs optional fields
- Field validations (max length, patterns, etc.)
- Reference field targets
- 获取站点:确定目标站点。如果用户未提供站点ID,请向用户索要。
- 列出集合:使用Webflow MCP的,指定action为
data_cms_tool来显示可用集合get_collection_list - 请用户选择集合:用户指定要操作的集合
- 获取集合架构:使用Webflow MCP的,指定action为
data_cms_tool来检索:get_collection_details- 所有字段的定义及类型
- 必填字段与可选字段
- 字段验证规则(最大长度、格式等)
- 引用字段的目标对象
Phase 2: Data Collection & Parsing
阶段2:数据收集与解析
-
Ask operation type: Clarify what user wants to do:
- Create new items only
- Update existing items only
- Both create and update
-
Receive data from user: Accept data in flexible formats:
- Structured format (JSON-like)
- Natural language descriptions
- CSV-style data
- Bullet lists
-
Parse and normalize: Convert user data into structured format
-
Fetch existing items (if updates involved): Use Webflow MCP'swith action
data_cms_toolto get current datalist_collection_itemsIMPORTANT - Efficient Item Lookup:- When searching for specific items by name, ALWAYS use the parameter to filter (e.g.,
name)name: "Pikachu" - When searching by slug, use the parameter to filter
slug - NEVER fetch all items first and then search through the results - this wastes API calls and tokens
- Only fetch the full list when you need to display all items or don't know which specific items to target
- When searching for specific items by name, ALWAYS use the
-
确认操作类型:明确用户需求:
- 仅创建新项目
- 仅更新现有项目
- 同时创建和更新
-
接收用户数据:支持多种灵活格式的数据输入:
- 结构化格式(类JSON)
- 自然语言描述
- CSV风格数据
- 项目符号列表
-
解析并标准化:将用户数据转换为结构化格式
-
获取现有项目(若涉及更新):使用Webflow MCP的,指定action为
data_cms_tool来获取当前数据list_collection_items重要提示 - 高效项目查找:- 当按名称查找特定项目时,请务必使用参数进行过滤(例如:
name)name: "Pikachu" - 当按slug查找时,使用参数进行过滤
slug - 切勿先获取所有项目再手动搜索结果——这会浪费API调用和令牌
- 仅当需要显示所有项目或不知道目标项目时,才获取完整列表
- 当按名称查找特定项目时,请务必使用
Phase 3: Validation & Analysis
阶段3:验证与分析
- Validate all data:
- Field names: Check all field names exist in schema
- Required fields: Ensure all required fields are provided
- Field types: Validate data types match schema
- Constraints: Check max lengths, patterns, allowed values
- Slugs: Ensure slugs are unique and valid
- Reference fields: Verify referenced items exist
- Detect conflicts:
- Duplicate slugs (within batch or with existing items)
- Missing required fields
- Invalid data types
- Constraint violations
- Analyze impact:
- Count creates vs updates
- Identify which fields will change
- Calculate batch size and processing time
- 全面验证数据:
- 字段名称:检查所有字段名称是否存在于架构中
- 必填字段:确保所有必填字段都已提供
- 字段类型:验证数据类型与架构匹配
- 约束规则:检查最大长度、格式、允许值
- Slug:确保slug唯一且有效
- 引用字段:验证被引用的项目是否存在
- 检测冲突:
- 重复的slug(在批量内或与现有项目重复)
- 缺失必填字段
- 无效数据类型
- 违反约束规则
- 分析影响:
- 统计创建与更新的数量
- 确定哪些字段会被修改
- 计算批量大小和处理时间
Phase 4: Preview & Granular Approval
阶段4:预览与精细化审批
- Generate detailed preview:
- Show each item with validation status
- Display warnings for any issues
- For updates, show diffs (old → new)
- For creates, show all field values
- Number each item for selective approval
- Present granular approval options:
- Allow user to select specific items to process
- Options: "all", "none", specific numbers, number ranges
- Show estimated processing time
- Offer publish options:
- Publish immediately (use endpoints)
*_live - Create as drafts (use regular endpoints + manual publish)
- Publish immediately (use
- 生成详细预览:
- 显示每个项目的验证状态
- 展示所有问题警告
- 对于更新操作,显示差异(旧值→新值)
- 对于创建操作,显示所有字段值
- 为每个项目编号,方便选择性审批
- 提供精细化审批选项:
- 允许用户选择要处理的特定项目
- 选项:“全部”、“无”、特定编号、编号范围
- 显示预估处理时间
- 提供发布选项:
- 立即发布(使用端点)
*_live - 创建为草稿(使用常规端点 + 手动发布)
- 立即发布(使用
Phase 5: Execution & Reporting
阶段5:执行与报告
- Store rollback data: Before any changes, save:
- Original values for all updated items
- Timestamp
- Operation details
- Process in batches:
- Maximum 50 items per batch
- Show progress indicator
- Handle rate limits gracefully
- Execute operations: Use appropriate Webflow MCP tools based on user choice
- Handle errors gracefully:
- Continue processing on single item failures
- Track successes and failures separately
- Provide detailed error messages
- Generate comprehensive report:
- Summary (success/failure counts)
- Detailed results per item
- Item IDs for created/updated items
- Error details for failed items
- Offer rollback option: Allow user to undo changes if needed
- 存储回滚数据:在进行任何更改前,保存:
- 所有待更新项目的原始值
- 时间戳
- 操作详情
- 批量处理:
- 每批最多处理50个项目
- 显示进度指示器
- 优雅处理速率限制
- 执行操作:根据用户选择使用相应的Webflow MCP工具
- 优雅处理错误:
- 单个项目失败时继续处理其他项目
- 分别跟踪成功和失败的项目
- 提供详细的错误信息
- 生成全面报告:
- 摘要(成功/失败数量)
- 每个项目的详细结果
- 已创建/更新项目的ID
- 失败项目的错误详情
- 提供回滚选项:允许用户在需要时撤销更改
Examples
示例
User prompt:
Add 2 blog posts about Webflow MCP and update the first blog to say "Top" instead of "Best"Step 1: Site & Collection Selection
📋 Bulk CMS Update Setup
Available Sites:
1. MCP Demo#1
2. MCP Demo#2
3. MCP Demo#3
Please select a site (1-3):User selects: 1
Available Collections in MCP Demo#1:
└── Blog Posts (9 items)
Fields: name, slug, post-body, post-summary, main-image, thumbnail-image, featured, color
Proceed with Blog Posts collection? (yes/no)User confirms: yes
Step 2: Data Collection
🔍 Collection Schema: Blog Posts
Required Fields:
- name (PlainText, max 256 chars)
- slug (PlainText, max 256 chars, alphanumeric only)
Optional Fields:
- post-body (RichText)
- post-summary (PlainText)
- main-image (Image)
- thumbnail-image (Image)
- featured (Switch, true/false)
- color (Color, hex format)
I'll parse your request:
- Create 2 new posts about Webflow MCP
- Update first post: "Best" → "Top"
Generating items...Step 3: Validation & Preview
📋 Preview: Bulk CMS Update
Collection: Blog Posts
Operations: Create 2 items + Update 1 item
---用户请求:
添加2篇关于Webflow MCP的博客文章,并将第一篇博客的“Best”改为“Top”步骤1:站点与集合选择
📋 批量CMS更新设置
可用站点:
1. MCP Demo#1
2. MCP Demo#2
3. MCP Demo#3
请选择站点(1-3):用户选择:1
MCP Demo#1中的可用集合:
└── 博客文章(9个项目)
字段:name, slug, post-body, post-summary, main-image, thumbnail-image, featured, color
是否继续使用博客文章集合?(是/否)用户确认:是
步骤2:数据收集
🔍 集合架构:博客文章
必填字段:
- name(纯文本,最大256字符)
- slug(纯文本,最大256字符,仅允许字母数字)
可选字段:
- post-body(富文本)
- post-summary(纯文本)
- main-image(图片)
- thumbnail-image(图片)
- featured(开关,true/false)
- color(颜色,十六进制格式)
我将解析您的请求:
- 创建2篇关于Webflow MCP的新文章
- 更新第一篇文章:将“Best”改为“Top”
正在生成项目...步骤3:验证与预览
📋 预览:批量CMS更新
集合:博客文章
操作:创建2个项目 + 更新1个项目
---🆕 Items to Create (2)
🆕 待创建项目(2个)
[1] ✓ NEW POST
name: "Webflow MCP: The Future of Web Development"
slug: "webflow-mcp-future-web-development"
post-summary: "Discover how Webflow MCP is revolutionizing..."
post-body: "<h1>The Future is Here</h1><p>..."
featured: true
color: "#9B59B6"
✅ All validations passed
[2] ✓ NEW POST
name: "Why Webflow MCP Will Transform Your Workflow in 2026"
slug: "webflow-mcp-transform-workflow-2026"
post-summary: "Learn how Webflow MCP's integration..."
post-body: "<h1>Transform Your Workflow</h1><p>..."
featured: true
color: "#3498DB"
✅ All validations passed
[1] ✓ 新文章
name: "Webflow MCP:Web开发的未来"
slug: "webflow-mcp-future-web-development"
post-summary: "探索Webflow MCP如何革新..."
post-body: "<h1>未来已来</h1><p>..."
featured: true
color: "#9B59B6"
✅ 所有验证已通过
[2] ✓ 新文章
name: "为什么Webflow MCP将在2026年改变您的工作流程"
slug: "webflow-mcp-transform-workflow-2026"
post-summary: "了解Webflow MCP的集成..."
post-body: "<h1>转变您的工作流程</h1><p>..."
featured: true
color: "#3498DB"
✅ 所有验证已通过
✏️ Items to Update (1)
✏️ 待更新项目(1个)
[3] ✓ UPDATE EXISTING
Item ID: 69615f84fc6ce1aa444d24d5
Slug: why-webflow-is-best-2026-ai
Changes:
name: "Why Webflow is the Best Choice for 2026" → "Why Webflow is the Top Choice for 2026"
✅ All validations passedSummary:
- ✅ 2 items will be created
- ✅ 1 item will be updated
- ⚠️ 0 warnings
- ❌ 0 errors
Publish Options:
- Publish immediately (recommended)
- Save as drafts
Which items would you like to process?
- Type "all" to process all 3 items
- Type numbers to skip (e.g., "2" to skip item 2)
- Type "none" to cancel
Select publish option (1/2): _
Select items: _
*User selects: 1, all*
⚠️ You're about to:
- Create 2 new blog posts (published live)
- Update 1 existing blog post (changes published live)
Type "confirm" to proceed.
*User confirms: confirm*
**Step 4: Execution & Results**🔄 Processing bulk update...
Creating items: ██████████ 100% (2/2)
Updating items: ██████████ 100% (1/1)
✅ Bulk CMS Update Complete!
[3] ✓ 更新现有项目
项目ID: 69615f84fc6ce1aa444d24d5
Slug: why-webflow-is-best-2026-ai
更改内容:
name: "Why Webflow is the Best Choice for 2026" → "Why Webflow is the Top Choice for 2026"
✅ 所有验证已通过摘要:
- ✅ 将创建2个项目
- ✅ 将更新1个项目
- ⚠️ 0条警告
- ❌ 0个错误
发布选项:
- 立即发布(推荐)
- 保存为草稿
您希望处理哪些项目?
- 输入"all"处理全部3个项目
- 输入编号跳过指定项目(例如:"2"跳过项目2)
- 输入"none"取消操作
选择发布选项(1/2):_
选择项目:_
*用户选择:1, all*
⚠️ 您即将执行以下操作:
- 创建2篇新博客文章(实时发布)
- 更新1篇现有博客文章(更改实时发布)
输入"confirm"继续。
*用户确认:confirm*
**步骤4:执行与结果**🔄 正在处理批量更新...
创建项目:██████████ 100% (2/2)
更新项目:██████████ 100% (1/1)
✅ 批量CMS更新完成!
🆕 Created Items (2)
🆕 已创建项目(2个)
✓ [1] "Webflow MCP: The Future of Web Development"
ID: 6961640c66de07bed9aacf3e
Slug: webflow-mcp-future-web-development
Published: Jan 9, 2026, 8:24 PM
✓ [2] "Why Webflow MCP Will Transform Your Workflow in 2026"
ID: 6961640c66de07bed9aacf41
Slug: webflow-mcp-transform-workflow-2026
Published: Jan 9, 2026, 8:24 PM
✓ [1] "Webflow MCP:Web开发的未来"
ID: 6961640c66de07bed9aacf3e
Slug: webflow-mcp-future-web-development
发布时间: 2026年1月9日 晚上8:24
✓ [2] "为什么Webflow MCP将在2026年改变您的工作流程"
ID: 6961640c66de07bed9aacf41
Slug: webflow-mcp-transform-workflow-2026
发布时间: 2026年1月9日 晚上8:24
✏️ Updated Items (1)
✏️ 已更新项目(1个)
✓ [3] "Why Webflow is the Top Choice for 2026"
ID: 69615f84fc6ce1aa444d24d5
Changed: title updated
Published: Jan 9, 2026, 8:24 PM
Summary:
- ✅ 2 items created successfully
- ✅ 1 item updated successfully
- ❌ 0 failures
- ⏱️ Completed in 3.2 seconds
Total Items: 11 (was 9)
📋 Rollback Available:
Last update: 3 items modified just now
Type "undo" within 5 minutes to revert all changes
**Alternative: With Validation Warnings**📋 Preview: Bulk CMS Update
[1] ⚠️ NEW POST
name: "Test Post"
slug: "test"
post-summary: "Hi"
⚠️ Warning: post-summary too short (< 20 chars) - may affect SEO
⚠️ Warning: slug too generic - consider more descriptive slug
⚠️ Warning: missing post-body - content will be empty
✅ Required fields present (can proceed)
[2] ❌ NEW POST
name: "Another Post!!!"
slug: "another post"
❌ Error: slug contains spaces (must be alphanumeric with hyphens only)
❌ Error: name contains special characters not allowed
🔴 Cannot proceed - fix errors first
Summary:
- ✅ 1 item can be created (with warnings)
- ❌ 1 item has errors (cannot create)
Fix item 2 or skip it? (fix/skip)
undefined✓ [3] "Why Webflow is the Top Choice for 2026"
ID: 69615f84fc6ce1aa444d24d5
更改内容:标题已更新
发布时间: 2026年1月9日 晚上8:24
摘要:
- ✅ 成功创建2个项目
- ✅ 成功更新1个项目
- ❌ 0个失败项目
- ⏱️ 耗时3.2秒
项目总数:11个(原9个)
📋 支持回滚:
最近更新:刚刚修改了3个项目
请在5分钟内输入"undo"撤销所有更改
**另一个示例:包含验证警告**📋 预览:批量CMS更新
[1] ⚠️ 新文章
name: "测试文章"
slug: "test"
post-summary: "你好"
⚠️ 警告:post-summary过短(<20字符)- 可能影响SEO
⚠️ 警告:slug过于通用 - 建议使用更具描述性的slug
⚠️ 警告:缺少post-body - 内容将为空
✅ 必填字段已提供(可继续操作)
[2] ❌ 新文章
name: "另一篇文章!!!"
slug: "another post"
❌ 错误:slug包含空格(仅允许字母数字和连字符)
❌ 错误:name包含不允许的特殊字符
🔴 无法继续 - 请先修复错误
摘要:
- ✅ 1个项目可创建(含警告)
- ❌ 1个项目存在错误(无法创建)
修复项目2还是跳过?(修复/跳过)
undefinedGuidelines
指南
Phase 1: Critical Requirements
阶段1:关键要求
Site & Collection Selection:
- Always fetch actual site list using
sites_list - Never assume site IDs
- Show collection names and item counts
- Display field schema before accepting data
- Confirm collection selection with user
站点与集合选择:
- 始终使用获取实际站点列表
sites_list - 切勿假设站点ID
- 显示集合名称和项目数量
- 在接收数据前显示字段架构
- 与用户确认集合选择
Phase 2: Data Parsing
阶段2:数据解析
Flexible Input Formats:
Accept data in multiple formats:
- Structured (JSON-like):
CREATE:
- name: "Post Title"
slug: "post-slug"
featured: true- Natural Language:
"Add a blog post called 'Getting Started' with slug 'getting-started'"- CSV-style:
name,slug,featured
"Post 1","post-1",true
"Post 2","post-2",false- Bullet Lists:
- Post 1: "Title" (slug: title-slug)
- Post 2: "Another" (slug: another-slug)Parsing Rules:
- Be lenient with format variations
- Infer missing optional fields
- Ask for clarification if ambiguous
- Never assume required field values
Efficient Item Lookup:
When fetching existing items for updates, use filter parameters to minimize API calls:
undefined灵活输入格式:
支持多种数据格式:
- 结构化(类JSON):
CREATE:
- name: "文章标题"
slug: "post-slug"
featured: true- 自然语言:
"添加一篇名为'入门指南'的博客文章,slug为'getting-started'"- CSV风格:
name,slug,featured
"文章1","post-1",true
"文章2","post-2",false- 项目符号列表:
- 文章1:"标题"(slug: title-slug)
- 文章2:"另一篇"(slug: another-slug)解析规则:
- 对格式变体保持宽容
- 推断缺失的可选字段
- 若存在歧义,请向用户确认
- 切勿假设必填字段的值
高效项目查找:
当获取现有项目进行更新时,使用过滤参数减少API调用:
undefinedGood - Filter by name when you know the item name
推荐 - 已知项目名称时按名称过滤
collections_items_list_items(collection_id, name: "Pikachu")
collections_items_list_items(collection_id, name: "Pikachu")
Good - Filter by slug when you know the slug
推荐 - 已知slug时按slug过滤
collections_items_list_items(collection_id, slug: "pikachu")
collections_items_list_items(collection_id, slug: "pikachu")
Bad - Fetching all items then searching through results
不推荐 - 获取所有项目再手动搜索
collections_items_list_items(collection_id) # Returns 100 items
collections_items_list_items(collection_id) # 返回100个项目
Then manually searching for "Pikachu" in results...
然后在结果中手动搜索"Pikachu"...
- ALWAYS use `name` or `slug` parameters when searching for specific items
- This reduces API calls, response size, and token usage
- Only fetch unfiltered lists when displaying all items or when the target is unknown
- 查找特定项目时,请务必使用`name`或`slug`参数
- 这会减少API调用、响应大小和令牌消耗
- 仅当显示所有项目或未知目标项目时,才获取未过滤的列表Phase 3: Validation Rules
阶段3:验证规则
Field Name Validation:
- Check all field names exist in schema
- Case-sensitive matching
- Suggest corrections for typos
- Example: "autor" → Did you mean "author"?
Required Fields:
- and
nameare ALWAYS required for Webflow CMSslug - Check collection-specific required fields from schema
- List all missing required fields clearly
- Cannot proceed if required fields missing
Field Type Validation:
PlainText:
- Check max length constraints
- Validate patterns if specified
- No HTML allowed
RichText:
- Must be valid HTML
- Check for unclosed tags
- Allow common HTML elements
Image/File:
- Accept file IDs or URLs
- Validate file exists (if possible)
- Optional alt text
Switch (Boolean):
- Accept: true/false, yes/no, 1/0
- Normalize to boolean
Color:
- Must be hex format (#RRGGBB)
- Validate hex characters
- Example: #FF5733 ✓, red ✗
Reference Fields:
- Must reference existing item IDs
- Validate referenced items exist
- Show referenced item names for clarity
Slug Validation:
- CRITICAL: Must be alphanumeric with hyphens only
- No spaces, underscores, or special characters
- Max 256 characters
- Must be unique (check against existing + batch)
- Auto-suggest slugs from titles if missing
- Example:
- ❌ "My Post!" → ⚠️ Contains special characters
- ✅ "my-post" → Valid
Constraint Validation:
- Max length: Warn if approaching limit, error if exceeds
- Patterns: Test regex patterns from schema
- Allowed values: Check against enumerated options
字段名称验证:
- 检查所有字段名称是否存在于架构中
- 区分大小写匹配
- 为拼写错误提供修正建议
- 示例:"autor" → 是否指"author"?
必填字段:
- 和
name是Webflow CMS的必填字段slug - 根据集合架构检查特定的必填字段
- 清晰列出所有缺失的必填字段
- 若缺失必填字段,无法继续操作
字段类型验证:
纯文本:
- 检查最大长度约束
- 若有指定,验证格式
- 不允许HTML
富文本:
- 必须是有效的HTML
- 检查未闭合的标签
- 允许常见HTML元素
图片/文件:
- 接受文件ID或URL
- 尽可能验证文件是否存在
- 可选替代文本
开关(布尔值):
- 接受:true/false、是/否、1/0
- 标准化为布尔值
颜色:
- 必须是十六进制格式(#RRGGBB)
- 验证十六进制字符
- 示例:#FF5733 ✓, red ✗
引用字段:
- 必须引用现有项目的ID
- 验证被引用的项目是否存在
- 显示被引用项目的名称以便清晰识别
Slug验证:
- 关键要求:仅允许字母数字和连字符
- 不允许空格、下划线或特殊字符
- 最大256字符
- 必须唯一(检查批量内和现有项目)
- 若缺失,根据标题自动生成slug建议
- 示例:
- ❌ "My Post!" → ⚠️ 包含特殊字符
- ✅ "my-post" → 有效
约束验证:
- 最大长度:接近限制时发出警告,超过时报错
- 格式:测试架构中的正则表达式
- 允许值:检查是否在枚举选项范围内
Phase 4: Preview & Approval
阶段4:预览与审批
Preview Format:
For Create Operations:
[1] ✓ NEW POST
field1: "value1"
field2: "value2"
field3: "value3"
✅ All validations passedFor Update Operations:
[2] ✓ UPDATE EXISTING
Item ID: xxx
Slug: existing-slug
Changes:
field1: "old value" → "new value"
field2: (no change)
field3: "old" → "new"
✅ All validations passedFor Items with Warnings:
[3] ⚠️ NEW POST
name: "Title"
⚠️ Warning: Missing optional field 'post-body'
⚠️ Warning: Slug may be too generic
✅ Can proceed (warnings only)For Items with Errors:
[4] ❌ NEW POST
name: "Title!!!"
slug: "bad slug"
❌ Error: slug contains spaces
❌ Error: name has special characters
🔴 Cannot proceed - must fix errorsGranular Approval:
- Number each item: [1], [2], [3]...
- Allow selective processing
- Accept formats:
- "all" - process everything
- "none" - cancel operation
- "1,3,5" - process items 1, 3, and 5
- "1-5" - process items 1 through 5
- "2" - skip only item 2, process rest
Publish Options:
- Immediate publish: Use endpoints (recommended)
*_live - Draft mode: Use regular endpoints, publish later
- Explain implications of each choice
预览格式:
创建操作:
[1] ✓ 新文章
field1: "value1"
field2: "value2"
field3: "value3"
✅ 所有验证已通过更新操作:
[2] ✓ 更新现有项目
项目ID: xxx
Slug: existing-slug
更改内容:
field1: "旧值" → "新值"
field2: (无更改)
field3: "旧值" → "新值"
✅ 所有验证已通过含警告的项目:
[3] ⚠️ 新文章
name: "标题"
⚠️ 警告:缺少可选字段'post-body'
⚠️ 警告:slug可能过于通用
✅ 可继续操作(仅含警告)含错误的项目:
[4] ❌ 新文章
name: "标题!!!"
slug: "bad slug"
❌ 错误:slug包含空格
❌ 错误:name包含特殊字符
🔴 无法继续 - 必须先修复错误精细化审批:
- 为每个项目编号:[1], [2], [3]...
- 支持选择性处理
- 接受以下格式:
- "all" - 处理所有项目
- "none" - 取消操作
- "1,3,5" - 处理项目1、3和5
- "1-5" - 处理项目1至5
- "2" - 仅跳过项目2,处理其余项目
发布选项:
- 立即发布:使用端点(推荐)
*_live - 草稿模式:使用常规端点,稍后发布
- 解释每个选项的影响
Phase 5: Execution & Reporting
阶段5:执行与报告
Batch Processing:
- Maximum 50 items per batch
- Show progress bar:
Processing: ████████░░ 80% (40/50 items) - Estimated time remaining
- Handle rate limits (pause/retry)
Error Handling:
For Single Item Failures:
Processing item 3/10...
❌ Failed: "Post Title"
Error: Slug already exists
→ Skipping to next itemContinue Processing:
- Don't fail entire batch for one error
- Track all successes and failures
- Report both separately
For Critical Failures:
❌ Critical Error: API connection lost
Items processed before error: 7/50
- 5 created successfully
- 2 updated successfully
- 43 not processed
Retry failed items? (yes/no)Success Report Format:
✅ Operation Complete
Created: 25 items
- Show first 5 with IDs
- "[+20 more]" if > 5
Updated: 10 items
- Show first 5 with IDs
- "[+5 more]" if > 5
Failed: 2 items
- "Item Name": Error reason
- "Item Name": Error reason
Total time: 12.5 seconds
Items per second: 2.8Rollback Capability:
Store Before Changes:
json
{
"timestamp": "2026-01-09T20:24:44Z",
"operations": [
{
"type": "update",
"itemId": "xxx",
"originalValues": {
"name": "Old Title",
"featured": false
},
"newValues": {
"name": "New Title",
"featured": true
}
}
]
}Offer Rollback:
📋 Rollback Available:
Last update: 15 items modified 2 minutes ago
Rollback will:
- Restore 10 updated items to previous values
- Delete 5 newly created items
⚠️ Type "undo" to rollback all changes
⚠️ Rollback expires in 3 minutes批量处理:
- 每批最多处理50个项目
- 显示进度条:
处理中:████████░░ 80% (40/50个项目) - 显示剩余预估时间
- 优雅处理速率限制(暂停/重试)
错误处理:
单个项目失败:
正在处理项目3/10...
❌ 失败:"文章标题"
错误:Slug已存在
→ 跳至下一个项目继续处理:
- 切勿因单个项目错误导致整个批量失败
- 跟踪所有成功和失败的项目
- 分别报告两者
严重失败:
❌ 严重错误:API连接中断
错误发生前已处理项目:7/50
- 5个项目创建成功
- 2个项目更新成功
- 43个项目未处理
是否重试失败的项目?(是/否)成功报告格式:
✅ 操作完成
已创建:25个项目
- 显示前5个项目及ID
- 若超过5个,显示"[+20个更多]"
已更新:10个项目
- 显示前5个项目及ID
- 若超过5个,显示"[+5个更多]"
失败:2个项目
- "项目名称":错误原因
- "项目名称":错误原因
总耗时:12.5秒
每秒处理项目数:2.8回滚功能:
更改前存储数据:
json
{
"timestamp": "2026-01-09T20:24:44Z",
"operations": [
{
"type": "update",
"itemId": "xxx",
"originalValues": {
"name": "旧标题",
"featured": false
},
"newValues": {
"name": "新标题",
"featured": true
}
}
]
}提供回滚选项:
📋 支持回滚:
最近更新:2分钟前修改了15个项目
回滚将:
- 将10个更新项目恢复为之前的值
- 删除5个新建项目
⚠️ 输入"undo"回滚所有更改
⚠️ 回滚将在3分钟后过期Performance Optimization
性能优化
Batch Size:
- Default: 50 items per batch
- Adjust based on field complexity
- Heavy images: 20 items per batch
- Simple text fields: 100 items per batch
Progress Indicators:
Creating items...
Batch 1/3: ████████████████████ 100% (50/50)
Batch 2/3: ████████████████████ 100% (50/50)
Batch 3/3: ██████░░░░░░░░░░░░░░ 30% (15/50)Rate Limiting:
- Respect Webflow API rate limits
- Pause between batches if needed
- Show user why waiting
- Retry failed requests automatically (max 3 attempts)
批量大小:
- 默认:每批50个项目
- 根据字段复杂度调整
- 包含大量图片:每批20个项目
- 仅含简单文本字段:每批100个项目
进度指示器:
正在创建项目...
批次1/3:████████████████████ 100% (50/50)
批次2/3:████████████████████ 100% (50/50)
批次3/3:██████░░░░░░░░░░░░░░ 30% (15/50)速率限制:
- 遵守Webflow API速率限制
- 必要时在批次间暂停
- 向用户说明等待原因
- 自动重试失败请求(最多3次)
Error Messages
错误消息
Clear and Actionable:
❌ Bad:
"Error: validation failed"✅ Good:
"Validation Error on item 3:
- Slug 'my post' contains spaces
- Change to: 'my-post' (alphanumeric with hyphens only)"Error Categories:
- 🔴 Critical: Cannot proceed at all (API down, invalid auth)
- ❌ Error: This item cannot be processed (fix or skip)
- ⚠️ Warning: Can proceed but not recommended (missing optional fields)
- 💡 Suggestion: Best practices (slug too generic, summary too short)
清晰且可操作:
❌ 不佳示例:
"错误:验证失败"✅ 良好示例:
"项目3验证错误:
- Slug 'my post'包含空格
- 建议修改为:'my-post'(仅允许字母数字和连字符)"错误分类:
- 🔴 严重错误:完全无法继续(API故障、无效授权)
- ❌ 错误:该项目无法处理(修复或跳过)
- ⚠️ 警告:可继续但不建议(缺少可选字段)
- 💡 建议:最佳实践(slug过于通用、摘要过短)
Best Practices
最佳实践
Always:
- ✅ Show preview before any changes
- ✅ Require explicit confirmation
- ✅ Validate all data thoroughly
- ✅ Process in batches for large operations
- ✅ Report successes and failures separately
- ✅ Offer rollback for recent changes
- ✅ Use granular approval for flexibility
Never:
- ❌ Apply changes without user confirmation
- ❌ Fail entire batch for single item error
- ❌ Assume field names or values
- ❌ Process without validating first
- ❌ Hide validation warnings from user
Edge Cases:
- Duplicate slugs: Auto-append number (post-title-2)
- Missing optional fields: Leave empty (don't invent values)
- Large batches: Warn about processing time
- Reference fields: Validate targets exist
- Image fields: Accept URLs or file IDs
User Experience:
- Show collection schema upfront
- Number items for easy reference
- Use visual hierarchy (├── └──)
- Provide actionable error messages
- Estimate processing time
- Allow cancellation mid-process
请始终:
- ✅ 在进行任何更改前显示预览
- ✅ 要求用户明确确认
- ✅ 全面验证所有数据
- ✅ 对大型操作进行批量处理
- ✅ 分别报告成功和失败的项目
- ✅ 为最近的更改提供回滚选项
- ✅ 支持精细化审批以提升灵活性
请勿:
- ❌ 未经用户确认直接应用更改
- ❌ 因单个项目错误导致整个批量失败
- ❌ 假设字段名称或值
- ❌ 未验证就进行处理
- ❌ 向用户隐藏验证警告
边缘情况:
- 重复slug:自动追加数字(post-title-2)
- 缺失可选字段:留空(请勿自行生成值)
- 大型批量:警告用户处理时间
- 引用字段:验证目标对象存在
- 图片字段:接受URL或文件ID
用户体验:
- 提前显示集合架构
- 为项目编号以便引用
- 使用可视化层级(├── └──)
- 提供可操作的错误消息
- 预估处理时间
- 允许用户中途取消操作