List Content Types: Contentful action

Sample request

{}

Returns

{
  "items": [
    {
      "sys": {
        "id": "blogPost"
      },
      "name": "Blog Post",
      "fields": [
        {
          "id": "title",
          "name": "Title",
          "type": "Symbol"
        }
      ]
    }
  ]
}

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

FAQ

Questions about List Content Types.

What does the List Content Types action do in Contentful?

Returns every content type in the space with field definitions. Useful for validating content shape at workflow-build time and for introspection workflows that adapt to schema changes.

What inputs does List Content Types require?

List Content Types has no required inputs. Sensible defaults are applied if you leave fields blank.

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 Contentful 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 Content Types support batch operations?

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

More actions

What content types are defined in Contentful?

Apps that pair well as the trigger for List Content Types.

Questions about List Content Types.

Other Contentful actions.

Send list content types from your workflows.