본문으로 건너뛰기
cccskills
무료GitHub에 공개

webflow-automation

Automate Webflow CMS collections, site publishing, page management, asset uploads, and ecommerce orders via Rube MCP (Composio). Always search tools first for current schemas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

연동 도구MongoDB
설치 방법 보기

포함된 파일(1)

  • SKILL.md11.1 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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.

Toolkit docs: composio.dev/toolkits/webflow

Prerequisites

  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Webflow connection via RUBE_MANAGE_CONNECTIONS with toolkit webflow
  • Always call RUBE_SEARCH_TOOLS first 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.

  1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  2. Call RUBE_MANAGE_CONNECTIONS with toolkit webflow
  3. If connection is not ACTIVE, follow the returned auth link to complete Webflow OAuth
  4. 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:

  1. WEBFLOW_LIST_WEBFLOW_SITES - List sites to find the target site_id [Prerequisite]
  2. WEBFLOW_LIST_COLLECTIONS - List all collections for the site [Prerequisite]
  3. WEBFLOW_GET_COLLECTION - Get collection schema to find valid field slugs [Prerequisite for create/update]
  4. WEBFLOW_LIST_COLLECTION_ITEMS - List existing items with filtering and pagination [Optional]
  5. WEBFLOW_GET_COLLECTION_ITEM - Get a specific item's full details [Optional]
  6. WEBFLOW_CREATE_COLLECTION_ITEM - Create a new item with field data [Required for creation]
  7. WEBFLOW_UPDATE_COLLECTION_ITEM - Update an existing item's fields [Required for updates]
  8. WEBFLOW_DELETE_COLLECTION_ITEM - Permanently remove an item [Optional]
  9. WEBFLOW_PUBLISH_SITE - Publish changes to make them live [Optional]

Key parameters for CREATE_COLLECTION_ITEM:

  • collection_id: 24-character hex string from LIST_COLLECTIONS
  • field_data: Object with field slug keys (NOT display names); must include name and slug
  • field_data.name: Display name for the item
  • field_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 identifier
  • item_id: 24-character hex MongoDB ObjectId of the existing item
  • fields: Object with field slug keys and new values
  • live: 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 slug from the collection schema, NOT display names
  • Always call GET_COLLECTION first to retrieve the schema and identify correct field slugs
  • CREATE_COLLECTION_ITEM requires name and slug in field_data
  • UPDATE_COLLECTION_ITEM cannot create new items; it requires a valid existing item_id
  • item_id must 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_SITE or set live: true to 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:

  1. WEBFLOW_LIST_WEBFLOW_SITES - List all accessible sites [Required]
  2. WEBFLOW_GET_SITE_INFO - Get detailed site metadata including domains and settings [Optional]
  3. 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_SITES
  • custom_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_domains or publish_to_webflow_subdomain must be specified

Pitfalls:

  • PUBLISH_SITE republishes 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_domains expects 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:

  1. WEBFLOW_LIST_WEBFLOW_SITES - Find the target site_id [Prerequisite]
  2. WEBFLOW_LIST_PAGES - List all pages for a site with pagination [Required]
  3. WEBFLOW_GET_PAGE - Get detailed metadata for a specific page [Optional]
  4. 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 identifier
  • locale_id: Optional locale filter for multi-language sites
  • limit: Max results per page (max 100)
  • offset: Pagination offset

Pitfalls:

  • LIST_PAGES paginates 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_DOM returns 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:

  1. WEBFLOW_LIST_WEBFLOW_SITES - Find the target site_id [Prerequisite]
  2. WEBFLOW_UPLOAD_ASSET - Upload a file with base64-encoded content [Required]

Key parameters:

  • site_id: Site identifier
  • file_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_content must be actual base64-encoded data, NOT a variable reference or placeholder
  • md5 must 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:

  1. WEBFLOW_LIST_WEBFLOW_SITES - Find the site with ecommerce enabled [Prerequisite]
  2. WEBFLOW_LIST_ORDERS - List all orders with optional status filtering [Required]
  3. 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 retrieval
  • status: 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, capture id
  • Collection ID: WEBFLOW_LIST_COLLECTIONS with site_id
  • Item ID: WEBFLOW_LIST_COLLECTION_ITEMS with collection_id
  • Page ID: WEBFLOW_LIST_PAGES with site_id
  • Domain IDs: WEBFLOW_GET_SITE_INFO -- found in customDomains array
  • Field slugs: WEBFLOW_GET_COLLECTION -- found in collection fields array

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:

  1. Get site_id from LIST_WEBFLOW_SITES
  2. Get collection_id from LIST_COLLECTIONS
  3. Get field schema from GET_COLLECTION (to learn field slugs)
  4. Create/update items using correct field slugs
  5. 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 slug values, NOT display names
  • A field with displayName "Author Name" might have slug author-name
  • Always call GET_COLLECTION to discover correct field slugs
  • Using wrong field names silently ignores the data or causes validation errors

