webflow-automation

First list sites and collections to get the collection_id, then call GET_COLLECTION to learn the field slugs. Create the item with field_data containing at least name and slug, using field slugs rather than display names.

Call WEBFLOW_PUBLISH_SITE with the site_id and either custom domain IDs or publish_to_webflow_subdomain set to true. Publishing deploys all staged changes and is rate limited to one publish per minute.

Webflow CMS operations require field slugs, not display names. A field labeled "Author Name" may have the slug "author-name". Always call GET_COLLECTION first to retrieve the schema and confirm the correct slugs.

All Webflow IDs are 24-character hexadecimal MongoDB ObjectIds matching the pattern ^[0-9a-fA-F]{24}$. Invalid IDs return 404 errors, so resolve IDs by listing sites, collections, items, or pages first.

No, the Webflow order endpoints are read-only. You can list orders with optional status filters and retrieve individual order details, but creating, updating, or deleting orders is not supported.

The file_content parameter must be actual base64-encoded binary data, not a URL or placeholder, and the md5 hash must be computed from the raw file bytes. Large files may also time out during the S3 upload step.