Overview
If you’re using HaloPSA, you can integrate DefensX to:
The integration process involves creating an API-only agent, generating API keys in HaloPSA, and configuring the DefensX backend.
Configurations in HaloPSA
Creating a Custom Agent
To set up the custom API agent:
Once the agent is created, click Edit in the top panel to adjust permissions:
|
Note
|
The term Supplier/Vendor and Product/Items can be shown based on your localization preferences in Halo PSA.
|
Generating API Keys
To generate the API keys for the newly created agent, follow these steps:
-
Click on View Applications under the Applications section.
-
Click New to create a new application.
-
Provide a name like "DefensX Application" and select Authentication Method as Client ID and Secret (Services). Make sure to note down the Client ID and Secret, as these will be needed for the integration.
-
Select the agent you created earlier from the list.
Configurations in DefensX Portal
Creating the Integration
-
Copy the Authorization Server from HaloPSA backend under Configuration → Integrations → HaloPSA API and paste it to as Authorization URL in DefensX Backend
-
Find the created application under Configuration → Integrations → HaloPSA API → View Applications menu and copy the Client ID and Client Secret values
-
Paste the Client ID and Client Secret values to the DefensX Backend
-
Click the Test Connection button below. You should see the "Connection successful" message.
Client Mapping
HaloPSA Clients are your customers in DefensX. You need to map the HaloPSA clients to your DefensX customers.
|
Note
|
Due to your HaloPSA settings, you can see your clients as "Customers" or "Companies" in the HaloPSA. You can modify the label of client management area.
|
Ticket Integration
|
Tip
|
If you are not interested in the Ticket Integration, you can skip the action by clicking Recurring Invoices at the top.
|
Click the toggle button at the line of Ticket Integration and select the following configuration option values:
Default Agent |
This agent will be assigned to the tickets created by DefensX. If you are not interested, please select “Unassigned”. If you can not see any agent other than "Unassigned", please check the Default Team setting of the Agent created for Integration. By the way, if you expect more Agents, you should assign more teams in Departments & Teams in the page of Custom Agent from HaloPSA. |
Default Team |
This team will be assigned to the tickets created by DefensX. The only option could be the Default Team of the Custom Agent. You create more options by assigning more teams in Departments & Teams page of Custom Agent from HaloPSA. |
Initial Status |
This will be the initial status of your tickets. |
Closing Status |
This will be the status of your tickets which are closed by DefensX Backend. Do not forget to scroll down to see more statuses. |
Ticket Title
The Ticket Title field allows you to customize the summary/title of the service tickets created in your PSA. You can use a combination of plain text and dynamic variables to make the ticket titles more descriptive.
-
{{report_type}}: The type of the generated report (e.g., User Feedback, URL Block).
-
{{hostname}}: The domain or server name where the event occurred (e.g., example.com).
-
{{user}}: The name, email, or username of the user who performed the action.
If you leave this field blank, the default format will be used: New user request: {{report_type}}.
Billing Integration
|
Tip
|
If you are not interested with the Ticket Integration, you can skip the action by clicking Status at the top.
|
|
Important
|
Only Monthly Recurring Invoices will be listed here. Also, make sure that the invoice is assigned to the related client.
|
Synchronization
Your integration has been set, and it will be periodically synchronized. However, you might want to trigger the first synchronization manually to speed up the integration.
Questions & Answers
If a site does not have a "general user" assigned, this error may occur. To resolve the issue, try creating a user record for the site with username of 'general user'.
|