HTTP Server Trigger
The HTTP Server trigger starts a server on a given port and listens for the request on the configured context path. Each request received triggers a new flow instance.
Trigger Settings
| Field | Required | Description |
|---|---|---|
| Trigger Settings | ||
| Port | Yes |
The port on which the trigger listens for requests. Default: 9173 You can change this to use another port that is open. |
| Processing Mode | Yes |
Proxy In this mode, request/response is opaquely passed to/from the trigger. So, request/response payload, request/response headers, path parameters, invocation method, and so on, are not accessible inside the flow. This mode must be used along with HTTP Client activity for pass through proxy implementation. In case context path is set, context path is omitted from the request when request is passed to the HTTP Client. Data Data mode gives the user flexibility to configure request/response headers, params, body and do orchestration on the input data. Return/ReplyToTrigger activity must be configured to send back the response received from the HTTP Client activity. |
| Handler Settings | ||
| Context Path | No |
For Proxy mode: Optional context path for the request. The default is set to For Data mode: Context path trigger is required and works as a route for the incoming request. Note: Strict path matching is done including the pathParams of the incoming request.
|
|
Method Note: Applicable only for Data mode.
|
Supported HTTP methods are: GET, PUT, POST, DELETE, and PATCH. | |
Map to Flow Inputs
In this tab, the mapping of trigger output is automatically done with the flow input when HTTP Server trigger is added.
Map to Flow Outputs
In this tab, user can map the flow outputs to the trigger reply.