For insert, supply documentsSource and vectorsSource, with one equal-dimension vector per document. For query, supply queryVectorSource; for delete, supply a nonempty idsSource list. Results are in matches. The simple store stays in execution data and storeSource reuses its output; external storage retains an index across runs.
Technical type : ai_qdrant_vector_store. Runtime : nodulz.
Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.
Parameters
Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.
Parameter
Type
Default
Values / limits
operation
enum
"insert"
insert, query, delete
credentialId
string
-
-
serviceInstanceId
string
-
-
connectionSource
enum
"credential"
credential, service
indexName
string
""
-
namespace
string
""
-
documentsSource
string
""
-
vectorsSource
string
""
-
query
string
""
-
queryVectorSource
string
""
-
idsSource
string
""
-
topK
number
4
-; ≥ 1, ≤ 1000
storeSource
string
""
-
Configuration help
connectionSource Connection source
Use a manual credential or a service deployed in the Services space.
serviceInstanceId Service instance
Only Available services matching the app binding are listed.
credentialId Vector credential
Qdrant connection settings are stored on the Credentials page. This vector store uses a compatible HTTP gateway. A native Redis or PostgreSQL connection cannot be used by this node.
operation Operation
Insert, query, or delete vectors in the remote index.
indexName Index / collection
Remote index or Qdrant collection name. Falls back to the credential default.
namespace Namespace
Optional namespace or partition supported by the provider.
topK Top K
Maximum number of matches to return.
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.
Qdrant vector database
Usage and specifics
For insert, supply documentsSource and vectorsSource, with one equal-dimension vector per document. For query, supply queryVectorSource; for delete, supply a nonempty idsSource list. Results are in matches. The simple store stays in execution data and storeSource reuses its output; external storage retains an index across runs.
Technical type :
ai_qdrant_vector_store. Runtime :nodulz.Credentials and prerequisites
Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.
Parameters
Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.
operationenum"insert"insert,query,deletecredentialIdstringserviceInstanceIdstringconnectionSourceenum"credential"credential,serviceindexNamestring""namespacestring""documentsSourcestring""vectorsSourcestring""querystring""queryVectorSourcestring""idsSourcestring""topKnumber4storeSourcestring""Configuration help
connectionSourceConnection source
serviceInstanceIdService instance
credentialIdVector credential
operationOperation
indexNameIndex / collection
namespaceNamespace
topKTop K
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
{ "operation": "insert", "connectionSource": "credential", "indexName": "", "namespace": "", "documentsSource": "", "vectorsSource": "", "query": "", "queryVectorSource": "", "idsSource": "", "topK": 4, "storeSource": "" }Verification
Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.
See also : Expressions and data, Executions, Node catalog.