Skip to content

Edit a Flow

The Floogos visual editor allows you to modify any existing flow: add, move or delete nodes, change connections and adjust configurations.

  1. Go to the Flows section in the sidebar menu
  2. Click on the flow you want to edit
  3. The visual editor opens with all flow nodes

Inside the editor, click the folder icon (bottom-left) to open the workflow selector panel. This panel lets you switch between workflows without leaving the editor.

Folder organization: workflows are grouped by their assigned folder. Click a folder to expand or collapse it. The active workflow’s folder is automatically expanded on open.

Search: type in the search box to filter workflows. Folders that contain matching workflows expand automatically.

Pin mode: click the pin icon (📌) in the panel header to keep the panel open after selecting a workflow. When pinned, selecting a workflow navigates to it without closing the panel — useful when switching between related workflows frequently.

  • Drag a node from the left panel to the canvas
  • Or right-click on the canvas to see the node menu
  • Drag any node to reposition it on the canvas
  • Nodes maintain their connections when moved
  • Select the node and press Delete
  • Or right-click on the node and select Delete
  • To create: drag from a node’s output point to another node’s input point
  • To delete: click on the connection line and press Delete
  • To change: delete the existing one and create a new one
  1. Double-click on the node
  2. The configuration panel opens on the right

Node configuration panel open on the right: node name, its parameters with inline help, and the cancel and save buttons.

The configuration panel. The fields you see here are the ones listed in each node’s reference page. 3. Modify the necessary fields 4. Changes apply when you close the panel

When you select 2 or more nodes, a floating action bar appears right above the selection with everything you need to tidy them up.

  • Align: left · horizontal center · right · top · vertical center · bottom.
  • Distribute (with 3 or more nodes): horizontal or vertical, with equal spacing.
  • The same bar also includes Duplicate, Copy, Group and Delete.

In the canvas controls (bottom-left) the Auto-arrange button (tree icon) lays out the whole flow left-to-right automatically, respecting the connections. The AI agent sub-nodes (brain, tools, skills, RAG) are grouped below their agent; sticky notes and groups are left as they are. When done, the view re-fits.

  • Snap to grid: the grid button in the controls snaps node moves to a 16 px grid.
  • Alignment guides: with snapping off, dragging a node shows dashed guide lines and the node snaps to other nodes’ edges or centers (Figma style).

All these operations are visual only: they change node positions in the editor, not the workflow execution. They can be undone with Ctrl+Z.

When a node fails during execution, FlooIA can help you understand and resolve the problem:

  1. Double-click on the failed node
  2. Go to the Trace tab to see the error
  3. Click “Analyze with AI”
  4. FlooIA will show you:
    • Cause of the error
    • Detailed explanation of why it happened
    • Solution step by step
    • Fixed configuration (if applicable, with a button to apply directly)
    • Prevention tips to avoid the error in the future

Open FlooIA chat while editing to ask questions about the flow:

  1. Click the AI button in the toolbar and enable “Floo AI”
  2. A chat panel opens on the right
  3. FlooIA knows the context of your current flow (nodes, connections, errors)

Useful question examples:

QuestionWhat FlooIA answers
”Why is the Decision node failing?”Analyzes the condition and input data
”How can I filter only Portuguese orders?”Suggests Decision node configuration
”What node do I need to send an email?”Recommends Postmark, Email or SMTP for your case
”How do I save the result to a CSV?”Explains how to configure CSV Create

FlooIA can analyze your complete flow and suggest improvements:

  1. Open the AI menu in the toolbar
  2. FlooIA will review the flow structure
  3. It will indicate possible improvements: unnecessary nodes, missing error paths, performance optimizations

The editor lets you visually group related nodes inside a colored container with a title and optional description. Groups are purely visual — they do not affect workflow execution.

Option A — multi-selection bar:

  1. Select two or more nodes (Shift+Click or drag a region)
  2. Click Group in the action bar that appears above the selection
  3. A container wraps the selection automatically with 52 px padding on each side

Option B — context menu:

  1. Right-click on any selected node while two or more nodes are selected
  2. Choose Group selection
  • The container moves all child nodes together when you drag it
  • Child nodes cannot be dragged outside the group (they are contained)
  • Adding a node from the sidebar: drag it and drop it inside the group area — the node is automatically assigned to the group
  • Adding a node from a handle (+): when you connect from a node that already belongs to a group, the new node is placed inside the same group
ActionHow
RenameClick directly on the title text inside the container
Add descriptionClick on the description area below the title
Change colorSelect the group → click the color palette icon (top-right corner)
ResizeDrag any corner or edge of the container
UngroupRight-click the group → Ungroup, or click the trash icon while the group is selected

Renaming and the description are also available in the configuration panel on the right — double-click the group to open it.

Groups are excluded from the execution engine. The workflow_json sent to the engine contains only executable nodes; group containers are stripped automatically. Connections between nodes inside a group work exactly the same as connections between any other nodes.


