Skip to main content

Power Automate Customer Connectors

Recently I came across a requirement to create an interface between SharePoint and 3rd party project management tool.

Click here login with your Ofice365 account. Click on Data > Custom Connector menu option from left navigation pane.




















Click on "New Custom Connector" from top right corner.










Select Create from blank. You can now see a new connector creation screen.

General Tab

Provide the host URL and API end point URL. Click on "Security" tab select the authentication method that the source tool is using.











Security Tab

Based on your selection rest of the input controls will be be shows, Lets assume you have selected 0Auth 2.0.

You should now see columns like 

  • Client ID : is id from app registered in project management tool to consume API. 
  • Client Secret : is a secret key generated by the source from where you are to consume API.
  • Authorization URL : is token generation endpoint URL. 
  • Token URL : is Refresh token URL.
  • Scope : Specify if the API documentation has any details for it.
  • Redirect URI : This is auto generated by power automate, you need to copy this and configure it in your app that you register to consume API's in source system.










Now, lets go the the definition tab. 

You can create 3 things here.

  1. Actions: Allows you to create an action from one API endpoint. Actions are basic components that we use while creating a Flow ex. GetItems, GetFileName and so on...
  2. Triggers: Triggers are events that would result into starting the flow execution.
  3. Policies: Policies can be used to perform actions like replacing the endpoint url before the call is made. We can also create a policy that ensures a set of headers is always passed with each call and so on. 

Definition Tab

To create an action, click on "New Action" button

Fill the Summary, Description and Operation ID. Operation ID is the one that will be visible as action title. Description is that we see while adding the action in power automate flow.


Visibility
  1. None: Shows properly to take input, when action is added.
  2. Advanced: These input boxes are mostly of not required type and will be visible only when "Show Advanced Mode" is clicked.
  3. Internal: Internal visibility is used when you have static values of calculated values to be passed.
  4. Important: Important ensures that field is shown on top.






Request

Click on "Import from sample"


Select verb, add the end point URL, headers and default body if necessary.

Click on "Import" button. this will handle the request body part.

























Note: You can add Query String and body parameters to the request URL, this can be modified later. You can also attach dependent actions to get dropdown options for lookup values. 

Response

You can add default response by clicking on "Add default response". You can rename the response title as well.

You are done with custom connector.

Note: you can update each Request/Response properties display name and description. 

Test Tab

You can now click on test tab, select your action and perform a test.
Labels:

Comments

Post a Comment

Popular posts from this blog

Business Data Connectivity

I came to a requirement wherein I was supposed to get data from an 3 rd party portal using API’s and then bring them to SharePoint server. The first approach that I finalized was just to make BDC solution that will get data from 3 rd party portal and will deploy it to SharePoint. How to Create BDC solution in SharePoint? I found below link that is having really great description about hot to create and deploy the BDC solution to SharePoint. http://www.c-sharpcorner.com/uploadfile/hung123/creating-business-data-connectivity-service-using-visual-studio-2010/ After creating an POC I came to know that BDC model cannot be deployed on Multi tenant farm. So what can be done next? After some amount of googling I came to know that we can create BDC solution using WCF services also. So I created a WCF service solution that acted as a wrapper that used to fetch data from the portal. We can them publish that service to IIS or Server and use the servic...
2 comments
Read more

Dataverse Multi Choice Columns in PowerApps

We have been working with PowerApps, PowerApps and Dataverse and now I thought of sharing a few tips to ease your work if you are new to PowerApps + Dataverse as a combination. I will be sharing a few more tips in my upcoming blogs but to get started, Let’s take Multi Choice Columns this time. Unlike SharePoint or any other data source, Dataverse Multi choice columns are different so basically, I cannot go to my PowerApp and directly print selected value in a label. So, this is how you can show multi choice values in label. You need to use concat that allows to concat multiple selection. PowerApps has concat function that takes. Concat function syntax :  Concat (  Table ,  Formula  ) In my case I am trying to render a multi choice column values into a vertical gallery webpart. I have added a label control to a vertical gallery and then added below code.   Concat(ThisItem.ColumnName,Value & "") Hope this helps, Thanks, Keyur
Post a Comment
Read more

SharePoint Migration : This content database has a schema version which is not supported in this farm

Today one of my client was expecting to restore a SharePoint Site Collection from and Database that he already took as a backup.  I followed below steps.           1.        Imported content database to SQL of the farm where the site is to be restored.           2.        Created a web application.           3.        Visited manage content database, set the current database property to offline.           4.        Click on add a new content database.           5.        Set the name of the content database same as the database that is imported to SQL.   SharePoint gave me below error. “ This content database has a schema version which is not supported in this farm." I tried to use powershe...
2 comments
Read more