Dynamiq Docs
  • Welcome to Dynamiq
  • Low-Code Builder
    • Chat
    • Basics
    • Connecting Nodes
    • Conditional Nodes and Multiple Outputs
    • Input and Output Transformers
    • Error Handling and Retries
    • LLM Nodes
    • Validator Nodes
    • RAG Nodes
      • Indexing Workflow
        • Pre-processing Nodes
        • Document Splitting
        • Document Embedders
        • Document Writers
      • Inference RAG workflow
        • Text embedders
        • Document retrievers
          • Complex retrievers
        • LLM Answer Generators
    • LLM Agents
      • Basics
      • Guide to Implementing LLM Agents: ReAct and Simple Agents
      • Guide to Agent Orchestration: Linear and Adaptive Orchestrators
      • Guide to Advanced Agent Orchestration: Graph Orchestrator
    • Audio and voice
    • Tools and External Integrations
    • Python Code in Workflows
    • Memory
    • Guardrails
  • Deployments
    • Workflows
      • Tracing Workflow Execution
    • LLMs
      • Fine-tuned Adapters
      • Supported Models
    • Vector Databases
  • Prompts
    • Prompt Playground
  • Connections
  • LLM Fine-tuning
    • Basics
    • Using Adapters
    • Preparing Data
    • Supported Models
    • Parameters Guide
  • Knowledge Bases
  • Evaluations
    • Metrics
      • LLM-as-a-Judge
      • Predefined metrics
        • Faithfulness
        • Context Precision
        • Context Recall
        • Factual Correctness
        • Answer Correctness
      • Python Code Metrics
    • Datasets
    • Evaluation Runs
    • Examples
      • Build Accurate vs. Inaccurate Workflows
  • Examples
    • Building a Search Assistant
      • Approach 1: Single Agent with a Defined Role
      • Approach 2: Adaptive Orchestrator with Multiple Agents
      • Approach 3: Custom Logic Pipeline with a Straightforward Workflow
    • Building a Code Assistant
  • Platform Settings
    • Access Keys
    • Organizations
    • Settings
    • Billing
  • On-premise Deployment
    • AWS
    • IBM
  • Support Center
Powered by GitBook
On this page
  • Node
  • Input and Output Nodes
  • Connecting Nodes within a Single Workflow
  1. Low-Code Builder

Connecting Nodes

PreviousBasicsNextConditional Nodes and Multiple Outputs

Last updated 6 months ago

Node

A Node functions as an abstract component within a workflow architecture. Nodes can serve various purposes, such as data preprocessing, managing LLM Agents, tools, and supporting retrieval-augmented generation. Nodes can be interconnected to form directed acyclic graph workflows, allowing development of applications of any complexity.

Input and Output Nodes

A Workflow begins with Input Node and finishes with Output Node. Both nodes will be automatically added to each new workflow.

Each node has its own set of inputs and outputs, which vary based on its functionality. An Input Node has two default parameters: input for text input, and files for file input.

  • Input: For text input

  • Files: For file input

Connecting Nodes within a Single Workflow

Clicking on either the input or the output nodes will bring up their configuration options. Any parameter can be added to both nodes.

Nodes can be connected in a single workflow to create a sequence of operations. This is done by simply connecting the output of one node to the input parameter of another node.

Without specifying the input transformer, this implementation will not function as expected. However, if we use the same instructions in the input transformer as in the previous example, both implementations will be equivalent.

By doing this, the necessary code to correctly pass the input data to the input transformer is generated automatically. For more information about the input and output transformers, please refer to the following .

Alternatively, we can connect nodes directly without linking their parameters. This approach allows all parameters to be passed at once, offering flexibility to define custom logic within the input transformer, which is empty by default. This method is also used by the Choice Node, enabling conditional branching based on . It also allows for the creation of a workflow structure, outlining the sequence of nodes without requiring data to be passed between them.

link
specific criteria
Input and output nodes
Adding parameters to the Input Node
Example of a simple Workflow with parameter connections
Example of a simple Workflow with directly connected nodes