Microsoft Request Trigger - Webhook Change

I just received this notification from Microsoft:

image.png

I have no idea what affect this will have on my webhook flow. I imagine this is going to break the flow from triggering as the old URL is registered with Blackbaud webhook monitor.

@Ben Wong Is Blackbaud aware of this and potentially has instruction coming up for updating the webhook information, or do we need to setup new webhook. If we need to setup new, would the previous instruction you provided still works?

Answers

  • I got a similar email about a flow I have with the request trigger.
    I went ahead and tested the new HTTP URL in my browser and it significantly changes schema of the trigger output.

    Old trigger output:

    image.png

    New trigger output:

    image.png

    The problem this causes for me is the parameter I've got on the end of the url no longer generates a queries object as part of the output. My flow tries to use this information later and thus fails.

    I might be able to get my case to work by extracting the same string from the "x-ms-igw-external-uri" header