Conditional Branching And Dynamic Workflow Routing Based On Llm Output

via “conditional branching and loop constructs in workflows”

Hey HN, we're Jon and Kristiane, and we're building Orloj (https://orloj.dev), an open-source orchestration runtime for multi-agent AI systems. You define agents, tools, policies, and workflows in declarative YAML manifests, and Orloj handles scheduling, execution, governance, an

Unique: Provides declarative control flow primitives in YAML that avoid imperative code while supporting complex agent decision-making patterns

vs others: More readable than imperative Python chains for simple conditionals; less powerful than full programming languages but sufficient for most agent workflows

via “conditional branching with dynamic path selection”

A durable workflow execution engine for Elixir

Unique: Treats branching as a first-class workflow construct with full persistence and observability, rather than as imperative if/else logic in step functions. Each branch is a separate sub-graph with independent step execution history, enabling fine-grained control flow analysis and debugging.

vs others: More declarative than embedding conditionals in step logic and simpler than Temporal's workflow versioning for conditional behavior. Branch selection is queryable and auditable via database records.

via “dynamic llm routing based on context”

MCP server: auto_llm_routing

Unique: Employs a decision tree-based routing mechanism that evaluates multiple context parameters for optimal LLM selection, unlike simpler static routing methods.

vs others: More adaptive than static routing solutions, enabling real-time adjustments based on user input and context.

via “dynamic api orchestration for llm workflows”

MCP server: testp

Unique: The dynamic routing mechanism allows for real-time adjustments to API calls based on user-defined conditions.

vs others: More flexible than static workflow engines, which require predefined paths and cannot adapt to real-time changes.

via “conditional rendering and branching logic in workflows”

[Twitter](https://twitter.com/fixieai)

Unique: Expresses workflow branching as JSX conditional rendering, allowing complex decision trees to be built using familiar React patterns (if/else, ternary operators) rather than explicit state machine or graph-based workflow definitions

vs others: Provides a more intuitive, code-based approach to workflow branching compared to visual workflow builders, while remaining more readable than imperative control flow in traditional LLM frameworks

via “conditional workflow branching and decision logic”

Automate technical business workflows

Unique: unknown — insufficient data on whether Manaflow supports visual condition builders, expression languages (e.g., JSONPath, CEL), or advanced pattern matching

vs others: Conditional logic is standard in workflow platforms; differentiation depends on expressiveness and ease of use which are not documented

via “conditional logic and branching with llm-based decision routing”

Build your AI Workforce

via “conditional-logic-routing”

via “conditional-branching-and-routing”

via “conditional-prompt-branching”

via “conditional branching and decision logic with llm-powered evaluation”

Unique: Supports both rule-based and LLM-evaluated conditions, allowing workflows to make intelligent decisions based on unstructured data (sentiment analysis, classification, reasoning) without requiring users to write conditional logic code or train custom models

vs others: More flexible than Zapier's conditional branching because it supports LLM-powered evaluation of unstructured data, though it introduces non-determinism and latency compared to deterministic rule-based branching

via “conditional-logic-branching”

via “conditional-logic-routing”

via “conditional-logic-and-branching”

via “conditional-logic-execution”

via “conditional-logic-and-branching”

via “conditional workflow logic execution”

via “conditional-logic-branching”

via “conditional workflow branching”