List CMS Items: Webflow action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Collection ID collection_id	string	Required	Collection ID. Example: 63a...abc
Limit limit	string	Optional	Max items to return (max 100)
Offset offset	string	Optional	Offset. e.g. "0"

Sample request

{
  "collection_id": "e.g. 63a...abc",
  "limit": "100",
  "offset": "0"
}

Returns

{
  "items": [
    {
      "id": "item123",
      "fieldData": {
        "name": "Blog Post",
        "slug": "blog-post"
      }
    }
  ],
  "pagination": {
    "limit": 100,
    "total": 42,
    "offset": 0
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List CMS Items.

What does the List CMS Items action do in Webflow?

Lists items in a Webflow CMS collection with their field values. Useful for content audits, batch updates, or for piping the catalog into search.

What inputs does List CMS Items require?

Required: Collection ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Webflow returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List CMS Items support batch operations?

Yes. Run List CMS Items inside a Loop node to process arrays. Tiny Command handles Webflow's rate limits automatically so you don't have to throttle manually.

More actions