HTTP

The Task Planner HTTP job allows running an HTTP Request and collecting the response as File-results for subsequent actions. The job can be configured to use the following methods: GET, HEAD, POST, PUT and DELETE. The methods POST and PUT allow sending additional JSON or custom body content.

Task Configuration

  • URL: The address to call. It can contain placeholders as well.
  • Method: The HTTP method to use for the request.
  • Body Content to send: For methods PUT and POST you can define additional text content to be sent with the request.
  • 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
  • Custom Body Content: A text area with optional Body Content to be sent with a request when using POST or PUT methods
  • Headers: Optional headers to be sent with the request

Conditions

Task configuration allows a condition to be added to check the response status code of the job. Subsequent actions can be set up to run only if the condition is met. The following syntax is allowed for the response status code:

  • 200, 201, 202: check for one or more explicit status codes. The condition is true if one of the codes is returned.
  • 200-299: checks for a range of status codes. The condition is true if one of the codes in the range is returned.
  • !200, !201, !202: check if one or more codes are not returned by the request. The condition is true if the request does not return any of the given status codes.
  • !200-299: check for a range of status codes that must not be returned by the request. The condition is true if the request returns none of the status codes in the range.

Note: You can mix and match the syntax, e.g. 400-410, !401, !405-407.