BusyBot
Search all guides

Reference · Credentials

Connect HaloPSA to BusyBot

Used by 1 BusyBot node.

Type haloPsaApi 7 fields

Fields

FieldTypeRequiredNotes
Hosting Type
hostingType		 options Yes Whether you use HaloPSA cloud or self-hosted.
Auth Server URL
authUrl		 string Yes Authorization server URL (e.g., https://yourtenant.halopsa.com).
Resource API URL
resourceApiUrl		 string Yes API base URL (e.g., https://yourtenant.halopsa.com/api).
Client ID
client_id		 string Yes —
Client Secret
client_secret		 password Yes —
Tenant
tenant		 string No Tenant ID (required for hosted deployments).
Scope
scope		 string No OAuth2 scopes.

Setting up HaloPSA API

  1. In HaloPSA API, create the credential this connection needs — the values listed in the table above. These are issued from your own HaloPSA API account, usually under its developer, API or integrations settings.
  2. In BusyBot, open Credentials → Add credential and choose HaloPSA API.
  3. Paste each value into the matching field and save.
  4. Add the HaloPSA node to a workflow, select this credential, and run a simple operation to confirm it authenticates.

Security

  • Secret values are encrypted at rest with AES-256-GCM, never written to logs, and readable only by your own account (to edit them).
  • Grant the minimum scopes or permissions the operations you actually use require.
  • Rotate the credential periodically, and immediately if it may have been exposed.
  • Credentials are scoped to your account — a workflow cannot use another account's.

Frequently asked questions

Which BusyBot nodes use HaloPSA credentials?

One node: HaloPSA. Create the credential once and select it in that node.

What does a HaloPSA credential need?

7 fields: Hosting Type, Auth Server URL, Resource API URL, Client ID, Client Secret, Tenant, Scope. Required: Hosting Type, Auth Server URL, Resource API URL, Client ID, Client Secret. The values come from your own HaloPSA account.

How are HaloPSA secrets stored?

Secret values are encrypted at rest with AES-256-GCM, never written to logs, and scoped to your account: only you can open the credential again to edit it, and a workflow in another account cannot use it.

Nodes that use HaloPSA API

One credential works across every node below — create it once and reuse it.