Verification Router component (AI Flowi Workflow)
Verification Router sends a complete verification result to Verified or Rejected without removing or changing fields. Place it after the step that produces that result and before the accepted and rejected paths.
Verification Router is documented in the 1.9.2 catalogue and used in the production-tested webhook input validator linked below; that evidence covers the configured template.
By Ai Flowi · Published
Where Verification Router fits
The catalogue exported 9 October 2026 requires one input: verification_result. Its description promises preservation of the supplied fields. It does not expose comparison, normalization or HTTP-response settings on this node. Keep the upstream verification rules and the downstream response configuration visible in your flow.
Inputs
Verification Router input names, types and required flags below come from the component catalogue. For Verification 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 Verification Router table sideways to read every column.
| Name | Type | Required | Accepted input types | Plain explanation |
|---|---|---|---|---|
verification_result | other | Yes | Data, JSON | Required complete verification result, connected as Data or JSON. The export does not publish a standalone payload schema. |
Outputs
The two JSON outputs are verified (Verified) and rejected (Rejected). The complete result is routed without field removal or changes, as documented by the catalogue. A destination must accept JSON and must still have its own action or response settings.
| Name | Display name | Type |
|---|---|---|
verified | Verified | JSON |
rejected | Rejected | JSON |
When to use Verification Router
Use this router when upstream logic prepares a verification result and you need two destinations while retaining the result fields. JSON Operations operates on the JSON before routing; Condition instead exposes a key name, operator and comparison value.
When not to use Verification Router
For message-text comparison, choose If-Else and its Message outputs. For webhook traffic separated by GET, POST, PUT, PATCH or DELETE, HTTP Method Router documents a method-specific JSON interface. Verification Router’s two output names alone do not configure either of those tasks.
Tested template using Verification Router
The webhook input validator template documents production tests on 9 October 2026 with AI Flowi Workflow 1.9.2: 28 of 28 cases passed. Its recorded result is:
The production run returned a 200 normalized echo or a 422 response with reasons.
In that template, JSON Operations data_output connects to verification_result and routing uses a top-level boolean verified. The router’s verified output connects to the 200 response’s body_data; rejected connects to the 422 response’s body_data. These are the template’s documented connections, not an independently tested configuration from this page.
Limitations
- The recorded result belongs to the webhook input validator, including its upstream JQ rules and downstream Webhook Response nodes. It does not establish success for every payload connected to verification_result.
- The linked template records production requests, but not an imported-copy verification or observed node billing. Its 200 response confirms validation only, with no persistence node in that workflow.
- The catalogue does not define how an absent or malformed verification flag is handled. Use the tested template contract as a scoped reference and check changes before attaching a business action.
Related components
JSON Operations · Condition · If-Else · HTTP Method Router
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.
The linked validator reports design estimates rather than measured billing; third-party API/model usage is not included in the plan if you add those calls to a verification branch. Review pricing for Verification Router.