{"id":40635,"date":"2025-03-17T17:32:48","date_gmt":"2025-03-17T12:02:48","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=40635"},"modified":"2025-04-17T12:33:48","modified_gmt":"2025-04-17T07:03:48","slug":"auto-populating-power-automate-callback-urls-for-http-flows-in-dataverse","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2025\/03\/auto-populating-power-automate-callback-urls-for-http-flows-in-dataverse\/","title":{"rendered":"Auto-Populating Power Automate Callback URLs for HTTP Flows in Dataverse"},"content":{"rendered":"

\"HTTP<\/p>\n

In our previous blog<\/a>, we covered regenerating the SAS key to secure Power Automate flows<\/a>. While security is important, another challenge is managing callback URLs, which are crucial for external applications to trigger automation, especially in large-scale implementations. Manually accessing the Power Automate portal, finding the flow, and copying the callback URL each time is time-consuming and prone to errors.<\/p>\n

To solve this, we developed a method to programmatically fetch and store the callback URL using the Power Automate Management connector within a Power Automate flow.<\/p>\n

In this blog, we will demonstrate how to automatically populate the Callback URL field with the URL of a specific HTTP-Triggered flow whenever a new Setting record is created in Dataverse. Additionally, this approach can be customized by adding conditions to retrieve different HTTP-Triggered flow callback URLs based on your requirements.<\/p>\n

Step-by-Step Approach to Retrieving and Storing the Callback URL<\/p>\n

1. Sign in to the Power Automate Portal<\/a> and navigate to your flows.<\/p>\n

2. Locate the flow that contains the HTTP-triggered action and note down the exact name of this flow.<\/p>\n

3. Create a new flow and choose the trigger based on your requirement. In this case, we want to trigger the Power Automate flow when a new Setting entity record is created in Dataverse.<\/p>\n

\"HTTP-Triggered<\/p>\n

4. “When a row is added” needs to be set as the trigger. Choose the table name as “Setting” (Custom Entity) and set the Scope to Organization.<\/p>\n

\"HTTP-Triggered<\/p>\n

5. Add a new action, search for Power Automate Management, and select it.<\/p>\n

\"HTTP-Triggered<\/p>\n

6. Under actions, choose “List Flows as Admin (V2)”.<\/p>\n

\"HTTP-Triggered<\/p>\n

7. Under Environment, select a specific environment or use the current environment by setting the custom value:<\/p>\n

    \n
  1. \n
      \n
    1. Environment: workflow()[‘tags’][‘environmentName’]<\/em>.<\/li>\n
    2. Set “Include Soft-Deleted Flows” to No.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

      \"HTTP-Triggered<\/p>\n

      8. Add an action and search for “Filter Array”. Filter the flow by its display name:<\/p>\n

        \n
      1. \n
          \n
        1. From: value (from the “List Flows as Admin” action).<\/li>\n
        2. Condition: Flow Display Name is equal to \u201cYOUR_FLOW_NAME\u201d i.e equals(item()?[‘properties\/displayName’], ‘YOUR_FLOW_NAME’) <\/em><\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

          \"HTTP-Triggered<\/em><\/p>\n

           <\/p>\n

          9. Add a new action, search for “List Callback URL” under the Power Automate Management connector. Enter the following details:<\/p>\n

            \n
          1. \n
              \n
            1. Environment: Use your preferred environment or the current environment: workflow()[‘tags’][‘environmentName’]<\/em><\/li>\n
            2. Flow: first(body(‘Filter_array’))?[‘name’]<\/em><\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

              \"HTTP-Triggered<\/em><\/p>\n

              10. Check whether the callback URL from the “List Callback URL” action is null or not. If not null, update the respective entity field in Dataverse.<\/p>\n

              \"HTTP-Triggered<\/p>\n

              Conclusion<\/h2>\n

              By implementing this approach, you can automate the retrieval of call-back URLs, saving time and improving efficiency. With the Power Automate Management connector, the URL can be stored in Dataverse for easier and more scalable integrations.<\/p>\n","protected":false},"excerpt":{"rendered":"

              In our previous blog, we covered regenerating the SAS key to secure Power Automate flows. While security is important, another challenge is managing callback URLs, which are crucial for external applications to trigger automation, especially in large-scale implementations. Manually accessing the Power Automate portal, finding the flow, and copying the callback URL each time is\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":15,"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":[1985,2361],"tags":[3129,1975],"class_list":["post-40635","post","type-post","status-publish","format-standard","hentry","category-power-automate","category-technical","tag-http-flows-in-dataverse","tag-power-automate"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/40635","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\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=40635"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/40635\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=40635"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=40635"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=40635"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}