Skip to main content

Flow Node Types Reference

A concise guide to the four node types available in elvex flows

Updated over a week ago

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)

Testing: Use the Test tab to try the step with sample inputs and see outputs before running the full flow.

Ask an Assistant

A node that leverages existing assistants within your flow.

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

Key benefits:

  • Reuses existing assistants with their specialized configurations

  • Maintains consistent assistant behavior across different contexts

  • Avoids duplicating setup work

Typical uses: Incorporating domain-specific assistants, content generation assistants, or analysis assistants 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 (e.g., "Is this a sandwich?")

  • Options: Define two or more possible paths (e.g., "Yes" and "No")

  • Option criteria: Optional explanation for when each option should be chosen

  • No match option: Optional path for when none of the defined options apply

Example:

Instructions: "Determine if the text describes a food item" 
Option 1: "Yes" - When input describes something edible
Option 2: "No" - When input doesn't describe food

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

Considerations:

  • Be mindful of performance when nesting multiple flows

  • Understand dependency relationships between parent and child flows

  • Ensure proper testing of the complete flow structure


Combine these node types to create sophisticated workflows that handle complex business processes while maintaining clarity and reusability.

Did this answer your question?