$npx -y skills add webflow/webflow-skills --skill bulk-cms-updateCreate or update multiple CMS items in a Webflow collection with validation and diff preview. Use when adding multiple blog posts, products, or updating fields across many items.
| 1 | # Bulk CMS Update |
| 2 | |
| 3 | Create or update multiple CMS items with comprehensive validation, granular approval, and rollback capability. |
| 4 | |
| 5 | ## Important Note |
| 6 | |
| 7 | **ALWAYS use Webflow MCP tools for all operations:** |
| 8 | - Use Webflow MCP's `data_sites_tool` with action `list_sites` for listing available sites |
| 9 | - Use Webflow MCP's `data_cms_tool` with action `get_collection_list` for listing CMS collections |
| 10 | - Use Webflow MCP's `data_cms_tool` with action `get_collection_details` for fetching collection schemas |
| 11 | - Use Webflow MCP's `data_cms_tool` with action `list_collection_items` for retrieving existing items |
| 12 | - Use Webflow MCP's `data_cms_tool` with action `create_collection_items` for creating items (draft or published) |
| 13 | - Use Webflow MCP's `data_cms_tool` with action `update_collection_items` for updating items (draft or published) |
| 14 | - Use Webflow MCP's `data_cms_tool` with action `publish_collection_items` for publishing draft items |
| 15 | - Use Webflow MCP's `webflow_guide_tool` to get best practices before starting |
| 16 | - DO NOT use any other tools or methods for Webflow operations |
| 17 | - All tool calls must include the required `context` parameter (15-25 words, third-person perspective) |
| 18 | |
| 19 | ## Instructions |
| 20 | |
| 21 | ### Phase 1: Site & Collection Selection |
| 22 | 1. **Get site**: Identify the target site. If user does not provide site ID, ask for it. |
| 23 | 2. **List collections**: Use Webflow MCP's `data_cms_tool` with action `get_collection_list` to show available collections |
| 24 | 3. **Ask user to select collection**: User specifies which collection to work with |
| 25 | 4. **Fetch collection schema**: Use Webflow MCP's `data_cms_tool` with action `get_collection_details` to retrieve: |
| 26 | - All field definitions with types |
| 27 | - Required vs optional fields |
| 28 | - Field validations (max length, patterns, etc.) |
| 29 | - Reference field targets |
| 30 | |
| 31 | ### Phase 2: Data Collection & Parsing |
| 32 | 5. **Ask operation type**: Clarify what user wants to do: |
| 33 | - Create new items only |
| 34 | - Update existing items only |
| 35 | - Both create and update |
| 36 | 6. **Receive data from user**: Accept data in flexible formats: |
| 37 | - Structured format (JSON-like) |
| 38 | - Natural language descriptions |
| 39 | - CSV-style data |
| 40 | - Bullet lists |
| 41 | 7. **Parse and normalize**: Convert user data into structured format |
| 42 | 8. **Fetch existing items** (if updates involved): Use Webflow MCP's `data_cms_tool` with action `list_collection_items` to get current data |
| 43 | |
| 44 | **IMPORTANT - Efficient Item Lookup:** |
| 45 | - When searching for specific items by name, ALWAYS use the `name` parameter to filter (e.g., `name: "Pikachu"`) |
| 46 | - When searching by slug, use the `slug` parameter to filter |
| 47 | - NEVER fetch all items first and then search through the results - this wastes API calls and tokens |
| 48 | - Only fetch the full list when you need to display all items or don't know which specific items to target |
| 49 | |
| 50 | ### Phase 3: Validation & Analysis |
| 51 | 9. **Validate all data**: |
| 52 | - **Field names**: Check all field names exist in schema |
| 53 | - **Required fields**: Ensure all required fields are provided |
| 54 | - **Field types**: Validate data types match schema |
| 55 | - **Constraints**: Check max lengths, patterns, allowed values |
| 56 | - **Slugs**: Ensure slugs are unique and valid |
| 57 | - **Reference fields**: Verify referenced items exist |
| 58 | 10. **Detect conflicts**: |
| 59 | - Duplicate slugs (within batch or with existing items) |
| 60 | - Missing required fields |
| 61 | - Invalid data types |
| 62 | - Constraint violations |
| 63 | 11. **Analyze impact**: |
| 64 | - Count creates vs updates |
| 65 | - Identify which fields will change |
| 66 | - Calculate batch size and processing time |
| 67 | |
| 68 | ### Phase 4: Preview & Granular Approval |
| 69 | 12. **Generate detailed preview**: |
| 70 | - Show each item with validation status |
| 71 | - Display warnings for any issues |
| 72 | - For updates, show diffs (old → new) |
| 73 | - For creates, show all field values |
| 74 | - Number each item for selective approval |
| 75 | 13. **Present granular approval options**: |
| 76 | - Allow user to select specific items to process |
| 77 | - Options: "all", "none", specific numbers, number ranges |
| 78 | - Show estimated processing time |
| 79 | 14. **Offer publish options**: |
| 80 | - Publish immediately (use `*_live` endpoints) |
| 81 | - Create as drafts (use regular endpoints + manual publish) |
| 82 | |
| 83 | ### Phase 5: Execution & Reporting |
| 84 | 15. **Store rollback data**: Before any changes, save: |
| 85 | - Original values for all updated items |
| 86 | - Timestamp |
| 87 | - Operation details |
| 88 | 16. **Process in batches**: |
| 89 | - Maximum 50 items per batch |
| 90 | - Show progress indicator |
| 91 | - Handle rate limits gracefully |
| 92 | 17. **Execute operations**: Use appropriate Webflow MCP tools based on user choice |
| 93 | 18. **Handle errors gracefully**: |
| 94 | - Continue processing on single item failures |
| 95 | - Track successes and failures separately |
| 96 | - Provide detailed error messages |
| 97 | 19. **Generate comprehensive report**: |
| 98 | - Summary (su |