Duaer

Integrations

Set up Quick Base credentials in Duaer

Store Quick Base 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 Quickbase user token

The Duaer Quick Base API credential:

  1. In Quickbase, click your avatar, open My preferences, click Manage user tokens under My User Information, create a token, and assign the apps it may access.
  2. Put it in User Token. Put your realm, such as demo.quickbase.com, in Hostname.

Quick Base API fields in Duaer

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

  • Hostname (required)
  • User Token (required, secret)

Duaer nodes that use it: Quick Base.

Save the connection in Duaer

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

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

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

In this section