📌 This article is for users of elvex Classic. Find out which version you're using.

elvex flows support different node types, each designed for specific purposes within your workflow. This reference explains what each node type does, when to use it, and its key configuration options.

Basic Step

The foundation of elvex flows - a customizable LLM prompt with configurable tools and datasources.

When to use it: For most standard flow operations where you need the LLM to process information, generate content, or perform analysis.

Key configuration:

Instructions (required): Specific directions for what the step should accomplish
Provider and model: Use flow defaults or specify custom settings
Tools: Enable capabilities like web search, webpage content retrieval, spreadsheet analysis, or SQL queries
Datasources: Connect relevant knowledge bases or files
Result validation: "Manager" that checks output quality (enabled by default)

Ask an Agent

A node that leverages existing agents within your flow.

When to use it: When you want to incorporate specialized agents you've already built rather than recreating their functionality.

Typical uses: Incorporating domain-specific agents, content generation agents, or analysis agents into larger workflows.

Decision

A branching node that evaluates input and directs flow based on defined criteria.

When to use it: When your workflow needs to take different paths depending on specific conditions.

Key configuration:

Decision instructions (required): Criteria for making the decision
Options: Define two or more possible paths
Option criteria: Optional explanation for when each option should be chosen
No match option: Optional path for when none of the defined options apply

Call an existing Flow

A node that embeds another flow as a step within your current flow.

When to use it: When you want to create modular, reusable workflow components or break complex processes into manageable parts.

Key benefits:

Creates modular, reusable workflow components
Simplifies maintenance (update once, changes reflect everywhere)
Helps organize complex processes into logical components

Loop

A container node that processes multiple items through the same series of steps automatically.

When to use it: When you need to process lists, spreadsheets, or text data by running each item through the same workflow steps.

Key configuration

Splitting strategy: Comma, Rows, Sentences, or Paragraphs
Data source (optional): Specific file or data source to use as input
Maximum iterations (default: 20): Range 1-20

Two output modes

Loop output (standard): Bottom-right handle. Processes all items in parallel. Use for independent items.

Iteration output (feedback): Bottom-left handle (yellow). Processes items sequentially. Each iteration receives all previous results. Use for items that build upon previous results.