I am working on a flow that will be triggered when ever there are changes to a custom API I made. The parts I have been able to understand about using microsoft flow and Webhooks are:
1) I know i have to have a url for FLOW to request the creation of a webhook wherever it is your trying to request the information from (based of of multiple videos and documentation examples, including Microsoft tutorial on triggers, where GitHub was used).
What do I need to do in my API to create the ability for webhooks to be used, created/deleted, or even be registered in my own API?
2) when the API is found how do I format the JSON body or schema the best way? (whether the format for sending the information back to the place requesting it, this case FLOW, or receiving it, in this case the request from FLOW to HTTP POST)
I may not undestand everything. Im not sure if i understand webhooks fully. Its been a battle of about 8 hours of searching to udnerstand them even a little.
A) are webhooks objects or actions?
B) If so are webhooks objects on both ends of the request or a single object sent between two locations (server, client etc)
Im am very open to anything along these lines, or redefining what I think about webhooks, triggers, API calls etc.
It seems that you are trying to use Custom trigger in your flow, please take this doc on Use a webhook as a trigger for Azure Logic Apps and Microsoft Flow for a reference:
Please check the following doc on Custom connectors for more details:
Initially problem was understanding custom connectors, but the real struggle is building the webhooks. It took about 2 days to find the documentation under ASP.NET for how to make a webhookMeaning to write the code for them.
Thank you for your reply. I was able to firgure it out a little bit now. After some research on what webhooks were etc. A thought about it include links to ASP.NET Webhooks under triggers or something?