Duaer

Integrations

Set up Uptime Robot credentials in Duaer

Store Uptime Robot 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 UptimeRobot API key

The Duaer Uptime Robot API credential needs one key:

  1. In UptimeRobot, open Integrations & API > API and create the Main API Key. A read-only key cannot create or change monitors.
  2. Put it in API Key and save.

Uptime Robot API fields in Duaer

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

  • API Key (secret)

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

Duaer nodes that use it: UptimeRobot.

Save the connection in Duaer

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

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

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

In this section