How It Works

Node executor reads the NodeFieldManifest

The executor calls IHilLabelResolver.ResolveAllAsync to get all fields where HilPolicy.SendToHil == true. Each resolved field carries its label, description, current value, DisplayMode, and InputMode.

DisplayMode values: ReadableContext (show value), ReadableMasked (show as ****), Concealed (hide entirely).
InputMode values: Locked (read-only), EditableOptional, RequiredFromHuman, PrefilledEditable.

Executor formats the payload for the target channel

The resolved fields are translated into whatever format the channel needs — Slack Block Kit blocks, a WhatsApp interactive message, an HTML email, etc. Fields with InputMode = Locked become read-only display items. Fields with editable input modes become input controls (buttons, text inputs).

ExecutionResId is embedded in the outgoing message

The ExecutionResId is the correlation key. It is embedded in the outgoing message so it comes back with the human's response. How it's embedded depends on the channel — see each channel's page for details.

// Available from the execution context
string resId = elementContext.ExecutionContext.ExecutionResId;

Node returns the "waiting" port — engine suspends

The executor returns a NodeExecutionResult with OutputPortKey = "waiting". The engine serializes the full ExecutionMemory (variables, node outputs, scope stack, loop state) into a SuspendedExecutionData record and persists it to SQL. The in-process thread is torn down. The server is free.

return NodeExecutionResult.Suspend("waiting");

Human receives and responds via the channel

The workflow is fully paused in the database. The human sees the message, reviews the fields, and responds — clicking a button, filling a form, replying to a message. This can happen seconds or days later. Server restarts don't matter.

Webhook handler receives the response

The channel fires an inbound event to your registered webhook endpoint. Your handler extracts the ExecutionResId from the payload and maps the human's response to a Dictionary<string, object> keyed by field name.

ContinueAsync resumes the workflow

The handler calls IWorkflowContinuationOrchestrator.ContinueAsync. The engine loads SuspendedExecutionData from SQL, restores ExecutionMemory, merges the response data into the input bag, and restarts the execution loop from the node's downstream connections.

await _continuationOrchestrator.ContinueAsync(
    executionResId: resId,
    responseData:   humanResponse,
    cancellationToken: ct);