HaloITSM Guides

Documentation to assist with the setup and configuration of the HaloITSM platform

GoCardless Integration

The GoCardless integration with HaloPSA doesn't currently support payment processing, this will be available in the near future.

To begin integrating with GoCardless, you must enable the integration module in Halo (Configuration > Integrations), by clicking on the + sign on the module:

Fig 1. The GoCardless Module

You can match GoCardless Companies to HaloPSA Customers/ Site if they are the same. When the Names are different across GoCardless and Halo, the user will be placed into the "Default Site" which is set on the integration page shown in Fig 2:

Fig 2. Custom Field Mappings

The site which is synced to when importing users, will be the default site of the customer (The Invoice Site). After the initial import, you can move users into the correct sites, this will not affect the syncing of users, as the Halo integrator will match onto the user and not the site, when recurring syncs are enabled.

If you have not yet setup the Halo Integrator, use the following guide: Halo customers that are On-Premise can setup the Halo DB Integrator (This is only for On-Premise customers as hosted customers have this hosted on Halo by default) The difference between the Integrator and the DB Integrator is explained in the DB Integrator guide.

Fig 3. Enabling the Halo Integrator for this Integration

From here you can enter your access token and begin mapping your customers in GoCardless to your users in Halo. There is an import users button for importing users into Halo, the below fields(Shown in Fig 4) will be populated based on the customers details in GoCardless. To sync custom fields from GoCardless to Halo, add them via the mappings table.

Fig 4. Importing Users from GoCardless

You can add custom fields to a Customer in GoCardless, and then map to fields in Halo (As shown in Fig 2). Within Halo, these will have to be custom fields of type "Text" and Entity: User. The field mapping example is shown in Fig 2.

Fig 5. The "User" Entity for Custom Fields

Custom Fields can be added to customers in GoCardless:

Fig 6. Adding Custom Fields in GoCardless

This will be added to the user in Halo, notice that the custom field mappings will need to be added to for this below field to populate (Fig 7). The import screen does not have custom field columns, this is why you must add to the field mappings table: