Duaer

Integrations

Set up Airtop credentials in Duaer

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

The Duaer Airtop API credential needs one key:

  1. Sign in to the Airtop portal and create an API key (the credential dialog notes it is free).
  2. Put it in API Key and save.

Airtop API fields in Duaer

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

  • API Key (required, secret): The Airtop API key. You can create one at Airtop (https://portal.airtop.ai/api-keys) for free.

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

Duaer nodes that use it: Airtop.

Save the connection in Duaer

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

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

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

In this section