The HTTP web hook is a way to kick off a Chain programmatically. This is benifical on many fronts as you can incorporate it in other 3rd party applications easily. You can provide it 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.

📓 Only the POST HTTP method is supported. Also, it has to be the start node position.

Getting Started

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

Editing the Command

Edit the command to populate the fields:

  1. Name (optional): Can be updated to something more meaningful

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

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

  4. Bearer Token: Generate a strong-key that will be used to identify your process and keep it secure. You will want to also note this token as 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 your authorization header.

Webhook URL

The Webhook URL noted in the command is what will be called from a 3rd party tool such as cURL or PostMan. In the screenshot below we have configured PostMan with the following:

  1. The POST url from the Webhook Event Command

  2. The Bearer Token we configured in the Webhook Event Command

  3. A JSON Payload

After we execute the request we will receive the following response:

Verifying inside of OneCloud

Going back into OneCloud we can notice in the Monitor that our command did run and provided the JSON payload as output.

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

Did this answer your question?