Integrations
Set up Freshdesk credentials in Duaer
Store Freshdesk 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 Freshdesk API key
This page covers two Duaer credentials, filled in the same way:
- Freshdesk API: in Freshdesk, click your avatar at the top right, open Profile settings, copy Your API Key from the right side, and put it in API Key. Domain is the subdomain only: for https://company.freshdesk.com, use company.
- Freshworks CRM API: copy the API key from Settings > API Settings in Freshworks CRM. Domain is again the subdomain only: for https://acme.myfreshworks.com, use acme.
The API key carries all of that agent’s permissions. For a workflow, use a dedicated agent account.
Freshdesk API
In Duaer, choose Freshdesk API when you create a credential, then fill in these fields:
- API Key (secret)
- Domain: If the URL you get displayed on Freshdesk is "https://company.freshdesk.com" enter "company".
When you save, Duaer tests the connection with these values.
Duaer nodes that use it: Freshdesk.
Freshworks CRM API
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 Freshdesk. 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 Freshdesk secret values appear in Duaer node parameters?
No. In Duaer, Freshdesk secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a Freshdesk 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 Freshdesk expects, then confirm you can create credentials in that project.
In this section
Built-in integrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Triggers start a workflow. Actions run a step after it has started.
IntegrationsRisks of community nodes in Duaer
Before you install a community node in Duaer, know the code comes from a source the instance admin trusts, and know what permissions it gets.
IntegrationsTroubleshoot community nodes in Duaer
When a Duaer community node will not install or run, check the version, permissions, and node docs, then the instance logs.
IntegrationsMake custom API calls for an app in Duaer
When a Duaer app node does not expose the API you need, use HTTP Request and reuse that app’s saved authentication.
IntegrationsIntegrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Community nodes are extra packages. Custom operations reuse saved authentication with HTTP Request.
CredentialsBuilt-in credentials in Duaer
Per-service credential notes for Duaer built-ins. The create flow is in the credentials overview; node docs link to the matching service page.
Create nodesCreate a custom node for Duaer
Write a node package for Duaer when built-in nodes and custom operations are not enough and you will reuse the step.