Duaer

Integrations

Set up Oura credentials in Duaer

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

Get a Oura API key

The Duaer Oura API credential needs one key:

  1. Sign in to Oura Cloud and create a token on the Personal Access Tokens page. If the page no longer offers one, Oura has stopped issuing personal tokens.
  2. Put it in Personal Access Token and save.

Oura API fields in Duaer

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

  • Personal Access Token (secret)

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

Duaer nodes that use it: Oura.

Save the connection in Duaer

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

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

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

In this section