Integrations
Set up HaloPSA credentials in Duaer
Store HaloPSA 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.
Create a HaloPSA API application
The Duaer HaloPSA API credential uses client credentials:
- In HaloPSA, open Configuration > Integrations > HaloPSA API > View Applications, create an application with Client ID and Secret (Services) authentication, and grant admin, edit:tickets, and edit:customers.
- Put Client ID and Client Secret in the credential. Resource Server is the Halo web address plus /api, such as https://halo.example.com/api.
- For Halo’s hosted service, pick Hosted Solution Of Halo and fill in Tenant; for your own server, pick On-Premise Solution.
HaloPSA API fields in Duaer
In Duaer, choose HaloPSA API when you create a credential, then fill in these fields:
- Hosting Type: Default: On-Premise Solution. Options: On-Premise Solution, Hosted Solution Of Halo.
- HaloPSA Authorisation Server URL (required)
- Resource Server (required): The Resource server is available at your "Halo Web Application URL/api".
- Client ID (required): Must be your application client ID.
- Client Secret (required, secret): Must be your application client secret.
- Tenant: An additional tenant parameter for HaloPSA hosted solution. Shown when Hosting Type is Hosted Solution Of Halo.
Duaer nodes that use it: HaloPSA.
Save the connection in Duaer
Open Credentials and create HaloPSA. 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 HaloPSA secret values appear in Duaer node parameters?
No. In Duaer, HaloPSA secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a HaloPSA 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 HaloPSA 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.