Short answer: Drop the "Weaviate → List Collections" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
{}
{"classes": [{"class": "Document","properties": [{"name": "content","dataType": ["text"]}]}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.