HTTP

The Task Planner HTTP action allows to run an HTTP Request after a Job has completed. The action can be configured to use the following methods: GET, HEAD, POST, POST with multiple parts, PUT and DELETE.

The action calls the given URL for every File- or None- Result-Flavor1).

The methods for POST and PUT additionally allow the transition of File-flavor result data.

Task configuration

  • URL: The address to call. It can contain placeholders as well.
  • Method: The HTTP method to use for the request (see below).
  • User: An optional user for Basic Authentication
  • Password: An optional password for Basic Authentication
  • Json: A text area with optional JSON data to be sent with a request when using POST or PUT methods
  • Headers: Optional headers to be sent with the request

HTTP Methods

The supported HTTP methods are: GET, HEAD, POST, POST with multiple parts, PUT and DELETE.

POST and PUT

The HTTP methods POST and PUT will send the received File-flavor result data along to allow file uploads. The URL will be called for every File-flavor result.

Note: If the JSON data field is set, it accounts for an individual File-flavor result and is sent in a separate request.

POST with multiple parts

The method POST with multiple parts will result in a single request to the given URL. The File-flavor results will be packed in a multipart/form-data container. Every file will be denoted by the form element name file[] to allow optimal integration into many back-ends.

Note: JSON-Data uses the element name json.

1)
Except for the POST with multiple parts