Skip to main content

​
What it is

Flows let you chain AI agents to automate an entire task from start to finish, without copying and pasting responses from one conversation to another. Think of an assembly line: each step receives the result of the previous step, does its part, and passes it on. For example:
Contract received → one agent summarizes the document → another agent points out the risks → the final result is saved for you to review.
You build this path once, by dragging blocks on the screen, and then run it as many times as you want, manually or automatically on a schedule.

​
How to access

  • Sidebar → Flows
  • To create: New flow button.
The page only appears if the Flows permission is enabled for you. If you can’t find the menu, contact your company’s administrator.
The Flows page has two tabs:
  • My flows — the flows you created and the ones shared with you.
  • Templates — ready-made flows provided by your company that you can use as a starting point.

​
Basic concepts

​
How to use

​
1. Create a flow

1

Click New flow

2

Fill in the fields

  • Flow name (required) — between 3 and 60 characters. It can’t repeat another flow’s name.
  • Description (optional) — the flow’s goal, in a few words.
3

Click Create

The flow editor opens next.

​
2. Get to know the editor

The editor has three areas: The top bar has the Undo, Redo, Validate, Run, Run history, Help, and Save buttons. Next to the flow name, you see whether there are Unsaved changes or everything is All saved.

​
3. Build the flow

1

Drag a node from the palette onto the canvas

2

Connect the nodes

Click a node’s connection point and drag it to the next node.
3

Click a node to configure it in the Properties panel

4

Repeat until you reach the Output node

Every flow needs one Start node and at least one Output node.

​
4. Node types

​
5. Configure each node

  • Content input — when enabled, clicking Run opens a window for you to paste text or upload a file (PDF, DOCX, XLSX, CSV, TXT, MD, JSON, HTML, PPTX, EPUB, RTF). This content is the flow’s starting point. When disabled, the flow starts without asking for anything.
  • Start mode:
    • Manual — you decide when to run it, by clicking Run.
    • Automatic — the flow runs on its own, on the defined schedule:
      • Interval — every X hours (e.g., every 6 hours).
      • Weekly — on the chosen days of the week and time. The screen shows when the next run will be.
For a weekly schedule, choose at least one day. Without it, the flow never runs.
  • Agent — choose one of the agents you can use. If the list is empty, create an agent first (see Agents).
  • Instructions — tell the agent what to do in this step. E.g., “List the three main risks in this contract.” The previous node’s output is added right after your instructions.
  • Timeout (ms) — maximum time to wait for the response, in milliseconds (1,000 ms = 1 second). Leave empty for no limit.
  • Tool and Function — the tool and the function of it that will be called.
  • Arguments (JSON) — the data sent to the tool. Use {{input}} to include the previous node’s output.
  • Comparison — Contains, Does not contain, Equals, Does not equal, Starts with, Ends with, or Matches regex.
  • Value to compare — the text to look for in the previous node’s output. E.g., APPROVED.
  • Case sensitive — enable if “Approved” and “APPROVED” should be treated as different.
If the condition is true, the flow continues through the node’s top output. Otherwise, it continues through the bottom output.
To use Condition, ask the previous agent for a standardized response. E.g., “Respond only APPROVED or REJECTED.”
All paths leaving this node run at the same time. Connect at least two outputs and use a Merge node afterward to combine the results.
Merge waits for all paths to arrive before continuing. Connect at least two inputs. In Merge strategy, choose how to combine:
  • Concatenate — joins the texts, one after the other.
  • JSON array — turns each result into an item in a list (useful when the next step is technical).
  • First non-empty — uses the first path that has content.
Choose another flow to run as a step in this one. Sub-flows support up to 5 levels (a flow inside another, inside another…). If the same flow appears twice in the chain, the run is blocked.
In Format, choose Plain text or JSON.
Agent and Tool nodes also show a Failure rate (%) / Failure chance (%) field. It’s only for testing how the flow behaves when a step fails. Leave it at 0 for normal use.

