Duaer

Integrations

Set up Dropbox credentials in Duaer

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

Choose a Dropbox credential type

The Duaer Dropbox node supports two credentials:

  • Dropbox API: create an app in the Dropbox App Console, click Generate under Settings, and put the access token in Access Token. These tokens expire within hours, so use them only to try things out.
  • Dropbox OAuth2 API: in the same app’s Settings, add the Duaer OAuth Redirect URL to Redirect URIs. Under Permissions, tick files.content.write, files.content.read, sharing.read, and account_info.read and submit. Put App key and App secret in Client ID and Client Secret, then click Connect my account. Use this type for long-running work.

Both types have APP Access Type, which must match the access you chose when creating the app: App Folder for App folder, Full Dropbox for Full Dropbox. With the wrong one, file paths do not line up.

Dropbox API

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

  • Access Token (secret)
  • APP Access Type: Default: Full Dropbox. Options: App Folder, Full Dropbox.

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

Duaer nodes that use it: Dropbox.

Dropbox OAuth2 API

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

  • Client ID (required)
  • Client Secret (required, secret)
  • APP Access Type: Default: Full Dropbox. Options: App Folder, Full Dropbox.

Duaer uses the OAuth2 Authorization Code grant for this type.

In the provider’s app settings, register the OAuth Redirect URL that the Duaer credential dialog shows (https://<your-duaer-host>/rest/oauth2-credential/callback). Then click Connect my account in Duaer and approve access.

By default, Duaer requests these scopes: files.content.write files.content.read sharing.read account_info.read.

Optional settings shared by every Duaer OAuth2 credential: Ignore SSL Issues (Insecure), Token Expired Status Code, Encrypted Tokens (JWE), JWKS URI. They are described under OAuth2 API.

Duaer nodes that use it: Dropbox.

Save the connection in Duaer

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

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

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

In this section