Automate Webflow CMS and Site Management

This skill automates Webflow site operations through Composio's Webflow toolkit accessed via Rube MCP (no API keys, just the https://rube.app/mcp endpoint plus OAuth). It covers five workflows: CMS collection item management (list sites/collections, get a collection's field schema to learn valid field slugs, then create/update/delete items - always requiring name and slug in field_data, with item IDs as 24-character hex MongoDB ObjectIds); site management and publishing (PUBLISH_SITE deploys ALL staged changes for the selected domain, rate-limited to one publish per minute, requiring either custom domain IDs or publish_to_webflow_subdomain: true); page inspection (listing pages with offset/limit pagination, retrieving page metadata or DOM/content-node structure, not rendered HTML); asset uploads (base64-encoded file content plus an MD5 hash computed from the raw bytes, internally a two-step S3 pre-signed-URL upload); and read-only ecommerce order retrieval for sites with ecommerce enabled.

It documents Webflow's ID conventions in depth (every ID - site, collection, item, page, domain - is a 24-character hex string, and invalid IDs return 404s) and a set of recurring pitfalls: field operations require the field's slug (e.g. author-name), not its display name (e.g. "Author Name") - using the wrong one silently drops data or triggers validation errors, so GET_COLLECTION must always be called first to discover correct slugs; CMS items are staged by default and require PUBLISH_SITE or live: true to go to production; PUBLISH_SITE and DELETE_COLLECTION_ITEM are both explicitly flagged as destructive/production-affecting actions requiring user confirmation before execution; and different operations require different OAuth scopes (sites:read, cms:read, cms:write, pages:read), so a 403 error typically signals a missing scope rather than a bad request.

Use this skill for any Webflow automation task - CMS content management, site publishing, page inspection, asset uploads, or ecommerce order retrieval - once Rube MCP is connected and the webflow toolkit shows an ACTIVE connection via RUBE_MANAGE_CONNECTIONS. Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas before invoking any Webflow tool.

It is not useful without an active Rube MCP connection and completed Webflow OAuth, and ecommerce order tools are read-only - there's no create/update/delete for orders through this toolkit, so order management itself must happen elsewhere.

Input is a Webflow action request - a CMS item to create/update, a site to publish, pages to inspect, an asset to upload, or orders to review. Output is the tool call result - a created/updated CMS item, a confirmed publish, page metadata/DOM structure, an uploaded asset reference, or order details - following the documented ID-resolution chain (site -> collection/page -> item) and field-slug conventions for each workflow.

# Setup: add Rube MCP endpoint
https://rube.app/mcp

Built on Composio's Webflow toolkit surfaced through Rube MCP tools (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS) and the full WEBFLOW_* tool family for sites, collections, pages, assets, and orders.

Developers or agents automating Webflow site management - CMS content pipelines, publishing workflows, asset uploads, or ecommerce order review - through an MCP-connected toolkit rather than direct Webflow API integration.