Publishing

  • PUBLISH_SITE deploys 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_ITEM permanently removes CMS items
  • PUBLISH_SITE makes all staged changes live immediately
  • Always confirm with the user before executing these actions

Quick Reference

TaskTool SlugKey Params
List sitesWEBFLOW_LIST_WEBFLOW_SITES(none)
Get site infoWEBFLOW_GET_SITE_INFOsite_id
Publish siteWEBFLOW_PUBLISH_SITEsite_id, custom_domains or publish_to_webflow_subdomain
List collectionsWEBFLOW_LIST_COLLECTIONSsite_id
Get collection schemaWEBFLOW_GET_COLLECTIONcollection_id
List collection itemsWEBFLOW_LIST_COLLECTION_ITEMScollection_id, limit, offset
Get collection itemWEBFLOW_GET_COLLECTION_ITEMcollection_id, item_id
Create collection itemWEBFLOW_CREATE_COLLECTION_ITEMcollection_id, field_data
Update collection itemWEBFLOW_UPDATE_COLLECTION_ITEMcollection_id, item_id, fields
Delete collection itemWEBFLOW_DELETE_COLLECTION_ITEMcollection_id, item_id
List pagesWEBFLOW_LIST_PAGESsite_id, limit, offset
Get pageWEBFLOW_GET_PAGEpage_id
Get page DOMWEBFLOW_GET_PAGE_DOMpage_id
Upload assetWEBFLOW_UPLOAD_ASSETsite_id, file_name, file_content, content_type, md5
List ordersWEBFLOW_LIST_ORDERSsite_id, status
Get orderWEBFLOW_GET_ORDERsite_id, order_id

Powered by Composio

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Automate ActiveCampaign tasks via Rube MCP (Composio): manage contacts, tags, list subscriptions, automation enrollment, and tasks. Always search tools first for current schemas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

davepoon/buildwithclaude3.7천2026년 10월 19일 업데이트

Pull the ads a competitor is running right now on Meta (Facebook/Instagram) and Google, then extract the hooks, offers, CTAs and landing pages worth modelling. Use when writing ad copy, planning creative tests, choosing a landing page angle, or when the user asks "what is X advertising", "what ads does X run", "find competitor ad hooks". Reads live Ad Library and Ads Transparency data through the Tracetify MCP; falls back to a manual Ad Library walkthrough when the connector is absent.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

davepoon/buildwithclaude3.7천2026년 10월 19일 업데이트

Analytics your AI agent can actually use. Track, analyze, run A/B experiments, and optimize across all your projects via CLI. Includes a growth playbook so your agent knows HOW to grow, not just what to track.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

davepoon/buildwithclaude3.7천2026년 10월 19일 업데이트

Teaches when to recall from long-term memory before acting and when to save durable decisions, corrections and failures afterwards. Use when a memory tool or MCP memory server is connected but the agent is not using it consistently, when the user complains that the assistant forgets preferences, conventions or past decisions between sessions, or when setting up persistent memory for a project. Works with any memory backend: a folder of Markdown files, a local MCP server, or a managed service.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

davepoon/buildwithclaude3.7천2026년 10월 19일 업데이트

Audit local AI coding-agent sessions with agenttrace for cost, tokens, tool failures, latency, anomalies, health, diffs, and CI gates.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

davepoon/buildwithclaude3.7천2026년 10월 19일 업데이트

Checks which private files (.env, keys, secrets) Claude Code and its subagents reached in this project, whether a value came into an agent's context, and which key to change, by running the open source agentwhy CLI over the session records Claude Code already keeps on disk. Use when the user asks whether the agent or a subagent read their .env or other secrets, which private files a session touched, whether a key leaked into the conversation, or which key to rotate. Runs locally and never prints a secret value.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

davepoon/buildwithclaude3.7천2026년 10월 19일 업데이트

davepoon의 스킬 모두 보기

이 스킬의 문제 신고