Hi @gauthambr ,
Launch() is interactive, so I don't think it would be easy to get it to run suppressed.
If you have a premium license I'd suggest passing the web call off to Flow in the background.
You can create a PowerApps triggered flow that uses the HTTP/HTTPS function - this way you can use the same flow for different calls.
It does however carry a licensing implication.
Likewise, you could create a custom API for your azure function and then use the custom connector in PowerApps to execute the function.
Something I can't test as I don't have an API or webhook that would show me whether it works or not, is putting a dynamic URL into an image....So here, I would put an image on the page and set it's Image: property to varURL. Then set the varURL value to your URL with a button OnSelect:
UpdateContext({varURL: "your url here"})
As I say, I can't unfortunately test this so have no clue whether it will work or whether it will throw errors or anything else, but it might attempt to reach the URL which might be enough to execute the webhook, even if it doesn't actually have an image to render.
Hope this helps,
RT
