Webhooks allow you to set up prebuilt posting instructions for events within WorkFlow.
Storing Authentication for Webhooks
Although the webhook itself allows you to put in any header information you wish, it does not encrypt that information. Please use the Webhook connection to store any sensitive authentication information.
Webhook connections store private webhook authentication header information. Items like bearer tokens or usernames and passwords need to be stored securely.
This section allows you to place authentication into an area that will encrypt it and store it so it cannot be seen in the UI or Database.
- The name of the connection that is easily identifiable by you.
- A brief description of the connection.
- Authentication headers that are to be used and encrypted for re-use.
- Any other headers you would like to reuse in all other Webhooks that use this connection.
The Webhook itself along with the selected connection contains the payload that will be posted when an event occurs.
- The name of the Webhook that is easily identifiable by you.
- The Webhook connection you would like to use. See above.
- The Request Method you would like to use. POST, GET, PUT, DELETE
- The URL that you will be sending your request to. Please make sure this URL is secured via HTTPS.
- The content type of the data you will be sending.
- Any additional header you would like to include. Please do not put any authentication here.
- The body of the request. Currently, only JSON body content is supported.
- If you would like to validate or assert response information, you can make sure a JSON path evaluates to a specific value.
- If you would like to grab information from the JSON path response and store it as variable, you may reuse this variable later in the workflow.
Updated over 1 year ago