The following example pipeline demonstrates the use of HTTP Router Snap to process an incoming POST request via a Triggered Task. This Pipeline contains the REQUEST_METHOD parameter configured with the value POST.

Triggered Task	Pipeline with HTTP Router Snap

Download this Pipeline

Pipeline Properties

When the Triggered Task - Task_On_HTTP_Router is run from the Task's details page, the corresponding pipeline is executed.

The HTTP Router is configured to route the incoming document to a corresponding output view, matching the Request method value with the REQUEST_METHOD Pipeline parameter.

HTTP Router Snap Settings	HTTP Router Snap Views

In this example, the HTTP Router uses this JSON document and the REQUEST_METHOD from the Triggered Task as inputs. Based on the incoming value for REQUEST_METHOD (POST in this example), the HTTP Router routes the document to the corresponding output view (output1 in the validated Pipeline above). The Pipeline execution continues further to finally write the formatted JSON output into a JSON file.