Chroma integration
Vector database
Chroma is an open-source vector database for storing embeddings and running semantic search over them. The NoClick Chroma node talks to the Chroma API, so a single workflow can create databases, tenants, and collections, add records with their embeddings, read and count records, and delete records or whole collections when they go stale. It can also fork a collection, attach and detach embedding functions, and look up a collection by ID or CRN. Drop it onto the canvas to keep a vector store in sync with your data instead of managing it by hand.
What you can automate with Chroma
Chroma operations
Records9
Collection11
Functions4
Tenant3
Database4
Utility5
Questions
Yes. The Chroma node adds records with their embeddings, reads them back, counts them, and deletes records or entire collections. Wire these to any trigger so new data flows in and stale data is removed without manual steps.
Add the Chroma node and open its credentials tab to enter your Chroma connection details. Once connected, every operation, from creating a database to forking a collection, runs against your instance.
The node is request and response, so it does not fire on its own when Chroma changes. You drive it from other triggers, a schedule, a form submission, or an inbound event, then have it create collections, add records, or read counts as part of the run.
Yes. Beyond records, the node creates databases, tenants, and collections, counts and deletes collections, forks a collection, and looks one up by ID or CRN. That lets a workflow stand up and tear down vector stores as your projects come and go.
Chroma lets you attach embedding functions to a collection, and the node exposes that. It can attach and detach a function, add a function input, and read which function is currently attached, so records get embedded the way you intend.