​
6. Validate and save

1

Click Validate

Symphony checks whether the flow is ready.
  • Validation passed — the flow can be saved and run.
  • Validation issues — a list of what to fix appears. Click an item to go straight to the node with the problem.
2

Click Save

Or use Ctrl + S.
The most common issues:

​
7. Run the flow

1

Save the flow

The Run button only works when everything is saved.
2

Click Run

3

Provide the content, if asked

If the Start node has Content input enabled, choose:
  • Text — paste or type the content.
  • File — click or drag the file. Wait for processing: a preview of the extracted content appears.
4

Confirm

While it runs, each node shows its own status on the canvas.
While the flow is running, editing is locked. To stop it, click Stop. The node already in progress finishes before the run stops.

​
8. View the result

When it finishes, the side panel shows:
  • Final result — what the flow delivered. Click View full to read everything and download the result as .txt or .json.
  • Selected node — click any node to see the Input received and the Output of that step. This helps you find where a result came out differently than expected.
Click Close run to return to the editor.

​
9. Run history

The Run history button lists every time the flow ran, with status and time. Click a run to see the result and the details of each step. When an automatic flow starts, finishes, or fails, you get a notification on the platform, with an Open button to see the result.

​
10. Manage flows

In each flow’s menu, in the list:

​
11. Use a template

The Templates tab holds ready-made flows provided by your company. They’re read-only: to adapt a template, use Clone and edit your copy.
Administrators can turn a flow into a template (Make template) or remove it from the list (Remove from templates). Templates are visible to everyone in the company.

​
Practical example: contract summary

1

Create the "Contract summary" flow

2

Drag a Start node and enable Content input

3

Drag an Agent node to summarize

Choose an agent and write in Instructions: “Summarize this contract in up to 10 bullet points.”
4

Drag another Agent node for the risks

Write in Instructions: “Based on the summary, list the three main risks for the company.”
5

Drag an Output node

6

Connect the nodes

Start → Agent (summary) → Agent (risks) → Output.
7

Click Validate, then Save

8

Click Run, choose File, and upload the contract

9

Read the Final result

Download the .txt if you want to keep it.

​
Keyboard shortcuts

The Help button in the editor shows this summary at any time.

​
Best practices

  • Start simple. First build a flow with Start → Agent → Output, test it, and only then add steps.
  • One task per node. Short, clear instructions for each agent work better than one agent doing everything.
  • Test with real content before enabling Automatic mode.
  • Use the history to understand failures: click the node that failed and check the input it received.
  • Give nodes clear names (Name field), like “Summarize contract” or “Classify risk”. This makes the flow and the history easier to read.
  • Keep usage in mind. Each Agent node uses AI and counts toward your usage, just like a chat message. Automatic flows that run often consume continuously.

​
Frequently asked questions

There are unsaved changes. Click Save and try again.
In the Start node, check that Start mode is set to Automatic and, for a Weekly schedule, that at least one day is selected. Also check that the flow has no validation issues.
Yes, any agent you have permission to use, including the ones shared with you.
Only if you shared it with the Can edit permission. With Can run, the person can only run the flow.
Each company can start up to 30 runs per minute. Wait a few seconds and try again.
Open the run in History, click the node with Failed status, and read the error message. If your AI usage limit has run out, Agent nodes fail too (see Settings → Usage).

​
Known limitations

  • The flow name must be between 3 and 60 characters and can’t repeat another flow’s name.
  • The flow needs exactly one Start node and at least one Output node, and can’t have paths that go back (loops).
  • Sub-flows support up to 5 levels.
  • Each company can start up to 30 runs per minute.
  • You can’t edit a flow while it’s running.
  • Connections can’t be edited: to change one, delete it and create another.
  • Templates are read-only: to change one, clone it.
  • Creating and using flows depends on the Flows permission, set by the administrator.