Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.sagalegal.io/llms.txt

Use this file to discover all available pages before exploring further.

Building a workflow means laying out the steps you want to automate and configuring what each one does. Running it means executing those steps with real inputs and getting results.

​
The builder

Open the workflow builder from the Workflows page in the sidebar. You’ll see a visual canvas — an empty workspace where you assemble your flow. Add steps from the sidebar catalog, which is organized into Inputs and Actions. Drag a step onto the canvas or click to add it. Connect steps by dragging from one step’s output handle to the next step’s input handle. The connections define the order of execution and how data passes between steps. Each step has a configuration panel. Select a step on the canvas to open it in the sidebar, where you can set:
  • Step title — a label that identifies what this step does (this is what you see when referencing it from other steps)
  • Instructions or query — the prompt, search query, or directions for this step
  • Assistant — for prompt-based steps, which AI model or custom assistant to use
  • Step-specific options — things like which legal sources to search, which languages to translate between, or which task to run
You can also click Improve prompt on instruction fields to let the AI refine your phrasing.

​
Referencing earlier steps

When writing instructions for a step, you can reference the output of any earlier step by mentioning it with @. Start typing @ and select the step you want to reference. At runtime, that mention is replaced with the actual output from that step — so the data threads through the workflow automatically. This is how you build up context across the flow. A prompt step can analyze documents from an upload step. A drafting step can pull together the results of a research step and a review step into a final memo.

​
Saving and running

Click Save and run when your workflow is ready. You’ll give it a name, an optional description, and a language. You can also tag it with practice areas to make it easier to find later. If you want to make it available to your whole organization, check Request to make organizational — an admin will review and approve it. The workflow begins executing as soon as it’s saved — there’s no separate run button in the builder. The sidebar switches to run mode, showing each step’s status as it progresses:
  • Pending — waiting to start
  • In progress — currently running
  • Waiting for input — the step needs something from you (text or files)
  • Completed — finished, with results shown
  • Failed — something went wrong, with an error message
When a step needs input — like a prompt input or file upload — the workflow pauses and waits for you to provide it before continuing. Fill in what’s needed and the workflow picks up where it left off. Each step shows its execution time, and the final results appear in a Final assets section at the bottom — documents to download, text to copy, grid reviews to open, or research results to browse. After the first save, edits to the workflow are persisted automatically as you work.

​
Running an existing workflow

How a workflow starts depends on where it’s coming from:
  • From the library. Open a workflow from the Workflows page and it starts running directly — no extra confirmation step.
  • From chat, when the AI matches an existing workflow. Saga runs it inline in the chat thread, pausing only when a step needs input from you.
  • From chat, when the AI drafts a new workflow. When Saga sketches a new flow on the fly to handle your request, it appears as an inline card with a Start running button. The draft waits for you to review the proposed steps and confirm before executing.

​
Drafts

Drafts are workflows the AI authors when you ask it to handle a multi-step task in chat without naming an existing workflow. After the AI runs a draft, it lands in Workflows > Drafts with the steps preserved. From there you can:
  • Save — add it to your personal library so you can run it again
  • Edit — open it in the builder to adjust steps before saving
  • Discard — remove it if it isn’t useful
Drafts are limited to ten steps and use a streamlined set of node types, so they may be simpler than workflows you’d build by hand. Treat them as a starting point — the AI gets you a working flow quickly, and you can refine or extend it from the builder.

​
When something goes wrong

If a step fails, the workflow stops and shows an error message for that step. Downstream steps won’t run. You can adjust the failing step’s configuration and run the workflow again from the start. Common causes:
  • “Invalid assistant selection” — a step points at a custom assistant that no longer exists (deleted or its ID changed). Open the step, pick a currently available assistant, save, and re-run.
  • “Selected model is not enabled” — the model exists but has been disabled for the workspace. Pick another model in the step’s assistant dropdown, or ask an admin to re-enable the original.
  • An earlier step produced no output — if a step that referenced an upstream step via @ failed with an empty input, check the upstream step’s result before re-running.
  • Document processing not yet complete — if a “Files upload” step finished but the documents aren’t fully indexed yet, an immediately following “Run prompt” might not find content. Wait a few seconds and re-run.
  • Transient model or network error — re-run. Many failures resolve on retry.
There’s no partial resume — re-running starts from the top.

​
Inline workflow card doesn’t appear or isn’t clickable in chat

When you ask the AI to run a workflow from chat, an inline card with a Start running button is rendered in the conversation. If the card is missing or unresponsive:
  • Refresh the page. The card depends on the live chat connection, which can drop after a long idle period.
  • Try Chrome or Edge in the latest version if you’re on a less-tested browser.
If the card is still missing, open the workflow from the Workflows page instead — it’ll start running directly from the library. The result is the same.

​
Workflow library: drafts or templates won’t open (blank screen)

If you click a draft or template and nothing opens — and the browser console shows a 401 error — your sign-in session has expired in the background. The library list still renders from cache, but opening a workflow tries to fetch fresh data and fails authentication. Sign out (avatar > Sign out), close the tab, open a fresh tab, sign in again, and retry. If it keeps happening, check whether a browser extension (ad blocker, privacy guard) is blocking third-party cookies for sagalegal.io — the Workflow library needs a persistent session cookie. Incognito mode is a useful diagnostic: if workflows open fine in incognito, the issue is an extension or cookie setting in your regular profile.

​
Downloading files generated by a workflow

Some workflow steps — particularly code interpreter and drafting steps — produce files. They appear as file chips below the AI’s message in chat, or in the Final assets section at the end of a builder run. Click the chip to download. If the AI references a file with a sandbox:/mnt/data/filename.xlsx path in its text, that’s an internal path that isn’t browser-clickable. Look for the matching file chip below the message — that’s the real download. If the chip is missing, ask the AI to “save the file as a chat attachment” and it will re-package the output.