Collections | Webflow Developer Documentation

Collections are the foundation of Webflow’s CMS, defining the structure for your content types like blog posts, authors, or team members.

When to use

Use Collections tools to:

Create new collections: Set up content structures for blogs, portfolios, authors, etc.
List existing collections: See all collections in a site
Get collection schemas: View field definitions and configuration
Plan content architecture: Understand collection relationships

Tool details

Tool name: data_cms_tool

Available actions

Get collection list

Retrieve all CMS collections in a site with metadata.

Action: get_collection_list

Parameters:

Parameter	Type	Required	Description
`siteId`	string	Yes	Unique identifier for the site

Returns: Array of collections with:

Collection ID
Collection name
Slug
Item count
Last modified date

Example usage:

List all collections for site [site_id]

Get collection details

Fetch detailed schema and field definitions for a specific collection.

Action: get_collection_details

Parameters:

Parameter	Type	Required	Description
`collection_id`	string	Yes	Unique identifier for the collection

Returns: Complete collection schema including:

All field definitions
Field types and validation rules
Required vs. optional fields
Reference field relationships

Example usage:

Show me the complete schema for collection [collection_id]

Use this to understand a collection’s structure before creating or updating items.

Create collection

Establish a new CMS collection.

Action: create_collection

Parameters:

Parameter	Type	Required	Description
`siteId`	string	Yes	Unique identifier for the site
`request`	object	Yes	Collection configuration (name and schema)

Request object:

1 {
2   "displayName": "Blog Posts",
3   "singularName": "Blog Post",
4   "slug": "blog-posts"
5 }

Returns: Created collection with ID and configuration

Example usage:

Create a new collection called "Blog Posts" for site [site_id]

After creating a collection, use Fields tools to add custom fields to it.

Best practices

Choose meaningful names

Display name: Human-readable, plural

✅ “Blog Posts”, “Team Members”, “Authors”
❌ “Items”, “Data”, “Things”

Singular name: Used in UI and URLs

✅ “Blog Post”, “Team Member”, “Product”
❌ “Post1”, “Member_”, “prod”

Slug: URL-friendly, lowercase with hyphens

✅ “blog-posts”, “team-members”, “authors”
❌ “BlogPosts”, “team members”, “authors_1”

Plan fields before creation

Before creating a collection, plan:

What content will it store?
What fields are required?
What fields are optional?
How does it relate to other collections?

Create a spreadsheet or document outlining your schema.

Consider future needs

Think ahead when designing collections:

Will you need localization?
Will items be filtered or sorted?
Will you need reference relationships?
What’s the expected item count?

It’s easier to add fields later than to restructure collections.

Use consistent naming conventions

Establish naming patterns across collections:

Field names: camelCase or snake_case
Collection slugs: lowercase-with-hyphens
Display names: Title Case with spaces

Consistency makes your CMS easier to work with.

Limitations

Plan limits: Number of collections varies by Webflow plan
Name changes: Collection names can be updated, but slugs should remain stable
Deletion: Deleting a collection deletes all items in it (use caution)
Structure changes: Major structural changes may require migration

Deleting a collection is permanent and removes all items. Export data before deletion if you might need it later.