Most legal work is, in fact, recurring. New matter intake, client onboarding, demand letters, chronology builds, issue-spotting passes, settlement outlines — the steps rarely change matter to matter, only the inputs do. Workflows is the surface in Xycora where you capture those recipes once and run them everywhere.
A workflow is an ordered list of steps that can include AI prompts, document reads, vector searches, conditional branches, notifications, and scheduled actions. Steps can be sequenced linearly or grouped into parallel lanes that run concurrently — useful when an AI prompt and an email draft can be produced at the same time. Every step's output is threaded into subsequent steps automatically, so a downstream prompt can reference the upstream draft without templating.
Seven templates ship in the box
You don't start from a blank page. Xycora seeds seven workflow templates on first boot:
- New matter from existing client — manual; opens a fresh matter and links the client.
- Matter kick-off — automatic, on matter created; runs the welcome email and the initial action list in parallel lanes.
- Draft demand letter — manual; generates a firm-voice demand letter from the matter facts.
- Spot legal issues — manual; runs a structured issue-spotting pass over the matter documents.
- Build chronology — manual; assembles a dated event timeline from the document set.
- Client welcome — automatic, on client created; sends the welcome letter and fires a conflict check in parallel.
- Quick legal research — manual; runs a jurisdiction-aware research pass and returns cited findings.
Build your own — visually or with AI
The visual builder is a three-column canvas: settings on the left, a story-view of the steps in the middle (drag-drop reordering, parallel-lane insertion), and an inspector on the right for the selected step. You can change a step's type, edit its prompt, toggle multi-step reasoning, or attach tools like vector search without leaving the canvas.
If a workflow is easier to describe than to build, you can describe it in one sentence and Claude will draft the whole thing — steps, prompts, dependencies, and inputs — for you to review and save.
Triggered automatically, or run by hand
Every workflow declares one or more triggers: manual, on matter created, on client created, or scheduled. Automation triggers are fire-and-forget: a failing workflow never blocks the action that triggered it, and every run is recorded with status, inputs, outputs, and per-step results. You can re-run, cancel, or inspect any run from the run-history view.
Shared the way matters are shared
Workflows reuse the same sharing model as the rest of Xycora — private to you, shared with specific users, or visible firm-wide — and the sharee's access level (use vs edit) is enforced server-side. Only the owner can delete a workflow or change its sharing, so a colleague who can use a workflow cannot reshape or remove it underneath you.