How-to guides

Connect HaloPSA

Create an API Application in HaloPSA, then paste four fields into DarkBird.


DarkBird connects to HaloPSA using OAuth 2.0 Client Credentials (no user login required). You will create a dedicated API Application inside HaloPSA, then paste its credentials into Settings → Integrations → HaloPSA.

Step 1 — Create an API Application

  1. Configuration → Integrations → HaloPSA API

    Click View Applications, then New.

  2. Name and authentication

    Set the Name to DarkBird and Authentication Method to Client Credentials.

  3. Set permissions

    Check the permissions listed in the table below.

  4. Save and copy credentials

    HaloPSA will display a Client ID and Client Secret. Copy both immediately — the secret is shown only once.

Step 2 — Required API permissions

PermissionReadEditNotes
ClientsYesNoRequired to search customers when linking a project
ProjectsYesYesRequired to link DarkBird projects and push the WBS
TicketsYesYesRequired to create phase and task tickets under a project
Time EntriesYesNoRequired to pull actuals back into DarkBird after project completion
Items (Products)YesNoRequired to sync the Halo product catalog into DarkBird
SitesYesNoRequired to populate site data when linking a project
QuotationsYesYesRequired to create opportunities and push BOM line items

Step 3 — Enter credentials in DarkBird

Go to Settings → Integrations → HaloPSA and click Connect. Fill in all four fields:

FieldWhere to find it
Client IDShown on the API Application page in HaloPSA after saving
Client SecretShown once when the application is first created — copy before closing
Tenant NameThe subdomain of your HaloPSA URL, e.g. yourcompany from yourcompany.halopsa.com
API URLYour full HaloPSA domain, e.g. https://yourcompany.halopsa.com
Tip

On first connect, DarkBird automatically imports your HaloPSA product/item catalog. This may take a moment for large catalogs.

What DarkBird does in HaloPSA

  • Create Opportunity — Click the link icon in the project header → Create Opportunity. DarkBird creates a new HaloPSA quotation pre-filled with the project name, client, all BOM line items, and a total labor hours summary. Products synced from HaloPSA are matched by catalog ID; manually-entered products appear as description-only lines.
  • Link to an Existing Record — Click the link icon → Link Existing to search for and attach an existing HaloPSA project. The client name and site data are pulled in automatically.
  • Sync Plan to HaloPSA — On the Deliver tab, push the WBS to the linked project. Each DarkBird phase becomes a parent ticket; each task becomes a child ticket with budget hours.
  • Pull Actuals from HaloPSA — On the Deliver tab, pull time entries logged against the project. Hours are matched to DarkBird tasks by name and populate the Actuals column for calibration.
  • Product Catalog Sync — Automatically runs on first connect and can be re-run from Settings → Integrations → HaloPSA → Sync Products.
Tip

DarkBird never deletes records in HaloPSA. Sync operations only create or read.