Workflow Nodes - hConnect

By default a workflow is a straight line: request → verification → response. Insert nodes between the verification and the response to add rules. For the basics, see Workflows.

Node	Purpose	Key `config`
`request`	Entry point	(none)
`verification`	Runs the verification. Holds the channel, claims, enabled connections, credential-specific claims, and branding	`channel`, `claims`, `credentials`, `credential_claims`, `branding`
`check-min-loa`	Checks a minimum level of assurance	`minLoa` (1 to 5)
`check-claim`	Checks that specific claims are present	`claimChecks`
`evaluate`	Stores a boolean result under `computed.<field>`	`outputField`, `conditions`
`if`	Branches on conditions	routes via `next`
`response`	Terminal node	(none)

Conditions

Conditions use dot notation over the verification output, for example input.user.nationality or input.hopae_loa.

Outputs

Node results are added to the userinfo response: metLoa from check-min-loa, hasClaim from check-claim, and computed.* from evaluate. Nodes only report results. Your integration enforces them. For example, read metLoa and reject the user in your own system when it is false.

Channel

The verification node has a channel: oidc for the hosted flow or api for the REST API. Both use the same connections and data request. The workflow-level type (managed or api) only records intent and does not change how it runs.