Duaer

Integrations

Set up Asana credentials in Duaer

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

Choose a Asana credential type

The Duaer Asana node supports two credentials:

  • Asana API: in the Asana developer console, click Create new token and put the personal access token in Access Token. It carries all of your account’s permissions.
  • Asana OAuth2 API: create an app in the same console, add the Duaer OAuth Redirect URL as a Redirect URL in its OAuth settings, put Client ID and Client Secret in the credential, then click Connect my account.

Asana Trigger registers a webhook in Asana, so Duaer must be reachable from the internet.

Asana API

In Duaer, choose Asana 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: Asana, Asana Trigger.

Asana OAuth2 API

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

  • Client ID (required)
  • Client Secret (required, secret)

Duaer uses the OAuth2 Authorization Code grant for this type.

In the provider’s app settings, register the OAuth Redirect URL that the Duaer credential dialog shows (https://<your-duaer-host>/rest/oauth2-credential/callback). Then click Connect my account in Duaer and approve access.

Optional settings shared by every Duaer OAuth2 credential: Ignore SSL Issues (Insecure), Token Expired Status Code, Encrypted Tokens (JWE), JWKS URI. They are described under OAuth2 API.

Duaer nodes that use it: Asana, Asana Trigger.

Save the connection in Duaer

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

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

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

In this section