Give us the ability to call an api from a site script and not just a flow using the triggerFlow action
Currently we can trigger a flow from a site script using the triggerFlow action as described here.
However it would be nice to extend this to allow us to trigger a webhook or another endpoint (eg azure function).
Roman Rozinov commented
i do not have votes left, but I definitely second the idea of expanding the way site script can bootstrap other processes.
Flow triggers are Premium so not everyone want invest in licensing. Further, the security mechanism is lacking from what i can see, so Flow may not be ideal to bootstrap a custom process anyways.
It would seem to be better to expand the verbs based on what most people want to accomplish (create folders, for example) , but having multiple ways to accomplish those actions which still don't exist in the Site Script schema seems like a good idea.
Fabio Franzini commented
I think it's a good idea to call a secure endpoint, maybe registered as an application within Azure AD.