List Collections: 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
Site ID site_id	string	Required	Site ID. Example: 62a...abc

Sample request

{
  "site_id": "e.g. 62a...abc"
}

Returns

{
  "collections": [
    {
      "id": "63a...abc",
      "slug": "blog-posts",
      "displayName": "Blog Posts",
      "singularName": "Blog Post"
    }
  ]
}

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

FAQ

Questions about List Collections.

What does the List Collections action do in Webflow?

Lists all CMS collections for a Webflow site with their field schema. Use as the first step in any flow that picks a collection.

What inputs does List Collections require?

Required: Site 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 Collections support batch operations?

Yes. Run List Collections 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