Skip to main content
Visual workflow builder allows you to create, connect, and manage agentic processes using a drag-and-drop interface.
The [flow] extra is opt-in and heavy (~500MB) because Langflow pulls many dependencies. Install only when you need the visual builder: pip install "praisonai[flow]".

Quick Start

1

Install Flow Addon

Install the visual builder components.
pip install "praisonai[flow]"
2

Launch Visual Builder

Start the local server and open the web interface.
praisonai flow
3

Connect Components

Open http://localhost:7860 to access the interface. Drag and drop Agent and Agent Team nodes to orchestrate workflows.

CLI Subcommands

CommandPurpose
praisonai flowLaunch Langflow with PraisonAI components
praisonai flow import <yaml>Convert PraisonAI YAML → Langflow JSON and upload
praisonai flow export <flow_id>Download a Langflow flow and convert back to YAML
praisonai flow listList flows on a running Langflow server
praisonai flow versionShow installed Langflow version
See Flow CLI for the full flag reference.

Which subcommand should I use?


Start Command Flags

FlagTypeDefaultDescription
--port, -pint7860Port to listen on
--host, -Hstr127.0.0.1Host to bind to (use 0.0.0.0 to expose)
--env-filestrNonePath to a .env file Langflow should load
--no-openflagFalseDon’t open the browser on start
--log-level, -lstrerrordebug, info, warning, error, critical
--backend-onlyflagFalseRun backend API only (no frontend UI)
--components-pathstrNoneExtra custom components directory (appended to PraisonAI’s)

Import flags

FlagTypeDefaultDescription
yaml_pathstrPath to YAML workflow file (positional)
--urlstrhttp://localhost:7860Langflow server URL
--dry-runflagFalsePreview JSON without uploading
--openflagFalseOpen the imported flow in the browser
--output, -ostrNoneSave JSON to file instead of uploading

Export flags

FlagTypeDefaultDescription
flow_idstrFlow ID to export (positional)
--output, -ostr<flow_name>.<ext>Output file path
--urlstrhttp://localhost:7860Langflow server URL
--formatstryamlOutput format: yaml or json

List flags

FlagTypeDefaultDescription
--urlstrhttp://localhost:7860Langflow server URL
--search, -sstrNoneSearch flows by name or description

How It Works

ComponentPurposeAvailability
Agent NodeIndividual AI entity with tailored instructionsSidebar > PraisonAI
Agent Team NodeMulti-agent orchestrator connecting multiple nodesSidebar > PraisonAI
CLI CommandBackend server runtime wrapperpraisonai CLI
If PRAISONAI_OBSERVE=langfuse is set, the Agent component auto-wires a LangfuseSink with praisonai_source=langflow trace metadata.

Agent Configuration Options

Options available on the Agent node visual component.
OptionTypeDefaultDescription
Agent Namestr"Agent"Name for identification and logging
Previous AgentHandleNoneConnect from previous agent to define execution order
RolestrNoneRole defining the agent’s expertise
GoalstrNonePrimary objective the agent aims to achieve
Backstorystr (multiline)NoneBackground context shaping personality
Instructionsstr"You are a helpful assistant."System prompt for the agent
InputHandleNoneUser input to process
Modelstr"openai/gpt-4o-mini"LLM model (provider/model format)
Language ModelHandle (LanguageModel)NoneExternal LLM from Langflow model components (overrides dropdown)
Base URLstrNoneCustom LLM endpoint (e.g. http://localhost:11434 for Ollama)
API KeySecretNoneAPI key for LLM provider (overrides env var)
ToolsHandleNoneTools available to the agent
Allow DelegationboolFalseAllow task delegation to other agents
Allow Code ExecutionboolFalseEnable code execution during tasks
Code Execution Modestrsafesafe (sandboxed) or unsafe (full system access)
HandoffsHandle[Agent][]Other agents this agent can hand off conversations to
MemoryboolFalseEnable context retention
Memory Providerstr"""", rag, or mem0
Memory ConfigdictNoneFull MemoryConfig dictionary
Knowledge FilesFileNoneFiles to use as knowledge sources (PDF, TXT, etc.)
Knowledge URLsstr (multiline)NoneURLs to use as knowledge sources (one per line)
GuardrailsboolFalseEnable output validation guardrails
VerboseboolFalseShow detailed execution logs
Markdown OutputboolTrueFormat output as markdown
Self ReflectboolFalseEnable self-reflection
Max Iterationsint20Maximum agent loop iterations

Agent Team Configuration Options

Options available on the Agent Team node visual component for multi-agent workflows.
OptionTypeDefaultDescription
Namestr"AgentTeam"Name for this multi-agent team
AgentsHandle[]List of connected PraisonAI agents to orchestrate
InputHandleNoneInitial input to start the multi-agent workflow
Processstr"sequential"Collaboration mode (sequential, hierarchical, workflow)
Manager AgentHandle[Agent]NoneExplicit manager agent for hierarchical process
Manager LLMstr"openai/gpt-4o"LLM used for auto-created managers
VariablesdictNoneGlobal variables for substitution in task descriptions
Shared MemoryboolFalseEnable shared memory across all agents
GuardrailsboolFalseEnable team-level validation guardrails
VerboseboolFalseShow detailed execution logs
Full OutputboolFalseReturn full output including all task results
PlanningboolFalseEnable planning mode for task decomposition
ReflectionboolFalseEnable self-reflection for improved results
CachingboolFalseEnable caching of agent responses

Common Patterns

YAML round-trip

praisonai flow                                   # 1. start the builder
praisonai flow import my_workflow.yaml --open    # 2. push YAML in
# (edit in browser, copy the flow ID from the URL)
praisonai flow export <flow_id> -o my_workflow.yaml   # 3. pull edits back to YAML

Sequential Connections

Connect individual Agent nodes linearly (Agent 1 → Agent 2) by linking the Agent output handle on the first node to the Previous Agent input handle on the second node.

Multi-Agent Orchestration

Connect multiple Agent nodes directly to the Agents input handle of an Agent Team node. The team node evaluates the topology and runs the sub-agents properly.

Headless / LAN deploy

praisonai flow --host 0.0.0.0 --port 8080
praisonai flow --backend-only --no-open

Best Practices

When using the agent node’s knowledge capabilities, upload compatible document types (PDF, TXT, CSV) or provide valid URLs in the Knowledge inputs.
Use the Previous Agent connection to establish hard execution boundaries. The orchestrator automatically parses node inputs backwards to map deterministic execution flow.
Click the “Advanced” toggle on nodes inside Langflow to expose robust SDK parameters like custom Base URLs, Code Execution Mode, Verbose logging, and specific Memory Providers.
Export flows back to YAML after visual edits so workflows stay in version control.

Flow CLI

CLI reference for all subcommands and flags

Langflow Integration

Component reference and model formats

Agent Workflow

Core workflow concepts

Installation Extras

[flow] extra reference