Integrations
Set up Postgres credentials in Duaer
Store Postgres 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 your Postgres database
The Duaer Postgres credential connects from the Duaer server, so fill in addresses that server can reach:
- Host: the database host name or IP. When Duaer runs in Docker, localhost means the container itself; use the database service name or the host address instead.
- Port defaults to 5432. Use the Database, User, and Password your database admin gave you, ideally a dedicated account with only the rights it needs.
- Most managed databases require encryption, so set SSL to Require. Turn on Ignore SSL Issues only for a self-signed certificate.
- When the database is reachable only through a bastion host, turn on SSH Tunnel and fill in the bastion address and sign-in method.
For refused or timed-out connections, refer to Postgres common issues.
Postgres
In Duaer, choose Postgres when you create a credential, then fill in these fields:
- Host: Default: localhost.
- Database: Default: postgres.
- User: Default: postgres.
- Password (secret)
- Maximum Number of Connections: Make sure this value times the number of workers you have is lower than the maximum number of connections your postgres instance allows. Default: 100.
- Ignore SSL Issues (Insecure): Whether to connect even if SSL certificate validation is not possible. Default: off.
- SSL: Default: Disable. Options: Allow, Disable, Require. Shown when Ignore SSL Issues (Insecure) is off.
- Port: Default: 5432.
- SSH Tunnel: Default: off.
- SSH Authenticate with: Default: Password. Options: Password, Private Key. Shown when SSH Tunnel is on.
- SSH Host: Default: localhost. Shown when SSH Tunnel is on.
- SSH Port: Default: 22. Shown when SSH Tunnel is on.
- SSH User: Default: root. Shown when SSH Tunnel is on.
- SSH Password (secret): Shown when SSH Tunnel is on.
- Private Key (secret): Shown when SSH Tunnel is on.
- Passphrase: Passphrase used to create the key, if no passphrase was used leave empty. Shown when SSH Tunnel is on.
Duaer nodes that use it: Postgres, Postgres Trigger.
ChatHub PGVector Store API
In Duaer, choose ChatHub PGVector Store API when you create a credential, then fill in these fields:
- Host: Default: localhost.
- Database: Default: postgres.
- User: Default: postgres.
- Password (secret)
- Maximum Number of Connections: Make sure this value times the number of workers you have is lower than the maximum number of connections your postgres instance allows. Default: 100.
- Ignore SSL Issues (Insecure): Whether to connect even if SSL certificate validation is not possible. Default: off.
- SSL: Default: Disable. Options: Allow, Disable, Require. Shown when Ignore SSL Issues (Insecure) is off.
- Port: Default: 5432.
- SSH Tunnel: Default: off.
- SSH Authenticate with: Default: Password. Options: Password, Private Key. Shown when SSH Tunnel is on.
- SSH Host: Default: localhost. Shown when SSH Tunnel is on.
- SSH Port: Default: 22. Shown when SSH Tunnel is on.
- SSH User: Default: root. Shown when SSH Tunnel is on.
- SSH Password (secret): Shown when SSH Tunnel is on.
- Private Key (secret): Shown when SSH Tunnel is on.
- Passphrase: Passphrase used to create the key, if no passphrase was used leave empty. Shown when SSH Tunnel is on.
- Table Name Prefix: Prefix for table names. The full table name will be {prefix}_{userId}. Default: a preset value.
Save the connection in Duaer
Open Credentials and create Postgres. 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. The matching node is under the related node.
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 Postgres secret values appear in Duaer node parameters?
No. In Duaer, Postgres secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a Postgres 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 Postgres 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.