|D s ed|
In Plan View, you can create HTTP tasks to send request to endpoints before or after the execution of other tasks. These tasks are specified in the right context panel.
Tip: To rename the task, click the task name.
|Method||Select the HTTP method to use to deliver the message. The appropriate method depends on the receiving application. Most use cases require the |
|URL||URL where the HTTP request is received by the other application.|
Insert HTTP content headers as key-value pairs. For example, if your body is in JSON format, you should include the following header:
For examples of requests including metadata examples, see Create HTTP Task.
(Optional) A secret key can be used to verify the request payload. This secret value must be inserted in this location, and it must be included as part of the code used to process the requests in the receiving application. Insert the secret value here as a string without quotes.
For more information on how this secret key is used to generate a signature, See Create HTTP Task .
|Validate SSL Certificate|
When set to
If the returned status code is outside of the 200-299 range, then the HTTP task is considered to have failed. When this option is enabled, the request is retried.
If the request fails, this value defined the number of times that the request should be retried. If this number of retries is reached without success, the task fails.
To test if the specified endpoint is reachable, click Test.
Tip: A status code of
200indicates that the test was successful.
Tip: You can use the GET method for testing purposes. A GET request does not change any data on the target platform but may permit you to specify elements in the request body.
Edit task name: Change the name of the task.
Tip: Good naming may include the target platform endpoint and method, as well as the purposes of the task in your plan.
Delete: Delete the task.
This step cannot be undone.
For more information, see Create HTTP Task.