update_flow

Modify existing flow properties, configuration, or organization.

Purpose: Update flow metadata (name, description), modify flow structure (nodes, edges, components), or reorganize flows into different folders. Essential for maintaining flows, fixing configurations, renaming workflows, and managing project organization over time.

Parameters:

• flow_id (required, UUID string): Unique identifier of flow to update (from list_flows or get_flow)

• name (optional, string, max: 255 chars): New display name for the flow

• description (optional, string): Updated purpose and functionality description

• data (optional, object): New flow structure with nodes, edges, and component configurations

• folder_id (optional, UUID string): Move flow to different folder (use list_folders for valid IDs, null for root level)

Returns: FlowRead object containing:

• id (UUID): Flow's unique identifier (unchanged)

• name (string): Updated flow name

• description (string): Updated description

• folder_id (UUID): New folder location

• user_id (UUID): Owner identifier

• created_at (ISO timestamp): Original creation time (unchanged)

• updated_at (ISO timestamp): Timestamp of this update

• data (object): Complete updated flow structure

Usage Examples:

1. Rename flow: { flow_id: "flow-uuid", name: "Improved Customer Bot" }

2. Update description: { flow_id: "flow-uuid", description: "Processes customer inquiries with sentiment analysis" }

3. Move to folder: { flow_id: "flow-uuid", folder_id: "folder-uuid" }

4. Move to root: { flow_id: "flow-uuid", folder_id: null }

5. Update structure: { flow_id: "flow-uuid", data: { nodes: [...], edges: [...] } }

6. Rename and move: { flow_id: "flow-uuid", name: "New Name", folder_id: "folder-uuid" }

Best Practices:

• Get current flow data with get_flow before updating to avoid overwriting changes

• Only specify fields you want to change (partial updates supported)

• Rebuild flow with build_flow after data modifications to validate changes

• Use descriptive names and descriptions for team collaboration

• Update description when flow functionality changes significantly

• Move flows to appropriate folders to maintain organization

• Verify folder_id exists before moving (use list_folders)

• Update flow name if purpose or functionality changes

Common Errors:

• "Flow not found": flow_id doesn't exist or was deleted (verify with list_flows)

• "Flow name already exists": Choose unique name within target folder

• "Invalid folder ID": folder_id is not valid UUID (use list_folders to get valid IDs)

• "Folder not found": Specified folder_id doesn't exist

• "Invalid flow data structure": data object doesn't match Langflow schema

• "Concurrent modification": Flow was updated by another user (re-fetch with get_flow)

• "flow_id is required": Must provide flow_id parameter

• "Unauthorized": API key lacks permission to modify this flow

Related Tools:

• get_flow: Retrieve current flow state before updating

• build_flow: Validate flow after data modifications

• list_flows: Find flow_id for flows to update

• list_folders: Get valid folder_id values for reorganization

• create_flow: Create new flow instead of modifying existing one