HTTP Method Router component (AI Flowi Workflow)
HTTP Method Router routes complete webhook Request Data to GET, POST, PUT, PATCH or DELETE without removing any request fields. Put it after the webhook request source and before the separate method-specific paths.
HTTP Method Router is documented in the catalogue; not production-tested by Ai Flowi.
By Ai Flowi · Published
Where HTTP Method Router fits
In the 1.9.2 catalogue exported 9 October 2026, request_data is the only input and is required. Supply the complete request data, rather than replacing it with the body alone. The router description covers keeping request fields; it does not document a request-envelope schema to construct by hand.
Inputs
HTTP Method Router input names, types and required flags below come from the component catalogue. For HTTP Method Router, “Not listed in export” means no accepted-connection list was supplied; it is not a claim that every type is supported.
On small screens, scroll either HTTP Method Router table sideways to read every column.
| Name | Type | Required | Accepted input types | Plain explanation |
|---|---|---|---|---|
request_data | other | Yes | Data, JSON | Required complete webhook Request Data connection, accepting Data or JSON. Keep the request envelope from your source intact. |
Outputs
There are five JSON ports: get (GET), post (POST), put (PUT), patch (PATCH), and delete (DELETE). They provide separate destinations for the listed methods while preserving request fields. Check JSON compatibility and configure the receiving components for each path you connect.
| Name | Display name | Type |
|---|---|---|
get | GET | JSON |
post | POST | JSON |
put | PUT | JSON |
patch | PATCH | JSON |
delete | DELETE | JSON |
When to use HTTP Method Router
Use this component when one incoming webhook flow needs different downstream paths for the five documented methods. The method is the routing criterion; retaining the complete request matters when later steps need more than the body. See the Universal Webhook guide for the request source.
When not to use HTTP Method Router
If the decision depends on a value inside your JSON, consider Condition. If the upstream step has already created a verification result, consider Verification Router. API Request makes an outbound HTTP request using a URL or cURL command; it serves a different stage from routing an incoming request.
example configuration, not a recorded test
request_data: [connect complete webhook Request Data]This single-input sketch shows the connection to configure. The bracketed text is not a literal JSON value or an importable workflow. Connect a selected method output to a JSON-compatible next step, then inspect synthetic requests before adding side effects.
Limitations
- Only GET, POST, PUT, PATCH and DELETE outputs are listed. The export does not specify a HEAD or OPTIONS path, a catch-all output, or the behaviour of an unsupported method.
- No input option for choosing a default route, setting authentication, validating a body or sending an HTTP response is exported. Configure those concerns in the appropriate surrounding steps.
- The request method field name, normalization rules and malformed-envelope behaviour are not published in this catalogue entry. A guessed JSON shape would not be a verified configuration.
- Preserving request fields is not a field-redaction policy. Before forwarding a request into another system, decide which fields that destination should receive.
Related components
Condition · Verification Router · If-Else · API Request
Node runs and usage
Plans: Go from USD8/month billed yearly (USD10 monthly), Plus from USD16 (USD20 monthly), Pro 100 from USD80 (USD100 monthly), Pro 200 from USD160 (USD200 monthly) and Pro 500 from USD400 (USD500 monthly), with 5,000 to 250,000 Flowi Tokens/month and top-ups; 1 token per node run; third-party API and model usage is not included.
Estimate the router run together with whichever method path your flow executes; outbound API calls or model calls on that path have third-party usage charges outside the Workflow plan. Review pricing for HTTP Method Router.