Duaer

Integrations

Set up Freshworks CRM credentials in Duaer

Store Freshworks CRM 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.

Freshworks CRM API fields in Duaer

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

  • API Key (secret)
  • Domain: Domain in the Freshworks CRM org URL. For example, in https://duaer.myfreshworks.com, the domain is duaer.

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

Duaer nodes that use it: Freshworks CRM.

Save the connection in Duaer

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

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

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

In this section