Installing and Configuring Power Automate Integration

Table of Contents

Overview

To automate your workflows, enable actions and triggers in a Power Automate flow within the Microsoft Power Platform. Triggers. These are starting points that you have selected in a connector, which affect your actions.

See the the list of all Power Automate triggers and actions.

Prerequisites

Before beginning the installation, ensure that the following prerequisites have been met:

You have created a KanBo account with a Power Automate license. This account will appear in KanBo as performing the Power Automate flow actions.
You have received a set of unique URLs, a client ID, a client secret, and a JSON file for the custom connector.
You have access to the KanBo app and can modify its appsettings.json configuration file
You are able and/or allowed to restart the KanBo app

KanBo configuration

Open your KanBo appsettings.json configuration file.
Check to see if your KanBo is loading the OAuth assemblies in the “assemblies” array:

"assemblies": [
{"Path": "KanBo.Oauth.dll"}
],

Add {“Path”: “KanBo.Oauth.dll”} to the array if it’s missing.
Then, add it to the “plugins” section in appsettings.json file.

{
    "type": "auth.oauth",
    "issuer": "mypaissuer",
    "children": [
     [
      "cert",
      {
       "type": "x509-store",
       "store-name": "my",
       "store-location": "currentuser",
       "key": "thumbprint",
       "value": "KANBO-THUMBPRINT",
       "valid-only": false
      }
     ]/*,
     {
      "type": "client",
      "id": "",
      "secret": "",
      "url": "https://brokerurl.com",
      "name": "KanBo Power Automate Integration",
      "scope": "kanbo.id security.* offline_access"
     }*/
    ]
   },

This section will be edited again after KanBo is restarted, but three other sections need editing first.

Change the issuer:

"issuer": "mypaissuer",

We recommend changing “mypaissuer” to a different name, such as “companynameissuer.” However, this is not required.

Change the KANBO-THUMBPRINT:

"value": "KANBO-THUMBPRINT",

Here, you should use the same certificate thumbprint that you are using in the rest of the KanBo app settings.json file, such as in the “auth-aad” or “webjobs” packages.

Change the broker URL:

https://brokerurl.com

Change the URL to the broker URL that you received from us, keeping the “https://”.

Save the file, then restart KanBo.

Creating an OAuth authorization

After the app is restarted, generate values for OAuth authorization. Go to a URL structured like this:

https://mykanbourl.com/auth/issuer/newclient

Replace “mykanbourl.com” with your KanBo URL and replace “issuer” with the value you set in the appsettings.json file in the previous step.

If everything has been done correctly, you should see a text output that looks like this:

Client config:
{
"id": "6fxxxxxxxxxxxxxxxxxxxxxxxxxxcf",
"secret": "JC1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxaz4=",
"url": "https://return-url",
"name": "Some App"
}

OAuth2 config:

Client Id: 6fxxxxxxxxxxxxxxxxxxxxxxxxxxcf
Client Secret: rvDETxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxVScpGE
Authorization Url: https://mykanbourl.com/auth/issuer/code
Access token request url: https://mykanbourl.com/auth/issuer/token
Refresh token request url: https://mykanbourl.com/auth/issuer/token

OpenID Connect config:

Client Id: 6fxxxxxxxxxxxxxxxxxxxxxxxxxxcf
Client Secret: rvDETxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxVScpGE
Authority: https://mykanbourl.com/auth/issuer

To avoid generating a new section, it is recommended that you save the above output in full in case an issue arises.

In the “Client Config” section, the “id” and “secret” values must be entered into KanBo’s appsettings.json file. The final section should look like this:

{
    "type": "auth.oauth",
    "issuer": "issuer",
    "children": [
     [
      "cert",
      {
       "type": "x509-store",
       "store-name": "my",
       "store-location": "currentuser",
       "key": "thumbprint",
       "value": "a2e1ffdb7038279aeeb468bb4f9fcd27",
       "valid-only": false
      }
     ],
     {
      "type": "client",
      "id": "6fxxxxxxxxxxxxxxxxxxxxxxxxxxcf",
      "secret": "JC1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxaz4=",
      "url": "https://brokerurl.com",
      "name": "KanBo Power Automate Integration",
      "scope": "kanbo.id security.* offline_access"
     }
    ]
   },

Make sure you drop the comment delimiters (/* */).

Restart KanBo.
We need to receive the “OAuth2 config” from you in order to establish communication between your KanBo and our Power Automate broker. For now, continue with the instructions. There is one more piece of information that you will need to send us, which you will create in the next step.

Creating the custom connector

Go to make.powerautomate.com and open the Custom connectors panel.

If the option does not appear, go to More > Discover All. You can find custom connectors under the Data tab.

In the top right select + New custom connector > Import an OpenAPI file.
Choose the KanBoOpenAPIFlow.json file that we sent you.

Check the following values on the first page:

Check if the Host section has the correct broker domain that we sent you.
Check if the Base URL has the correct issuer that we sent you. It should be something like /yourcompany/api.
Optionally, but recommended, change the custom connector icon and background color.

Select Security.

Change the Client ID, Client secret, Authorization URL, Token URL, and Refresh URL to the values you received from us.

In the top right corner, select Create Connector. You should then see something like this:

Your custom connector’s unique Redirect URL has now been generated. Please copy it by selecting the copy icon.

Connecting the custom connector

Before continuing, please send us the following information:

The “OAuth2 config” section that you generated previously,
The Redirect URL of your custom connector from the previous step.

We will then enter those values into our Power Automate broker. We will inform you once this is done.

Next, create a connection between Power Automate and KanBo. Follow the steps below to create a new flow with an action from the KanBo custom connector.