The HTTP webhook is a way to kick off a Chain programmatically. This is beneficial on many fronts as it may be incorporated in other third party applications easily. Users may provide a webhook with a JSON payload that is the output of the Command to be be used within the Chain for other Commands. It is very similar to starting a Chain via API or External Link.

📓 Two things to know. First, a webhook must be in the start node position. Second, only the POST HTTP method is supported.

Getting Started

Start by dragging the HTTP Webhooks Event into the Start Node position.

Editing the Command

Edit the command to populate the fields:

  • Name (optional): Can be updated to something more descriptive than the default.

  • Description (optional): Can be augmented to help identify the purpose or audit of the Command.

  • Trigger Event Details: Select the HTTP BizApp that is responsible for this connection. If one is not available, users need to setup and configure one.

  • Bearer Token: Generate a strong-key that will be used to identify your process and keep it secure. Note this token, because if it is lost cannot be recovered. A suggestion would be to use an available online tool to generate a base64 encoded string. This is used as part of the authorization header.

Webhook URL

The Webhook URL noted in the Command is what will be called from a third party tool such as cURL or PostMan. In the screenshot below PostMan has been configured with the following:

  • The POST url from the Webhook Event Command

  • The Bearer Token we configured in the Webhook Event Command

  • A JSON Payload

After executing the request the following response should be received:

Verifying Inside of OneCloud

Going back into OneCloud. notice in the Monitor that the Command did run and provided the JSON payload as output.

If you have any questions about Webhook Events, please feel free to contact us at

Did this answer your question?