Integrations
Set up Microsoft SQL credentials in Duaer
Store Microsoft SQL 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 SQL Server
The Duaer Microsoft SQL credential:
- Server and Port (default 1433) must be reachable from the Duaer server. For Azure SQL, Server looks like <name>.database.windows.net, and a firewall rule must allow the Duaer server’s IP.
- User and Password are a SQL Server authentication login, so the server needs mixed-mode authentication. Fill in Domain only for a Windows domain account.
- TLS is on by default. For a self-signed server certificate, turn on Ignore SSL Issues (Insecure).
- Keep TDS Version at the default unless you connect to a very old SQL Server.
Microsoft SQL fields in Duaer
In Duaer, choose Microsoft SQL when you create a credential, then fill in these fields:
- Authentication: Default: SQL Server Authentication. Options: SQL Server Authentication, Microsoft Entra Service Principal.
- Server: Default: localhost.
- Database: Default: master.
- User: Default: sa. Shown when Authentication is SQL Server Authentication.
- Password (secret): Shown when Authentication is SQL Server Authentication.
- Tenant ID (required): Shown when Authentication is Microsoft Entra Service Principal.
- Client ID (required): Shown when Authentication is Microsoft Entra Service Principal.
- Client Secret (required, secret): Shown when Authentication is Microsoft Entra Service Principal.
- Port: Default: 1433.
- Domain: Shown when Authentication is SQL Server Authentication.
- TLS: Default: on.
- Ignore SSL Issues (Insecure): Whether to connect even if SSL certificate validation is not possible. Default: off.
- Connect Timeout: Connection timeout in ms. Default: 15000.
- Request Timeout: Request timeout in ms. Default: 15000.
- TDS Version: The version of TDS to use. If server doesn't support specified version, negotiated version is used instead. Default: 7_4 (SQL Server 2012 ~ 2019). Options: 7_4 (SQL Server 2012 ~ 2019), 7_3_B (SQL Server 2008R2), 7_3_A (SQL Server 2008), 7_2 (SQL Server 2005), 7_1 (SQL Server 2000).
Duaer nodes that use it: Microsoft SQL.
Save the connection in Duaer
Open Credentials and create Microsoft SQL. 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 Microsoft SQL secret values appear in Duaer node parameters?
No. In Duaer, Microsoft SQL secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a Microsoft SQL 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 Microsoft SQL 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.