You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 26, 2018. It is now read-only.
As a citizen user, I would like the ability to trigger an integration through an external HTTP request to a well-known URL. When creating an integration, I would select WebHook as the start connection and specify whether data is accepted via the WebHook. If data is accepted, I should have the option of defining the type of that data via JSON or XML schema.
Integrations triggered via WebHook must have a publicly available URL endpoint which can be discoverable via the iPaaS UI so that this information can be passed along to clients invoking the WebHook.
The text was updated successfully, but these errors were encountered:
@kcbabo@zregvart I wonder where this story fits. Is this part of the "API Client connector" #119 Currently in the API client connector everything is focussed on outgoing connections, not incoming.
Is this an extra story (and if so, how should it be prioritized ?) or is this part of #119 ?
Agree with @zregvart. I view this story as a degenerate case of API provider - basically exposing an HTTP URL that can be used to start an integration.
As a citizen user, I would like the ability to trigger an integration through an external HTTP request to a well-known URL. When creating an integration, I would select WebHook as the start connection and specify whether data is accepted via the WebHook. If data is accepted, I should have the option of defining the type of that data via JSON or XML schema.
Integrations triggered via WebHook must have a publicly available URL endpoint which can be discoverable via the iPaaS UI so that this information can be passed along to clients invoking the WebHook.
The text was updated successfully, but these errors were encountered: