Help
Connect your PSA
ConfigCheckup raises one ticket per failing control in HaloPSA, ConnectWise Manage or Autotask, with the fix steps in it, and closes the ticket with a note once a later assessment shows the control passing.
How tickets work
- One PSA connection per workspace. Setting it up needs the Admin or Owner role in ConfigCheckup.
- Credentials are tested with your PSA before they are saved, and secrets are stored encrypted.
- After each completed assessment, every failing control at or above the severity you choose gets a ticket, unless it already has an open one. Nothing is raised twice.
- When a later assessment shows the control passing, ConfigCheckup adds a note saying so and closes the ticket.
- Only tenants mapped to a company in your PSA get tickets, so you can start with one client.
Start in ConfigCheckup at Settings → Integrations, choose your PSA, then follow the steps for it below.
HaloPSA
Create the API application
- In HaloPSA, go to Configuration → Integrations → HaloPSA API and select View Applications, then New.
- Name it “ConfigCheckup” and set the authentication method to Client ID and Secret (Services).
- Choose an agent for it to act as; tickets and notes are recorded against that agent.
- On the permissions tab, allow it to read customers and to read and edit tickets. Save, then copy the client ID and secret.
Fill in the form
| Field | What to enter |
|---|---|
| Resource server URL | Your Halo address, e.g. https://yourcompany.halopsa.com. HaloPSA shows it on the API page. |
| Authorisation server URL | Usually the same address with /auth on the end. |
| Client ID, client secret | From the application you just created. |
| Ticket type ID (optional) | The ticket type to raise, if not your default. |
| Closed status ID (optional) | The status used when a control passes again. Defaults to 9, Halo's standard “Closed”. |
The company for each tenant is the customer's client ID in Halo, shown in the address bar when you open the customer.
ConnectWise Manage
Create an API member and keys
- In ConnectWise Manage, go to System → Members → API Members and add a member for ConfigCheckup. Give it a security role that can view companies and add and edit service tickets.
- Open the member, go to the API Keys tab and create a key. Copy the public and private key; the private key is shown only once.
- ConnectWise also requires a client ID for each integration. Create one at developer.connectwise.com under Client IDs.
Fill in the form
| Field | What to enter |
|---|---|
| API URL | Your region's API address, e.g. https://api-eu.myconnectwise.net/v4_6_release/apis/3.0 (api-na, api-au and so on for other regions). |
| Company ID | The company name you type when signing in to ConnectWise. |
| Public key, private key | From the API member. |
| Client ID | From developer.connectwise.com. |
| Service board ID | The board tickets go on. Open the board under System → Setup Tables → Service Board; the ID is in the address. |
| Closed status ID | A closed status on that board, used when a control passes again. |
The company for each tenant is the company's record ID in ConnectWise (the number in the address when you open it).
Autotask
Create an API user
- In Autotask, go to Admin → Account Settings & Users → Resources/Users and add an API user.
- Give it the API User security level, or one that can view companies and create and edit tickets.
- Generate the user name and secret, and under API Tracking Identifier choose a custom (internal integration) identifier. Copy all three.
Fill in the form
| Field | What to enter |
|---|---|
| API zone URL | Your zone's REST address, e.g. https://webservices16.autotask.net/atservicesrest/v1.0. Autotask's zoneInformation endpoint returns the right one for your API user name. |
| API user name, API user secret | From the API user. |
| API tracking identifier | The identifier chosen for the API user. |
| Queue ID (optional) | The queue tickets go to. |
| Complete status value (optional) | Used when a control passes again. Defaults to 5, Autotask's standard “Complete”. |
The company for each tenant is the company's ID in Autotask.
Map tenants to companies
- Choose the lowest severity to raise tickets for. High is a sensible start: critical and high findings only.
- Save the connection. ConfigCheckup tests the credentials and tells you if anything is wrong.
- Open each tenant in ConfigCheckup and enter its Company ID in your PSA under PSA company. Leave it blank for tenants that should not get tickets.
- Run an assessment, or wait for the next scheduled one. Tickets appear once it completes.
Troubleshooting
- Saving fails: the message comes from your PSA. Check the URL is for the right region or zone, and that the API user is active.
- No tickets after an assessment: check the tenant has a PSA company set, the connection is enabled, and there are failing controls at or above your severity.
- Tickets are not closing: check the closed status ID belongs to the board or ticket type being used.
Prefer your own integration? The API and webhooks on Growth and Scale give you the same findings to route however you like.