Duaer

Integrations

Set up Qdrant credentials in Duaer

Store Qdrant connection details in Duaer for digital-organization nodes to use at runtime. Secrets are protected by the instance encryption key and are not written into node parameters.

Connect to Qdrant

The Duaer Qdrant API credential needs Qdrant URL, and API Key when the server asks for one:

  • Self-hosted Qdrant: put the REST address in Qdrant URL, port 6333 by default, such as http://qdrant:6333. Leave API Key empty if no key is configured.
  • Qdrant Cloud: copy the cluster URL from the cluster page into Qdrant URL, and create a key under the cluster’s API Keys for API Key.

The collection’s vector size must match the embedding model output.

Qdrant API

In Duaer, choose Qdrant API when you create a credential, then fill in these fields:

  • API Key (secret)
  • Qdrant URL (required)

When you save, Duaer tests the connection with these values.

Duaer nodes that use it: Qdrant Vector Store.

ChatHub Qdrant Vector Store API

In Duaer, choose ChatHub Qdrant Vector Store API when you create a credential, then fill in these fields:

  • API Key (secret)
  • Qdrant URL (required)
  • Collection Name: The Qdrant collection to use. All users share this collection; access is scoped per user via a userId metadata field. The collection is created automatically if it does not exist. Default: a preset value.

Save the connection in Duaer

Open Credentials and create Qdrant. Fill in the key, OAuth, or server fields. After you save, digital-organization nodes reference this credential instead of putting the secret in a parameter.

Credential values are protected by the instance encryption key. If you change or lose that key, stored credentials cannot be decrypted. See the hosting notes on encryption keys.

Who can use this credential

Who can see or edit it follows projects and roles. Do not paste secrets into chat or variables. External vaults are covered under external secrets.

Questions

Do Qdrant secret values appear in Duaer node parameters?

No. In Duaer, Qdrant secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.

What usually stops a Qdrant credential from saving in Duaer?

Wrong fields, an OAuth callback that does not match the instance URL, or a role that cannot create credentials. Check the fields Qdrant expects, then confirm you can create credentials in that project.

In this section