The editor lets you copy one or more selected nodes and paste them into any other workflow — even in a different workflow tab in the same browser. The clipboard persists in localStorage until you copy something new.

ActionHow
Select one nodeClick on the node
Select multiple nodesShift + Click on each additional node
Select a regionDrag over an empty area of the canvas
Select allCtrl + A
DeselectClick on an empty canvas area
  1. Select one or more nodes
  2. Press Ctrl + C (or click the Copy button in the toolbar)
  3. A confirmation appears: “N node(s) copied”

What is saved to the clipboard:

  • The complete configuration of each node (type, label, all fields)
  • The internal connections between selected nodes (connections to non-selected nodes are discarded)
  1. Open the destination workflow (same or a different one)
  2. Press Ctrl + V
  3. Nodes are pasted offset by 40px from their original position, selected and ready to move
  4. Internal connections between the copied nodes are restored with new unique IDs

The clipboard persists across workflows: you can copy in one workflow, navigate to another, and paste. Pasted nodes get new IDs to avoid collisions with existing ones.

Duplicate nodes in the same workflow — Ctrl + D

Section titled “Duplicate nodes in the same workflow — Ctrl + D”

To duplicate without going through the clipboard:

  1. Select the nodes to duplicate
  2. Press Ctrl + D
  3. A copy is created immediately, offset on the same canvas
ShortcutAction
Ctrl + CCopy selected nodes to clipboard
Ctrl + VPaste nodes from clipboard
Ctrl + DDuplicate selected nodes
Ctrl + ZUndo
Ctrl + Y / Ctrl + Shift + ZRedo
Ctrl + SSave workflow
Ctrl + ASelect all nodes
Ctrl + Shift + LView last execution
DeleteDelete selected nodes or connections

Typical use case: reuse logic across workflows

Section titled “Typical use case: reuse logic across workflows”
Workflow A (order processing)
→ Select the validation nodes (Decision + HTTP + SendMail)
→ Ctrl + C
Workflow B (returns processing)
→ Ctrl + V
→ Reposition and reconnect as needed

Tip: save the destination workflow before pasting to avoid conflicts if the browser closes unexpectedly.

When a flow contains an Iterator or Repeater node, the editor draws which part runs for each item on top of the canvas. It changes nothing about the flow: it is a visual aid computed at paint time and never saved.

Editor showing a dashed blue outline around the iterator and the nodes it runs for each item, with a dashed line towards the Merge Iterator node.

  • The outline wraps the loop body and carries the iterator’s name, preceded by the loop symbol. If the iterator is named “Per country”, the outline reads ↻ Per country.
  • The dashed line links the iterator to the node that closes it (MergeIterator or End). It deliberately has no arrowhead: it is not a connection data flows through, it only shows that those two nodes belong together. Data travels through the body, node by node.
  • The closing node stays OUTSIDE the outline, because it runs once when aggregating the results, not once per item.
  • Hovering the iterator highlights its loop and dims the rest of the canvas. That is what helps most in large flows.

An iterator inside another is drawn as concentric rings, each level with its own colour and more spacing towards the outside, so you can see which one contains which.

Three concentric outlines in different colours, each labelled with its iterator name: blue per country, violet per store, teal per product.

The editor warns in three situations, and each means something different:

WarningWhat happens
The loop does not end in MergeIterator or EndThe loop runs, but the aggregated result of the iterations goes nowhere. It may be intentional if the work is done by the last node of the body. The outline is drawn in amber.
The iterator has no node after itIt produces the items and does nothing with each one.
The iterator is not connected to anythingIt never runs. Usually a node left behind on the canvas; the notice is informational.

The name shown on the outline is the iterator node’s own name. To change it, double-click the node and edit the Label field: the outline updates on save. There is no separate name to keep in sync.

Under Settings → Editor preferences you can disable it with Show loops on the canvas. It is on by default.

Inside any configuration field you can use:

SyntaxDescriptionExample
{{field}}Field from current data{{email}}
{{field.subfield}}Nested field{{billing_address.name}}
{{@NodeName.field}}Data from a specific node{{@Webhook_1.order_id}}
{{#1.field}}Data from previous node (1 back){{#1.total}}
{{var.name}}Memory variable{{var.counter}}
{{$guid}}Unique UUIDa1b2c3d4-...
{{$timestamp}}Current timestamp in ms1712345678000
{{$datetime}}Current ISO date2026-04-07T10:30:00Z
  • Active flow: if the flow is active and receiving data while you edit, in-progress executions use the saved version. Your changes don’t take effect until you save.
  • Deactivate before big changes: if you’re reorganizing nodes or changing logic, deactivate first.
  • Credentials: when adding nodes that require credentials, make sure to configure them before testing.
  • Save frequently: there is no auto-save. Use Ctrl+S or the save button.
  • Test after each change using Test mode
  • Name nodes descriptively so the team understands the flow
  • Add Decision nodes to handle errors in critical nodes (external APIs, databases)
  • Use the trace to inspect what data passes between nodes

When done editing, see Execute a Flow to test and activate your changes.