Duaer

Integrations

Set up Orbit credentials in Duaer

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

Orbit has shut down

The credential dialog notes that Orbit has shut down and stopped working from July 11. The Duaer Orbit API credential and Orbit node no longer work; move workflows that rely on it to another community tool.

Orbit API fields in Duaer

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

  • API Token (secret)

Note from the dialog: Orbit has been shutdown and will no longer function from July 11th, You can read more here (https://blog.postman.com/announcing-postman-has-acquired-orbit/).

Duaer nodes that use it: Orbit.

Save the connection in Duaer

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

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

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

In this section