Integrations
Set up Weaviate Credentials credentials in Duaer
Store Weaviate Credentials 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 Weaviate
The Duaer Weaviate Credentials start with Connection Type:
- Weaviate Cloud: open your cluster in the Weaviate Cloud console, copy the REST Endpoint into Weaviate Cloud Endpoint, and create an API key for Weaviate Api Key. Use an Admin key to write data; Read Only is enough for search.
- Custom Connection: for a self-hosted Weaviate, fill in the HTTP and gRPC hosts and ports, 8080 and 50051 by default. Both hosts default to weaviate, the service name common in Docker Compose. Turn on the matching Secure option for HTTPS.
The Weaviate Vector Store node uses both HTTP and gRPC, so the Duaer server must reach both ports.
Weaviate Credentials fields in Duaer
In Duaer, choose Weaviate Credentials when you create a credential, then fill in these fields:
- Connection Type: Choose whether to connect to a Weaviate Cloud instance or a custom Weaviate instance. Default: Weaviate Cloud. Options: Weaviate Cloud, Custom Connection.
- Weaviate Cloud Endpoint (required): The Endpoint of a Weaviate Cloud instance. Shown when Connection Type is Weaviate Cloud.
- Weaviate Api Key (secret): The API key for the Weaviate instance.
- Custom Connection HTTP Host (required): The host of your Weaviate instance. Default: weaviate. Shown when Connection Type is Custom Connection.
- Custom Connection HTTP Port (required): The port of your Weaviate instance. Default: 8080. Shown when Connection Type is Custom Connection.
- Custom Connection HTTP Secure (required): Whether to use a secure connection for HTTP. Default: off. Shown when Connection Type is Custom Connection.
- Custom Connection gRPC Host (required): The gRPC host of your Weaviate instance. Default: weaviate. Shown when Connection Type is Custom Connection.
- Custom Connection gRPC Port (required): The gRPC port of your Weaviate instance. Default: 50051. Shown when Connection Type is Custom Connection.
- Custom Connection gRPC Secure (required): Whether to use a secure connection for gRPC. Default: off. Shown when Connection Type is Custom Connection.
When you save, Duaer tests the connection with these values.
Duaer nodes that use it: Weaviate Vector Store.
Save the connection in Duaer
Open Credentials and create Weaviate Credentials. 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 Weaviate Credentials secret values appear in Duaer node parameters?
No. In Duaer, Weaviate Credentials secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a Weaviate Credentials 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 Weaviate Credentials expects, then confirm you can create credentials in that project.
In this section
Built-in integrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Triggers start a workflow. Actions run a step after it has started.
IntegrationsRisks of community nodes in Duaer
Before you install a community node in Duaer, know the code comes from a source the instance admin trusts, and know what permissions it gets.
IntegrationsTroubleshoot community nodes in Duaer
When a Duaer community node will not install or run, check the version, permissions, and node docs, then the instance logs.
IntegrationsMake custom API calls for an app in Duaer
When a Duaer app node does not expose the API you need, use HTTP Request and reuse that app’s saved authentication.
IntegrationsIntegrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Community nodes are extra packages. Custom operations reuse saved authentication with HTTP Request.
CredentialsBuilt-in credentials in Duaer
Per-service credential notes for Duaer built-ins. The create flow is in the credentials overview; node docs link to the matching service page.
Create nodesCreate a custom node for Duaer
Write a node package for Duaer when built-in nodes and custom operations are not enough and you will reuse the step.