
About
Automate Webflow CMS collections, site publishing, page management, asset uploads, and ecommerce orders via Rube MCP (Composio). Always search tools first for current schemas.
name: webflow-automation description: "Automate Webflow CMS collections, site publishing, page management, asset uploads, and ecommerce orders via Rube MCP (Composio). Always search tools first for current schemas." risk: critical source: community date_added: "2026-02-27"
Webflow 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.
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 sequ
