Webhook

Hi Kate,

I'm aware of the possibility to start a NWC using an external API call. But I was thinking about leveraging the "webhook"-standard to register NWC to being called by 3rd Party systems, which allow to register webhooks to events.

see: https://en.wikipedia.org/wiki/Webhook
for an high-level overview see: https://docs.microsoft.com/en-us/aspnet/webhooks/

Hi Henning,

Thank you for clarifying, I think I understand what you're looking for now.

Questions about how this feature would be configured:
- Can you provide the scenario you want to achieve, where the same workflow design could be triggered by multiple systems?
- Are there other examples of 3rd party systems which you would want to call the same workflow?
- Given data-format often varies between systems, how will the system-specific event context be passed into the same workflow? How do you foreseeing the variables to reference system's data format?

Thanks,
Kate

Hi,

I could imagine having a workflow, that is hooked to a 3rd party system via a webhook. This way this workflow could be triggered by some system, when this webhook is called.

I would not see just one workflow listening to different webhooks, but instead having one workflow associated with one webhook.

As for incoming parameters: the data will be passed to the webhook as json anyway. Why not have that data available within NWC as a json data-structutre and then be able to query this data-structure within the workflow?

Hi Henning,

Just following up on this - I don't fully understand the ask . There isn't a webhook standard per say. The GitHub link you provided is just how GitHub expects you to provide when you want to register a webhook with their system. Dropbox / Box would expect different parameters.

Even IF you had a standard and always got a single json payload - you'd need to query it and assign the values into variables. It'd seem cumbersome to have 1 webhook / workflow to multiple 3rd party systems. Because that one workflow will be so large to try to accommodate the different systems it could potentially be used with.

However, we do have Xtensions Events that we're currently developing that will allow you to create a custom event that you can then use in your workflow. Upon publishing the workflow, based on the event definition, we'd then register the webhook against the URL / 3rd party that has been provided.

Let me know if the Xtensions Events is closer to what you're envisioning.

Josh