Skip to content
One platform. From customer conversation to completed work.Take a closer look
All connections
Data · CONNECTION

Chroma + NodeHub

Manage Chroma collections, add and upsert records with your own embeddings, and query nearest neighbors.

Explore 13 workflow actions for Chroma, including account permissions and operation limits.

6 read actions7 write actions
WORKFLOW ACTIONS

What you can configure.

Choose an action in the workflow builder, connect an account, and map its inputs. These actions are available in the catalog; your account access and a successful test determine whether they work for your setup.

Add records

Write

Adds records with your embeddings, and optional documents and metadata. Existing IDs are not changed.

Permissions and limits

Account permissions

  • A Chroma API key (x-chroma-token) with access to the connection's tenant and database

A repeated request may repeat the external action. Review the previous result before retrying a write.

Count records

Read

How many records a collection holds.

Permissions and limits

Account permissions

  • A Chroma API key (x-chroma-token) with access to the connection's tenant and database

Create collection

Write

Creates a collection (or returns the existing one when get_or_create is true).

Permissions and limits

Account permissions

  • A Chroma API key (x-chroma-token) with access to the connection's tenant and database

A repeated request may repeat the external action. Review the previous result before retrying a write.

Delete collection

Write

Deletes a collection and all its records.

Permissions and limits

Account permissions

  • A Chroma API key (x-chroma-token) with access to the connection's tenant and database

Operation limits

  • A deleted collection and its records cannot be restored.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Delete records

Write

Deletes records by ID or by metadata and document filters.

Permissions and limits

Account permissions

  • A Chroma API key (x-chroma-token) with access to the connection's tenant and database

Operation limits

  • Deleted records cannot be restored.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Get collection

Read

One collection's name, metadata, dimension and index configuration.

Permissions and limits

Account permissions

  • A Chroma API key (x-chroma-token) with access to the connection's tenant and database

Get key identity

Read

The user, tenant and databases the API key belongs to.

Permissions and limits

Account permissions

  • A Chroma API key (x-chroma-token) with access to the connection's tenant and database

Get records

Read

Records by ID or by metadata and document filters.

Permissions and limits

Account permissions

  • A Chroma API key (x-chroma-token) with access to the connection's tenant and database

List collections

Read

The collections in the connection's database.

Permissions and limits

Account permissions

  • A Chroma API key (x-chroma-token) with access to the connection's tenant and database

Query records

Read

The nearest records to each of your query embeddings, with distances, optionally within metadata and document filters.

Permissions and limits

Account permissions

  • A Chroma API key (x-chroma-token) with access to the connection's tenant and database

Update collection

Write

Renames a collection, replaces its metadata or changes its index settings.

Permissions and limits

Account permissions

  • A Chroma API key (x-chroma-token) with access to the connection's tenant and database

A repeated request may repeat the external action. Review the previous result before retrying a write.

Update records

Write

Changes the embeddings, documents or metadata of existing records by ID.

Permissions and limits

Account permissions

  • A Chroma API key (x-chroma-token) with access to the connection's tenant and database

A repeated request may repeat the external action. Review the previous result before retrying a write.

Upsert records

Write

Adds records, or replaces the embeddings, documents and metadata of records whose IDs exist.

Permissions and limits

Account permissions

  • A Chroma API key (x-chroma-token) with access to the connection's tenant and database

A repeated request may repeat the external action. Review the previous result before retrying a write.

SETUP

Start with a controlled test.

01Connect the intended account

Use the account and permissions required for your process. Review the connection check before configuring a workflow action.

02Review inputs and access

Select a listed operation and map its required inputs. Use test records and add a human approval before writes that need review.

03Confirm the result

Inspect step outputs and confirm the result in Chroma. A saved workflow is not a completed provider action.

Follow the workflow quickstart
EXPLORE YOUR STACK

More in Data.

Chroma integration | NodeHub