Saga’s legal engineers can help you design workflows tailored to your firm’s specific processes — reach out to your account team if you’d like assistance.
How workflows are structured
A workflow is a linear sequence of steps. Each step is a node that does one thing — generate text, search legal sources, translate a document, run a grid review. You connect nodes in the order you want them to run, and data flows from one step to the next automatically. There’s no branching or looping — every workflow is a straight line from start to finish. This keeps things predictable: you always know what runs when, and each step can reference the output of any earlier step.What steps can do
Steps fall into two categories: inputs that collect information from you, and actions that do something with it.Inputs
Actions
A Code interpreter step can return files, such as Excel and CSV files, charts, and HTML pages. The files appear in Final assets after the run. For previews and downloads, see “Files, charts and HTML pages” in the Chat overview.
How data flows between steps
Each step can reference the output of any step that came before it. When you’re configuring a step’s instructions, type@ to mention a previous step by name. At runtime, that mention is replaced with the actual output from that step.
For example, a “Run prompt” step can @ a “Files upload” step to analyze the uploaded documents, and a “Drafting” step further down can @ both to produce a final report. The data threads through the workflow automatically.
