With Custom Actions, it is possible to string together a set of actions that are executed whenever a Webhook.site URL receives a request. The actions can extract data from the request and use it to send another request as well as modify the response.
With this, you can connect APIs that aren’t compatible, convert a request to an email, and much more.
Executes custom scripts. More information here
This action runs a JSONPath query on the contents of a request. With it, you can extract any data from a JSON document and store it in a variable, which can then be used in a downstream action.
JSONPath is very similar to the
jq commandline utility.
For more details on what’s possible with JSONPath, take a look at the docs.
As you start entering a JSONPath, the results are validated and shown next to the input field.
This action runs a Regex (regular expression) query on the contents of a request. With it, you can extract any data from a text document and store it in a variable, which can then be used in a downstream action.
As you start entering a Regex, the results are validated and shown next to the input field.
This will send a request with variable contents from the Webhook.site cloud. Per default, the request contents will be identical to what was sent to the URL originally.
Variables extracted previously can be used.
The response of the request is stored in a series of variable names prefixed with a value of your choosing. The following variables are set after the request has been fired:
$your_prefix.content$- response body content
$your_prefix.status$- response status code
$your_prefix.headers$- response headers
$your_prefix.url$- the URL the request was sent to
This will send a email with variable contents from the Webhook.site cloud. Variables extracted previously can be used.
This action can be used to modify the response of the Webhook.site URL based on the input.
Useful if you need to validate that the request does or does not conform to certain criteria, the Condition action will either stop or continue based on a condition.
In both the input and the value fields, variables will be replaced (including Global Variables from the Control Panel), so you can compare e.g. JSONPath or Regex values - or even values from a previous HTTP request that was sent.
Currently, two actions are provided: stop and continue. Stop will stop further action execution of the condition is a match. Continue will only continue further execution if the condition is a match, and otherwise stop.
The following “operators” are available:
- is equal to
- is not equal to
- starts with
- ends with
- does not contain
- is greater than
- is greater than or equal to
- is less than
- is less than or equal to
The “result” of the condition will be logged below the request details, so you can see what happened.