Power automate from a dynamic button -flow will break

Hello, PA has recently changed the structure of http requests, I am getting a notification that if I don't change them they will break on 30Nov

the url is now different for http requests in that it contains '''default… rather than …westeurope.logic.azure…

If I follow this process to test this at step 8

Create an acknowledgement letter from an add-in button on the gift record - Microsoft Integrations

the button won't work and I am concerned my live flows will break and as yet I don't have a solution, has anyone been able to solve this?

Answers

  • Alex Wong
    Alex Wong Community All-Star
    Ninth Anniversary Kudos 5 Facilitator 3 Raiser's Edge NXT Fall 2025 Product Update Briefing Badge
  • Alex Wong
    Alex Wong Community All-Star
    Ninth Anniversary Kudos 5 Facilitator 3 Raiser's Edge NXT Fall 2025 Product Update Briefing Badge

    What needs to be done is:

    1. Edit your flow (no need to do anything in the flow and save) and go to the trigger action at the top, the NEW URL is right in the trigger for you to copy
    2. go to any URL Encoder tool on web and put the URL there and encode it
    3. go to developer.blackbaud.com and your application where the custom tile is defined.
    4. update the add-in for the custom tile where it is calling the flow's OLD encoded URL and replace it with NEW.
    5. DONE
  • Thanks Alex, if I follow your process it won't accept the encoded url with an error msg as follows: Please enter a valid url

    it will accept this url

    https://app.blackbaud.com/addin-webrequest-action?url=<encoded url>&title=buttontest

    but when i click on the add in on an action I get the following error:

    The web request action returned an error response: 401

  • Alex Wong
    Alex Wong Community All-Star
    Ninth Anniversary Kudos 5 Facilitator 3 Raiser's Edge NXT Fall 2025 Product Update Briefing Badge

    my original URL from flow (modified 1 section of URL to be all 'a' for sensitivity):

    https://prod-34.westus.logic.azure.com:443/workflows/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/triggers/manual/paths/invoke?api-version=2016-06-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=q69i9MQ7RlWvP8qAW5f7QvZtNbZJ9CoXJK1-Dz1NhSM

    original application URL from developer.blackbaud.com (purposely separated the "url encoded piece" into another line):

    https://app.blackbaud.com/addin-webrequest-action?url=

    https%3A%2F%2Fprod-34.westus.logic.azure.com%3A443%2Fworkflows%2Faaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa%2Ftriggers%2Fmanual%2Fpaths%2Finvoke%3Fapi-version%3D2016-06-01%26sp%3D%252Ftriggers%252Fmanual%252Frun%26sv%3D1.0%26sig%3Dq69i9MQ7RlWvP8qAW5f7QvZtNbZJ9CoXJK1-Dz1NhSM

    &title=Create%20AirReg%20Import%20Files&buttonStyle=Add&invokedMessage=AirReg%20Import%20Files%20Creation%20Request%20Submitted!

    new flow URL (also masked with 'a' and 'b' for sensitivity):

    https://ddfbf6987da5e3b8bb4934b1318ad4.15.environment.api.powerplatform.com:443/powerautomate/automations/direct/workflows/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/triggers/manual/paths/invoke?api-version=1&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb

    new application URL for developer.blackbaud.com:

    https://app.blackbaud.com/addin-webrequest-action?url=

    https%3A%2F%2Fddfbf6987da5e3b8bb4934b1318ad4.15.environment.api.powerplatform.com%3A443%2Fpowerautomate%2Fautomations%2Fdirect%2Fworkflows%2Faaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa%2Ftriggers%2Fmanual%2Fpaths%2Finvoke%3Fapi-version%3D1%26sp%3D%252Ftriggers%252Fmanual%252Frun%26sv%3D1.0%26sig%3Dbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb

    &title=Create%20AirReg%20Import%20Files&buttonStyle=Add&invokedMessage=AirReg%20Import%20Files%20Creation%20Request%20Submitted!

  • Alex Wong
    Alex Wong Community All-Star
    Ninth Anniversary Kudos 5 Facilitator 3 Raiser's Edge NXT Fall 2025 Product Update Briefing Badge

    Assuming you did this correctly, then go to RE NXT and click on the action you put in. What you should make sure is if the flow has a run history from your click on the action after you changed the URL. If the flow run history shows a run, that means you done this correctly.

    If you got error, then it means your flow is running with an error, that requires you to debug the run to see why it returned an error.

  • Alex Wong
    Alex Wong Community All-Star
    Ninth Anniversary Kudos 5 Facilitator 3 Raiser's Edge NXT Fall 2025 Product Update Briefing Badge

    @Crystal Bruce may want to move this post to the SKY Developer forum