This document provides a step by step guide for creating a Naverisk connector in Power automate.

1. Navigate to Settings → Power Automate

2. Click on New to create a new Application Key, once the key appears, the Integration Status will be changed to Enabled. Then click on Save

NOTE: Every time a new key is created in Naverisk, it will also need to be updated in Power Automate

1. Access the Naverisk Power Automate APIs via this link: https://trial1.naverisk.com/swagger/ (change the URL to the applicable test server).

The API Docs URL is used to create the Naverisk connector

2. Copy the API Docs URL and paste it into the browser URL section, then press Enter

3. Press Ctrl + A to select all the info on the page, then copy and paste it into a new note in Notepad. Then save it in a .json format

4. Log into your Power Automate environment with your credentials

- URL: https://make.powerautomate.com/
Note: If the Power Automate page appears blank, remove any extra parts from the URL that may have been added automatically.

5. Click on “Custom connectors” (if it’s not listed there, click on More)

6. Click on + New custom connector

7. Click on Import an OpenAPI file

8. Enter a Connector name and import the .json file saved from the Naverisk API Docs URL, then click on Continue.

9. You can upload the following connect icon by clicking on Upload

Icon:

10. Enter a description that is at least 30 characters; otherwise, there will be issues when trying to connect. Then, click on Security at the bottom of the page

11. In the Authentication type dropdown, select API key

12. Under API Key, enter a Parameter label (it can be anything).
​
Under the Parameter name, you must enter the following, as it is the identifier used within Naverisk. Ensure that it matches exactly and is case-sensitive.

Then click on Definition

NOTE: The APIs have pulled everything across to Power Automate under Actions.

13. Now, click on Create connector

Troubleshooting: If the connector fails to be created, it's often due to an issue with the OpenAPI file, such as a malformed or incorrect API definition. Double-check the JSON file and your Naverisk API Docs URL.