WActionWeaviateUpdated May 2026

How do I list Weaviate collections?

Short answer: Drop the "Weaviate → List Collections" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 3 Weaviate actions

Sample request

{}

Returns

{
  "classes": [
    {
      "class": "Document",
      "properties": [
        {
          "name": "content",
          "dataType": [
            "text"
          ]
        }
      ]
    }
  ]
}

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

Triggered by

Apps that pair well as the trigger for List Collections.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Weaviate

2 Google Sheets triggers

HubSpot → Weaviate

18 HubSpot triggers

FAQ

Questions about List Collections.

What does the List Collections action do in Weaviate?

Lists every collection (class) defined in this Weaviate instance along with its vectorizer and property schema. Use as the first step in any cross-collection automation.

What inputs does List Collections require?

List Collections 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 Weaviate 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 Weaviate's rate limits automatically so you don't have to throttle manually.

More actions