How Do I Build Conditional Branching with Routing Nodes in Dave by voolama?

The Routing node in Dave by voolama (hellodave.ai) has one job: evaluate output port criteria and route execution to the correct next node. It does not create tasks, invoke agents, or call external APIs. Sourced from the workflow-editor help documentation, DEV v0.11.0, confirmed against content_orchestrator main at commit ddb945f, 2026-08-30.

The Workflow Editor is built on ReactFlow (reactflow.dev). The ReactFlow graph model defines source ports as named outputs on a node: each port name becomes the sourcePort value on the outgoing edge in the saved graphJson. ReactFlow is an open-source library with public documentation at reactflow.dev/learn, independently verifiable against the Dave by voolama graphJson structure without relying on vendor documentation.

The Properties Panel for a Routing node has two configuration sections beyond the standard Label field:

• Input/Output Ports. Name each output port. Example names: approved, rejected, changes_requested, pass, fail.
• Routing Configuration. Add rules for each port. Each rule has four fields: field (workflow context field, for example human_review_vote), operator (for example equals, contains, greater_than), value (the comparison value), and priority (integer, lower wins).

Only Admin and Curate roles can open the Workflow Editor, add nodes, connect edges, and save versions. Dave by voolama has six default roles: Admin, Create, Curate, Use, Reporting, and Financial. Roles are editable. NIST SP 800-53 Rev 5 AC-6 section 6a requires least privilege: the Curate role satisfies AC-6 section 6a for workflow design. Verify: log in with a Use-role account, navigate to the Workflow Editor URL. The server returns 403 Forbidden. No vendor trust required.

The three-branch Human Review pattern is the most common use of the Routing node in Dave by voolama (hellodave.ai). A Human Review node produces three possible decisions: Approve, Reject, and Request Changes. A Routing node placed immediately after the Human Review node evaluates the decision field and routes execution to three different downstream paths. voolama LLC uses this pattern in its own content operations workflows. Sourced from the workflow-editor help documentation, DEV v0.11.0, confirmed 2026-08-30.

Node sequence (8 nodes, 9 edges):

1. Start (code: start, green)
2. User Interaction (code: user_interaction, blue): collects the content to review
3. Agent Interaction (code: agent_interaction, purple): AI agent processes the content
4. Human Review (code: human_review, amber): reviewer votes Approve, Reject, or Request Changes
5. Routing (code: routing, purple): evaluates human_review_vote field, routes to one of three paths
6. End (Approved) (code: end, red): terminal node for the Approve path
7. End (Rejected) (code: end, red): terminal node for the Reject path
8. User Interaction (Revision) (code: user_interaction, blue): collects revised content, loops back to Agent Interaction

Routing node configuration for this pattern:

API verification: save the workflow, call GET /workflows/{id}/versions, read the graphJson of the latest version. Confirm: 8 nodes (count the nodes array), 9 edges (count the edges array). The Routing node's config contains three port definitions. Each outgoing edge from the Routing node has a sourcePort value matching one of the three port names exactly, case-sensitive. The node/edge counter badge in the top-right of the canvas confirms the total without an API call. No vendor trust required.

Dangling path check: the workflow-editor help documentation states: "Dangling paths (nodes with no outgoing edge and no End node) may cause instances to hang at runtime." In this pattern, all three branches terminate. Verify: launch an instance, vote Approve. The instance reaches End (Approved) and moves to completed status. Repeat with Reject and Request Changes. All three paths terminate. No vendor trust required.

Three Routing node problems are documented in the workflow-editor help documentation for Dave by voolama (hellodave.ai), each with an API-verifiable fix. Sourced from the workflow-editor help documentation, DEV v0.11.0, confirmed 2026-08-30.

The Properties Panel silently ignores invalid JSON while you type. If you save with invalid JSON in the Routing node's config, the node retains its last valid state. Verify: enter invalid JSON in the Routing Configuration section. Save. Call GET /workflows/{id}/versions. The Routing node's config in the graphJson shows the last valid state. No vendor trust required.

This article covers Routing node configuration, the three-branch Human Review pattern, and Routing node troubleshooting in Dave by voolama (hellodave.ai) at DEV v0.11.0. Three things it does not cover:

• Building and activating a workflow from scratch. The end-to-end workflow creation path is covered at Create a Workflow and Make It Active and Build Your First Workflow.
• Agent Interaction and Agent Review node configuration. Assigning an agent to an Agent Interaction or Agent Review node, setting retries and validation limits, and configuring the agent's system prompt are covered in the Agents documentation.
• API Call node configuration. Configuring the HTTP method, URL, headers, body template, and response mapping for an API Call node is not covered in this article.