Set Up HaloPSA Ticketing Recipients
A ticketing recipient is a configuration linked to notification profiles. It automatically creates and closes tickets in HaloPSA based on the defined ticket details and settings.
A ticketing recipient includes four elements:
-
Ticket Details
Define the ticket type, category, urgency, initial status, and assignee.
-
Notification Settings
Configure acknowledgment settings, repeat failure behavior, and Windows Event Log properties.
-
Associated Notification Profiles
Select the ticket owner (SO, customer, site), choose notification profiles to associate with the recipient, and set escalation delays.
-
Notification Schedule
Specify whether the schedule applies to the entire day or a daily interval.
You can add or modify a ticketing recipient only if you have the appropriate permissions.
Configure HaloPSA
To ensure tickets sync correctly between N-central and HaloPSA, configure the following settings in HaloPSA:
Ticket type fields
Set all ticket type fields to Visible – Not Required.
-
Go to Configuration > Tickets > Ticket Types > Edit > Field list .
-
Set to Visible – Not Required.
Approval process
Disable the approval process to prevent ticket creation delays.
-
Go to Configuration > Tickets > Approval Processes.
-
Clear “Allow choice of CAB members when an approval step begins”
These settings ensure that required fields do not block ticket synchronization and that the correct ticket types are assigned during ticket creation from N-central to HaloPSA.
What do you want to do?
- Setup ticketing for the HaloPSA integration
- Setup a Notification Profile in N-central
- Create a Ticketing Recipient
- Configure Notifications for Status Changes
- Modify a ticketing recipient
- View notifications associated to a ticketing recipient
- Clone a ticketing recipient
