Duaer

Integrations

Set up NocoDB credentials in Duaer

Store NocoDB 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.

Create a NocoDB API token

For the Duaer NocoDB node, prefer the NocoDB API Token credential:

  1. In NocoDB, open Account settings > Tokens (Team & Settings > API Tokens in the cloud), click Create new token, and copy it.
  2. Put it in API Token. Host is https://app.nocodb.com, or your address when self-hosted, such as https://nocodb.example.com.

The NocoDB credential takes a session User Token (xc-auth) that expires with the sign-in, so it only suits old versions.

NocoDB

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

  • User Token (secret)
  • Host

Duaer nodes that use it: NocoDB.

NocoDB API Token

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

  • API Token (required, secret)
  • Host (required)

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

Duaer nodes that use it: NocoDB.

Save the connection in Duaer

Open Credentials and create NocoDB. 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 NocoDB secret values appear in Duaer node parameters?

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

What usually stops a NocoDB 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 NocoDB expects, then confirm you can create credentials in that project.

In this section