webflow-automation
Scannednpx machina-cli add skill davepoon/buildwithclaude/webflow-automation --openclawWebflow Automation via Rube MCP
Automate Webflow operations including CMS collection management, site publishing, page inspection, asset uploads, and ecommerce order retrieval through Composio's Webflow toolkit.
Toolkit docs: composio.dev/toolkits/webflow
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Webflow connection via
RUBE_MANAGE_CONNECTIONSwith toolkitwebflow - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitwebflow - If connection is not ACTIVE, follow the returned auth link to complete Webflow OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Manage CMS Collection Items
When to use: User wants to create, update, list, or delete items in Webflow CMS collections (blog posts, products, team members, etc.)
Tool sequence:
WEBFLOW_LIST_WEBFLOW_SITES- List sites to find the target site_id [Prerequisite]WEBFLOW_LIST_COLLECTIONS- List all collections for the site [Prerequisite]WEBFLOW_GET_COLLECTION- Get collection schema to find valid field slugs [Prerequisite for create/update]WEBFLOW_LIST_COLLECTION_ITEMS- List existing items with filtering and pagination [Optional]WEBFLOW_GET_COLLECTION_ITEM- Get a specific item's full details [Optional]WEBFLOW_CREATE_COLLECTION_ITEM- Create a new item with field data [Required for creation]WEBFLOW_UPDATE_COLLECTION_ITEM- Update an existing item's fields [Required for updates]WEBFLOW_DELETE_COLLECTION_ITEM- Permanently remove an item [Optional]WEBFLOW_PUBLISH_SITE- Publish changes to make them live [Optional]
Key parameters for CREATE_COLLECTION_ITEM:
collection_id: 24-character hex string from LIST_COLLECTIONSfield_data: Object with field slug keys (NOT display names); must includenameandslugfield_data.name: Display name for the itemfield_data.slug: URL-friendly identifier (lowercase, hyphens, no spaces)is_draft: Boolean to create as draft (default false)
Key parameters for UPDATE_COLLECTION_ITEM:
collection_id: Collection identifieritem_id: 24-character hex MongoDB ObjectId of the existing itemfields: Object with field slug keys and new valueslive: Boolean to publish changes immediately (default false)
Field value types:
- Text/Email/Link/Date: string
- Number: integer or float
- Boolean: true/false
- Image:
{"url": "...", "alt": "...", "fileId": "..."} - Multi-reference: array of reference ID strings
- Multi-image: array of image objects
- Option: option ID string
Pitfalls:
- Field keys must use the exact field
slugfrom the collection schema, NOT display names - Always call
GET_COLLECTIONfirst to retrieve the schema and identify correct field slugs CREATE_COLLECTION_ITEMrequiresnameandsluginfield_dataUPDATE_COLLECTION_ITEMcannot create new items; it requires a valid existingitem_iditem_idmust be a 24-character hexadecimal MongoDB ObjectId- Slug must be lowercase alphanumeric with hyphens:
^[a-z0-9]+(?:-[a-z0-9]+)*$ - CMS items are staged; use
PUBLISH_SITEor setlive: trueto push to production
2. Manage Sites and Publishing
When to use: User wants to list sites, inspect site configuration, or publish staged changes
Tool sequence:
WEBFLOW_LIST_WEBFLOW_SITES- List all accessible sites [Required]WEBFLOW_GET_SITE_INFO- Get detailed site metadata including domains and settings [Optional]WEBFLOW_PUBLISH_SITE- Deploy all staged changes to live site [Required for publishing]
Key parameters for PUBLISH_SITE:
site_id: Site identifier from LIST_WEBFLOW_SITEScustom_domains: Array of custom domain ID strings (from GET_SITE_INFO)publish_to_webflow_subdomain: Boolean to publish to{shortName}.webflow.io- At least one of
custom_domainsorpublish_to_webflow_subdomainmust be specified
Pitfalls:
PUBLISH_SITErepublishes ALL staged changes for selected domains -- verify no unintended drafts are pending- Rate limit: 1 successful publish per minute
- For sites without custom domains, must set
publish_to_webflow_subdomain: true custom_domainsexpects domain IDs (hex strings), not domain names- Publishing is a production action -- always confirm with the user first
3. Manage Pages
When to use: User wants to list pages, inspect page metadata, or examine page DOM structure
Tool sequence:
WEBFLOW_LIST_WEBFLOW_SITES- Find the target site_id [Prerequisite]WEBFLOW_LIST_PAGES- List all pages for a site with pagination [Required]WEBFLOW_GET_PAGE- Get detailed metadata for a specific page [Optional]WEBFLOW_GET_PAGE_DOM- Get the DOM/content node structure of a static page [Optional]
Key parameters:
site_id: Site identifier (required for list pages)page_id: 24-character hex page identifierlocale_id: Optional locale filter for multi-language siteslimit: Max results per page (max 100)offset: Pagination offset
Pitfalls:
LIST_PAGESpaginates via offset/limit; iterate when sites have many pages- Page IDs are 24-character hex strings matching pattern
^[0-9a-fA-F]{24}$ GET_PAGE_DOMreturns the node structure, not rendered HTML- Pages include both static and CMS-driven pages
4. Upload Assets
When to use: User wants to upload images, files, or other assets to a Webflow site
Tool sequence:
WEBFLOW_LIST_WEBFLOW_SITES- Find the target site_id [Prerequisite]WEBFLOW_UPLOAD_ASSET- Upload a file with base64-encoded content [Required]
Key parameters:
site_id: Site identifierfile_name: Name of the file (e.g.,"logo.png")file_content: Base64-encoded binary content of the file (NOT a placeholder or URL)content_type: MIME type (e.g.,"image/png","image/jpeg","application/pdf")md5: MD5 hash of the raw file bytes (32-character hex string)asset_folder_id: Optional folder placement
Pitfalls:
file_contentmust be actual base64-encoded data, NOT a variable reference or placeholdermd5must be computed from the raw bytes, not from the base64 string- This is a two-step process internally: generates an S3 pre-signed URL, then uploads
- Large files may encounter timeouts; keep uploads reasonable in size
5. Manage Ecommerce Orders
When to use: User wants to view ecommerce orders from a Webflow site
Tool sequence:
WEBFLOW_LIST_WEBFLOW_SITES- Find the site with ecommerce enabled [Prerequisite]WEBFLOW_LIST_ORDERS- List all orders with optional status filtering [Required]WEBFLOW_GET_ORDER- Get detailed information for a specific order [Optional]
Key parameters:
site_id: Site identifier (must have ecommerce enabled)order_id: Specific order identifier for detailed retrievalstatus: Filter orders by status
Pitfalls:
- Ecommerce must be enabled on the Webflow site for order endpoints to work
- Order endpoints are read-only; no create/update/delete for orders through these tools
Common Patterns
ID Resolution
Webflow uses 24-character hexadecimal IDs throughout:
- Site ID:
WEBFLOW_LIST_WEBFLOW_SITES-- find by name, captureid - Collection ID:
WEBFLOW_LIST_COLLECTIONSwithsite_id - Item ID:
WEBFLOW_LIST_COLLECTION_ITEMSwithcollection_id - Page ID:
WEBFLOW_LIST_PAGESwithsite_id - Domain IDs:
WEBFLOW_GET_SITE_INFO-- found incustomDomainsarray - Field slugs:
WEBFLOW_GET_COLLECTION-- found in collectionfieldsarray
Pagination
Webflow uses offset-based pagination:
offset: Starting index (0-based)limit: Items per page (max 100)- Increment offset by limit until fewer results than limit are returned
- Available on: LIST_COLLECTION_ITEMS, LIST_PAGES
CMS Workflow
Typical CMS content creation flow:
- Get site_id from LIST_WEBFLOW_SITES
- Get collection_id from LIST_COLLECTIONS
- Get field schema from GET_COLLECTION (to learn field slugs)
- Create/update items using correct field slugs
- Publish site to make changes live
Known Pitfalls
ID Formats
- All Webflow IDs are 24-character hexadecimal strings (MongoDB ObjectIds)
- Example:
580e63fc8c9a982ac9b8b745 - Pattern:
^[0-9a-fA-F]{24}$ - Invalid IDs return 404 errors
Field Slugs vs Display Names
- CMS operations require field
slugvalues, NOT display names - A field with displayName "Author Name" might have slug
author-name - Always call
GET_COLLECTIONto discover correct field slugs - Using wrong field names silently ignores the data or causes validation errors
Publishing
PUBLISH_SITEdeploys ALL staged changes, not just specific items- Rate limited to 1 publish per minute
- Must specify at least one domain target (custom or webflow subdomain)
- This is a production-affecting action; always confirm intent
Authentication Scopes
- Different operations require different OAuth scopes:
sites:read,cms:read,cms:write,pages:read - A 403 error typically means missing OAuth scopes
- Check connection permissions if operations fail with authorization errors
Destructive Operations
DELETE_COLLECTION_ITEMpermanently removes CMS itemsPUBLISH_SITEmakes all staged changes live immediately- Always confirm with the user before executing these actions
Quick Reference
| Task | Tool Slug | Key Params |
|---|---|---|
| List sites | WEBFLOW_LIST_WEBFLOW_SITES | (none) |
| Get site info | WEBFLOW_GET_SITE_INFO | site_id |
| Publish site | WEBFLOW_PUBLISH_SITE | site_id, custom_domains or publish_to_webflow_subdomain |
| List collections | WEBFLOW_LIST_COLLECTIONS | site_id |
| Get collection schema | WEBFLOW_GET_COLLECTION | collection_id |
| List collection items | WEBFLOW_LIST_COLLECTION_ITEMS | collection_id, limit, offset |
| Get collection item | WEBFLOW_GET_COLLECTION_ITEM | collection_id, item_id |
| Create collection item | WEBFLOW_CREATE_COLLECTION_ITEM | collection_id, field_data |
| Update collection item | WEBFLOW_UPDATE_COLLECTION_ITEM | collection_id, item_id, fields |
| Delete collection item | WEBFLOW_DELETE_COLLECTION_ITEM | collection_id, item_id |
| List pages | WEBFLOW_LIST_PAGES | site_id, limit, offset |
| Get page | WEBFLOW_GET_PAGE | page_id |
| Get page DOM | WEBFLOW_GET_PAGE_DOM | page_id |
| Upload asset | WEBFLOW_UPLOAD_ASSET | site_id, file_name, file_content, content_type, md5 |
| List orders | WEBFLOW_LIST_ORDERS | site_id, status |
| Get order | WEBFLOW_GET_ORDER | site_id, order_id |
Powered by Composio
Source
git clone https://github.com/davepoon/buildwithclaude/blob/main/plugins/all-skills/skills/webflow-automation/SKILL.mdView on GitHub Overview
Automates Webflow tasks using Composio's Webflow toolkit via Rube MCP. It covers CMS collection management, site publishing, page inspection, asset uploads, and ecommerce orders. Always fetch current tool schemas with RUBE_SEARCH_TOOLS before running workflows.
How This Skill Works
Enable Rube MCP and Webflow connection, then execute Webflow tool actions in a defined sequence to manage collections, publish changes, or fetch orders. For each operation, fetch the latest collection schema with GET_COLLECTION to discover field slugs, then use CREATE or UPDATE with field_data keyed by slug. Always start by calling RUBE_SEARCH_TOOLS to retrieve current tool schemas before any workflow.
When to Use It
- Create, update, list, or delete items in a Webflow CMS collection (e.g., blog posts, products, team members).
- Update an existing CMS item by its 24-character MongoDB ObjectId (item_id).
- Publish staged changes to production using PUBLISH_SITE or by setting live: true on updates.
- Upload assets or manage assets for a Webflow site (e.g., images, files).
- Retrieve ecommerce orders for processing and fulfillment.
Quick Start
- Step 1: Verify MCP tool schemas by ensuring RUBE_SEARCH_TOOLS responds.
- Step 2: Connect to Webflow via RUBE_MANAGE_CONNECTIONS with toolkit 'webflow' and complete OAuth if prompted.
- Step 3: Run a small workflow (e.g., WEBFLOW_LIST_WEBFLOW_SITES → WEBFLOW_LIST_COLLECTIONS → WEBFLOW_GET_COLLECTION → WEBFLOW_CREATE_COLLECTION_ITEM) to create a sample item.
Best Practices
- Always call GET_COLLECTION first to obtain the exact field slugs from the collection schema.
- Use field_data with keys that match collection slugs (not display names); include required fields like name and slug for create.
- Ensure item_id is a 24-character hexadecimal MongoDB ObjectId when updating or deleting items.
- CMS items are staged by default; publish with PUBLISH_SITE or set live: true to push to production.
- Slug values must be lowercase alphanumeric with hyphens (^[a-z0-9]+(?:-[a-z0-9]+)*$).
Example Use Cases
- Create a new blog post in the Blog Posts collection with name 'New Launch' and slug 'new-launch'.
- Update a product item’s price and stock using its item_id in the Products collection.
- Publish changes after updating the homepage hero section to live.
- Upload a product image asset to Webflow assets for a product page.
- Fetch the latest ecommerce orders to process shipments.
Frequently Asked Questions
Related Skills
supabase-automation
davepoon/buildwithclaude
Automate Supabase database queries, table management, project administration, storage, edge functions, and SQL execution via Rube MCP (Composio). Always search tools first for current schemas.
mcp-builder
davepoon/buildwithclaude
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
skill-creator
davepoon/buildwithclaude
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
webapp-testing
davepoon/buildwithclaude
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.