...
The mandatory information for a webhook configuration are:
Webhook Name: The name to be displayed for the webhook
Authentication Type
None Authentication: No Authentication is set for this webhook. This is the least secure configuration available;
Basic Authentication: Username is needed for the workflow Configuration. Uppon selecting this type of Authentication, a search field will be available for the Customer to attribute a user to this workflow. A dropdown list of available users will be available for selection.
The user field will list all the users the current administrator has access to;
Bearer Authentication: Upon Selecting the Bearer Authentication, the credentials field will be populated with an auto generated token that will be used to authenticate when executing the webhook.
...
Available in the Create Webhook Area is a workflow tree that shows all the available workflows for the current user, witch is also a mandatory information for the webhook configuration. Upon selection, this workflow will be associated with the webhook, and will be the one executing upon trigger of the webhook.
The customer can also search for workflows available from the tree;
After all the configurations have been properly set, the URL, Request Body and Response field will be auto populated with relevant information about the webhook configurations.
...
Bellow an example of webhook configuration after all configurations set up:
...
...
Note: The webhook is not active after creation by default.