Webhooks are user-defined HTTP callbacks. Webhooks allow you to build or set up integrations. They are usually triggered by some event, when that event occurs, the source app makes an HTTP request to the URI configured for the webhook.

A detailed description of the webhook setting can be seen in the table below:

Setting Webhook URLs

The URL on this webhook is the default and will be filled automatically when you create a workflow process and add webhook components.

Description of URLs:

  • {URL}: Used to pass information to the destination.

  • {Path}: Location of data on the server

  • {workflow_id} : ID that is automatically created when creating a workflow process.

  • WF : Code from workflow process (default)

  • {node_id} : ID obtained from the field name.

  • {webhook_path} : The keywords entered in the webhook path field (e.g whAddGitlabIssue).

{node_id} and {webhook_path} will automatically be created when adding a node in the workflow process. When a node has not been added, {node_id} and {webhook_path} are {empty}.

Using Dynamic Variable in Response Expression

In the WebHookReply Workflow, we take the example of the 'webHookReply' process. This process is to provide a feedback response to requests sent, this response is in the form of an 'output' object whose value is ${mvelReply.response}. This ${mvelReply.response} variable is to contain the response id of the 'webHookReply' process.

To display the response of dialog, you can use the value of success using ${wf.success} variable. ${wf.success} variable serves to define workflow process is true or false. For example, if we set the value of success using $ {wf.success}, when the workflow process starts and in the middle of the process an error occurs, the value success will automatically define that the process is false.

A detailed description of the response expression can be seen in the table below:

Last updated