Skip to main content
Glama

create_flow

Create a new Langflow workflow. Initialize a flow with optional configuration, description, and folder organization.

Instructions

Create a new Langflow workflow with optional configuration and organization.

Purpose: Initialize a new flow in your Langflow instance. Use this to create workflows from scratch or with predefined structure. The flow can be organized into folders and configured with initial data including nodes, edges, and component settings.

Parameters:

  • name (required, string, max: 255 chars): The display name of the flow (must be unique within folder)

  • description (optional, string): Brief explanation of flow's purpose and functionality

  • data (optional, object): Initial flow configuration containing nodes, edges, and component definitions

  • folder_id (optional, UUID string): ID of parent folder for organization (use list_folders to get valid IDs)

Returns: FlowRead object containing:

  • id (UUID): Newly created flow's unique identifier (save this for future operations)

  • name (string): Flow display name

  • description (string): Flow description

  • folder_id (UUID): Parent folder if specified

  • user_id (UUID): Owner user identifier

  • created_at, updated_at (ISO timestamps): Creation and modification timestamps

  • data (object): Complete flow structure with nodes and edges

Usage Examples:

  1. Create minimal flow: { name: "My Workflow" }

  2. Flow with description: { name: "Data Pipeline", description: "Processes user data" }

  3. Flow in folder: { name: "API Flow", folder_id: "folder-uuid-here" }

  4. Flow with structure: { name: "Chat Bot", data: { nodes: [...], edges: [...] } }

Best Practices:

  • Use descriptive names that indicate flow purpose (e.g., "Customer Onboarding" not "Flow1")

  • Add descriptions to document flow functionality for team collaboration

  • Organize related flows using folder_id for better project management

  • Start with minimal configuration, then use update_flow to add complexity

  • Validate data structure before passing complex flow configurations

Common Errors:

  • "Flow name already exists": Choose a unique name or specify different folder_id

  • "Invalid folder ID": Ensure folder_id is valid UUID from list_folders

  • "Name is required": Must provide name parameter

  • "Data validation failed": Check that data object follows Langflow schema structure

  • "Unauthorized": Verify LANGFLOW_API_KEY is valid

Related Tools:

  • list_flows: View all created flows

  • update_flow: Modify flow after creation

  • get_flow: Retrieve full flow details by ID

  • upload_flow: Import flow from JSON file instead of creating from scratch

  • create_folder: Create folders before organizing flows

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoOptional flow data/configuration
nameYesThe name of the flow
folder_idNoOptional folder ID to organize the flow
descriptionNoOptional description of the flow
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It discloses creation behavior, return object details, and common error scenarios (e.g., name exists, invalid folder, validation failure, unauthorized). However, it does not explicitly mention idempotency (likely not idempotent) or potential side effects beyond creation. Still, covers key behavioral traits well.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is long but well-structured with clear sections: summary, parameters, returns, usage examples, best practices, common errors, related tools. Front-loaded with purpose. Could trim some redundant examples (e.g., example 1 and 2 are minimal variations), but overall earns its length through comprehensive guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool is complex with 4 parameters, nested objects, and many sibling tools. Description covers all aspects: what it does, parameter details including constraints, return object fields (saving the ID for future operations), usage examples, best practices, common errors, and related tools. With no output schema, the detailed return field descriptions are essential and well provided.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds significant value: explains name must be unique within folder and max 255 chars, data object contains nodes/edges/component definitions, folder_id must be a valid UUID from list_folders. Includes four concrete usage examples showing different parameter combinations, clarifying how to use each parameter effectively.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Create a new Langflow workflow with optional configuration and organization.' It specifies the verb 'create', the resource 'Langflow workflow', and distinguishes from siblings like upload_flow (import from JSON) and update_flow (modify after creation). Detailed parameter descriptions and usage examples reinforce purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use ('Initialize a new flow') and provides best practices like using descriptive names, adding descriptions, organizing with folder_id, starting minimal then using update_flow. Related tools section lists alternatives: list_flows, update_flow, upload_flow, create_folder. Common errors section further guides correct usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nobrainer-tech/langflow-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server