Duaer

Integrations

Set up Msg91 credentials in Duaer

Store Msg91 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 MSG91 API key

The Duaer Msg91 Api credential needs one key:

  1. Sign in to the MSG91 dashboard and copy the auth key from the API or Authkey page.
  2. Put it in Authentication Key and save.

Msg91 Api fields in Duaer

In Duaer, choose Msg91 Api when you create a credential, then fill in these fields:

  • Authentication Key (secret)

Duaer nodes that use it: MSG91.

Save the connection in Duaer

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

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

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

In this section