Adding an HTTP trigger to a task enables the execution of this task using a web hook URL. The URL can be copied from the trigger configuration in the Task Planner GUI.
There is only one setting for this trigger: the task owner can decide whether the user triggering the task execution has to be authenticated. The following selection is available:
The same task will not be queued for execution again if it is already in the queue or being executed.
If executing a task was successfully triggered (e.g. via browser or curl) an HTTP Status 200
with the task id will be the response. Errors will be presented depending on the content type.
Note: You have to have the WebAPI enabled enabled in order to trigger tasks using the HTTP trigger.
The HTTP trigger supports placeholders that can be used in subsequent jobs and actions. You can use the following placeholders:
http.parameters
- a concatenated string of all parameters send to the triggerhttp.parameter1
- http.parameter9
- the first nine parameter
query entries send to the triggerNote: Please take into account the security implications of using the placeholders. Please use responsibly.