Ask the administrator for a compatible Chroma server and a collection reachable from the backend. Set its URL and collection identifier in nodulz.
Configure in nodulz
In your instance, open Credentials, select the type above, name the credential and complete these fields:
text
apiKey, host, indexName
Save the credential, then select it on relevant nodes. URLs or parameters marked as node settings belong directly on that node.
Things to check
The code targets /api/v1/collections/{collection} and does not send the stored API key for these calls. The form still requires a key. Cloud or API v2 deployments may need an adapter; do not assume compatibility.
Verify an operation with expected permissions and data before publishing. Keep secrets out of logs and revoke them with the provider when no longer needed.
Credential type in nodulz :
vector:chroma.Create access
Ask the administrator for a compatible Chroma server and a collection reachable from the backend. Set its URL and collection identifier in nodulz.
Configure in nodulz
In your instance, open Credentials, select the type above, name the credential and complete these fields:
Save the credential, then select it on relevant nodes. URLs or parameters marked as node settings belong directly on that node.
Things to check
The code targets /api/v1/collections/{collection} and does not send the stored API key for these calls. The form still requires a key. Cloud or API v2 deployments may need an adapter; do not assume compatibility.
Verify an operation with expected permissions and data before publishing. Keep secrets out of logs and revoke them with the provider when no longer needed.
Official references
See also : Credentials and rotation, Node catalog.