Duaer

Integrations

Set up Vonage credentials in Duaer

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

The Duaer Vonage API credential:

  1. Sign in to the Vonage API Dashboard; API key and API secret are on the home page.
  2. Put them in API Key and API Secret.

Vonage API fields in Duaer

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

  • API Key (secret)
  • API Secret (secret)

Duaer nodes that use it: Vonage.

Save the connection in Duaer

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

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

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

In this section