Duaer

Integrations

Set up OpenWeatherMap credentials in Duaer

Store OpenWeatherMap 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 OpenWeatherMap API key

The Duaer OpenWeatherMap API credential needs one key:

  1. Sign in to OpenWeatherMap and copy or create a key on the API keys tab.
  2. Put it in Access Token and save.

A new key can take up to about two hours to activate; until then calls return 401.

OpenWeatherMap API fields in Duaer

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

  • Access Token (secret)

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

Duaer nodes that use it: OpenWeatherMap.

Save the connection in Duaer

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

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

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

In this section