Skip to main content
Core creates a ticket in your PSA for each workflow run and maps each client to its PSA company. You need admin access to your PSA to create an API account for Triggr.

Connect your PSA, with Halo PSA as the example: connection details, the test and mapping clients (1:18).

​
Set up the connection

1

Choose your PSA

On Home, click Set up next to Connect your PSA, pick yours and click Continue. For Syncro or Something else, click Done and talk to your account manager.
The Choose your PSA step with ConnectWise PSA, Halo PSA (selected) and Autotask cards, and Syncro and Something else under Using something else?, with the wizard's four steps on the left.
2

Enter the connection details

Create the API account in your PSA, paste its details and click Save and test.
Follow Set up ConnectWise PSA, including the security role permissions. Company ID is the one you sign in with; API member identifier is the API member’s Member ID.
The Connect ConnectWise PSA step with three setup pointers and a Setup guide link, empty Hostname, Company ID, Public key, Private key and API member identifier fields with hints under each, and Back and Save and test buttons.
3

Check the test

When Core shows Connected, click Continue. If it shows an error, fix the fields and click Save and test again, or click Skip for now and come back from Home later.
The Connect Halo PSA step with Base URL, Client ID, Client secret and an optional Tenant ID field, above a green Connected. Found 8 ticket types. message with a Test again button.
4

Map clients

Click Apply 100% matches, then pick the company under Mapped to for anyone left; each change saves at once. With no clients yet, map them later from Integrations.
The Map clients step with Apply 100% matches (1) and Refresh buttons, a Search clients box, All, Mapped and Unmapped filters, and a table of Triggr clients with a Mapped to picker and a Suggested mapping column showing percentage matches with Apply buttons, above Back and Continue buttons.
The wizard also sets Default PSA in Settings > General, which ticket steps use.

​
Change it later

  • Map clients: Integrations > your PSA > Client mapping, or Map to your PSA in a client’s panel on Clients.
  • New credentials or a different PSA: on Home, click Review next to Connect your PSA. Switching PSA moves ticket steps to the new one at once.
If you set up the PSA from Integrations instead of the wizard, set Default PSA in Settings > General yourself; that route doesn’t run the test.

​
Troubleshooting

Re-copy the keys or secret. ConnectWise: both keys from one API key and the right Company ID. Halo: an enabled application with the all permission. Autotask: the full username and the same user’s tracking identifier.
Fix the host as described in your PSA’s tab; for Autotask, remove /atservicesrest. A self-hosted PSA must be reachable from the internet; allow Triggr’s IP addresses.
Let the API account read boards, queues or ticket types.
Set Default PSA in Settings > General, then reopen the workflow. The rest of the run still completes; only the ticket is missing.
Core creates tickets in ConnectWise PSA, Halo PSA and Autotask. Turn Ticketing off on the workflow’s Execution config, or ask your account manager about your PSA.
Next: Add your branding.