HaloPSA

HaloPSA Guides

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

Guides > Microsoft Power Automate Integration

Microsoft Power Automate Integration

In this guide we will cover:

- Application Registration

- Microsoft Power Automate Configuration



The Microsoft Power Automate integration allows you to use Azure Power Automate to create flows that interact with the Halo API, allowing the automation of certain processes. 

To set this up you need to create a registered application in Halo and use this to create a custom connector.


Application Registration

To register a new application, go to Configuration > Integrations > Halo API > Applications. Here you can create a new application with the authentication method "Authorisation Code (Native Application). This will need to be set to use a client secret.


The redirect URLs need to be set to "https://global.consent.azure-apim.net/redirect" and "Allow Agent Logins" needs to be set.


Fig 1. Configuring the application.


The application needs to be granted the correct permissions for the API calls you wish to make. Granting all permissions is not recommended.


Microsoft Power Automate Configuration

With the Halo application now registered, you can go to Microsoft Power Automate to configure your custom connector.


In Power Automate, go to Data > Custom Connectors. If you don't have a Data tab, then go to More > Discover All and find Custom Connectors under the Data column. Create a new custom connector from blank. 


Ensure the scheme is set to "HTTPS" the host is set to your Halo URL and the base URL can be left as "/".


Fig 2. Custom connector configuration. 


Authentication

The authentication type is "OAuth 2.0" and the identity provider is "Generic Oauth 2".


The Client ID and secret from your registered application can then be entered. The authorization URL should be your instance's /authorize endpoint and the token and refresh URLs should be your /token endpoint.


You then need to specify the scopes you set for your application. For example, if your flow will be reading and editing tickets you will need to give it the scopes "read:tickets" and "edit:tickets".


Fig 3. Authentication configuration.


Copy the Client ID/Secret obtained in Halo in the previous step. Your Authorization URL is your Halo URL '/auth' i.e.: https://halo.haloservicesolutions.com/auth/authorize and your Token and refresh URL should be your halo URL /auth/token i.e.: https://halo.haloservicesolutions.com/auth/token


Definition

You can specify the actions, triggers, and policies that can be used as part of your custom connector here. This is how you can set up the API calls and responses that will be used as part of your flow. 

For further guidance on how to make specific API calls, consult our API documentation. 


Test

You can then test and verify your connector works before saving it.


Flows

Once your custom connector has been configured, you can then configure a custom flow in the My Flows section on Power Automate. You will be able to select your custom connector and its actions when configuring steps of your flow.



Popular Guides