{"id":29328,"date":"2021-09-13T17:51:16","date_gmt":"2021-09-13T12:21:16","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=29328"},"modified":"2021-09-14T17:54:49","modified_gmt":"2021-09-14T12:24:49","slug":"use-of-custom-api-in-power-automate-flow","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2021\/09\/use-of-custom-api-in-power-automate-flow\/","title":{"rendered":"Use of Custom API in Power Automate Flow"},"content":{"rendered":"

Introduction<\/strong><\/h2>\n

As seen in our previous blog<\/a>, we can create a custom API that can be triggered in Dynamics 365 CRM Workflows. But since Microsoft is moving away from Dynamics 365 CRM Workflows to Power Automate Flows, we should too. So, in this blog, we will see how to use the same Custom API in a Power Automate Flow.<\/p>\n

After creating a custom API, follow the steps given below:<\/p>\n

    \n
  1. Navigate to your environment from make.powerapps.com<\/a> and to your solution -> Click on New -> Select Cloud Flow.<\/li>\n<\/ol>\n

    \"Custom<\/a><\/p>\n

      \n
    1. Search for \u201cwhen a row is added\u201d in the trigger and select \u201cWhen a row is added, modified or deleted<\/strong>\u201d trigger.<\/li>\n<\/ol>\n

      \"Custom<\/a><\/p>\n

        \n
      1. Rename the flow step. (Note \u2013 It is recommended to uniquely name every step to prevent confusion in case the power automate flow gets a bit complex).<\/em>\n
          \n
        1. Select \u2018Added\u2019 in change type and \u2018Accounts\u2019 in Table Name since we want this flow to run when a new account is created.<\/li>\n
        2. Choose scope from Organization\/Business Unit\/Parent: Child Business Unit\/User as per your requirement.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

          \"Custom<\/a><\/p>\n

            \n
          1. Click on New Step -> Search for \u201cPerform a bound action\u201d and Select \u201cPerform a bound action<\/strong>\u201d from Actions.<\/li>\n<\/ol>\n

            \"Custom<\/a><\/p>\n

              \n
            1. Rename this flow step.\n
                \n
              1. Select \u2018Accounts<\/strong>\u2019 in Table name since our custom API is bound to the Accounts entity.<\/li>\n
              2. Select the action by its unique name in Action Name.<\/li>\n
              3. Select unique identifier of the Account (added in the previous step) in Row ID as shown below:<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

                \"Custom<\/p>\n

                After this, the step would look like below.<\/p>\n

                \"Custom<\/a><\/p>\n

                  \n
                1. This is pretty much it. Next, give a proper name to your flow and save it.<\/li>\n<\/ol>\n

                  \"Custom<\/a><\/p>\n

                    \n
                  1. Now, whenever an account record gets created, a phone call activity associated to the account will also get created with the due date set as the next day and thus can be seen in the Timeline as well.<\/li>\n<\/ol>\n

                    Conclusion<\/strong>: In this way, we can easily use the custom API in Power Automate Flow.<\/p>\n","protected":false},"excerpt":{"rendered":"

                    Introduction As seen in our previous blog, we can create a custom API that can be triggered in Dynamics 365 CRM Workflows. But since Microsoft is moving away from Dynamics 365 CRM Workflows to Power Automate Flows, we should too. So, in this blog, we will see how to use the same Custom API in\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[16,19,36,38,1985,2361],"tags":[2367,1975,1989],"class_list":["post-29328","post","type-post","status-publish","format-standard","hentry","category-dynamics-365","category-dynamics-crm","category-microsoft-flow","category-microsoft-powerapps","category-power-automate","category-technical","tag-custom-api-dynamics-365","tag-power-automate","tag-power-automate-flows"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/29328","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=29328"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/29328\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=29328"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=29328"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=29328"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}