Workflows

A workflow chains agents into a repeatable process: an intake step gathers the facts, a drafting agent writes, a reviewer signs off, and a finished document comes out the other end. Where chat is a conversation, a workflow is a procedure, the same steps, in the same order, every run, with a full record of what happened.

Authoring needs the author workflows grant (admins have it automatically); running one from chat is open to any member the workflow is visible to. Workflows are part of the Automation plan.

Concepts

• A workflow is a sequence of steps. Most steps are agents (workflow-kind agents) and each receives the previous step's output and produces its own.
• Steps can branch on their output, run in parallel and merge, repeat until a condition is met, pause for a review, or render the result as a document.
• A workflow begins either with an input form (fields a person or the API fills in) or an intake agent (a conversation on the chat page that gathers what's needed).
• Like agents, workflows have draft and active versions: edit and test the draft, Promote to make it the live version. Runs record exactly which version they executed.

The Builder, the YAML tab

The workflow editor has two views of the same workflow:

• Builder — form-driven step cards: add a step, pick its kind and agent, set what it hands to which step next. Renaming a step updates every reference to it.
• YAML — the workflow's full definition as text, for precise editing, copying between workflows, and version-to-version comparison. The Reference drawer beside it documents every field, the same content as this site's workflow YAML reference.

Build in whichever suits the change. Validation runs on save and names exactly what's wrong, down to the step.

Generate a workflow from a description

Describe the process in plain English "capture the key facts about the NDA a client needs, draft it against our standard terms, then have a partner review it" and the generator builds a runnable starting point: the workflow, and draft agents for each step with proposed instructions. Everything arrives as drafts for you to review, adjust, and promote; nothing runs until you say so. Generation runs on your workspace's own model infrastructure, the description isn't sent to any third party.

Review steps

A review step pauses the run until a person acts. Who may act is set on the step, admins, named members, or roles.

1. When a run reaches the review, every eligible reviewer gets a notification (the bell). The link opens the review page: the content awaiting review and the step's instructions to the reviewer. The Notifications page shows who started the run (an API badge marks runs started through the API), can be filtered by workflow, date, and whether the review has been completed, and lets you delete notifications you're done with, Show deleted lists them again, with Restore.
2. The reviewer can Approve it unchanged, Approve with edit, changing the content (or just the one field the step was scoped to) with a comment explaining the change, or Reject with a comment, which stops the run.
3. The run resumes on approval, and the decision, reviewer, comment, and any edit are recorded on the run permanently.

One reviewer acting clears the request for the rest, and every reviewer's notification then carries a Reviewed badge naming who acted and how so a notification you've opened but not actioned is never mistaken for one that's done.

Render steps

End a workflow with a render step to produce a PDF or Word document from the final content. The finished file appears on the run page for download, and via the API for machine callers.

Draft steps

A draft step produces a document from your drafting library instead of from the text of the step before it. Name a template — a document author's fixed recipe — and no AI is involved: the blocks are settled in advance and the values come from the previous step's output, checked against the template's fields. The editor shows the template's input schema with a Copy button, so the step before can be set up to supply exactly those fields, and tells you which of them that step's schema provides. The finished Word or PDF file lands on the run page like a render step's, with a link to the document itself on the drafting pages, and a template or document type that requires a review holds the file until someone attests to it there. A field the previous step didn't supply stops the step unless you allow unanswered fields on it.

Runs

Starting a workflow from chat or from the API creates a run you can watch live: each step's status and output streams into the run page as it executes, review pauses are flagged, and the final output (and any rendered document) lands at the bottom.

• History lists runs with filters, workflow, status, date range, who started it.
• Who sees a run: the person who started it and admins, always; plus anyone on the workflow's run visibility list (set alongside its access), for teams where oversight of everyone's runs matters. Seeing a run doesn't grant cancelling it that stays with the initiator and admins.
• Runs that pause for external reasons (a busy model, a usage limit) resume on their own; a cancelled run stops where it is and says so.
• Delete run (admins, once a run has finished): removes the run's record and any document uploaded for it that no other run uses; a document another run still uses is kept. The confirmation says how many of each. A run that's still going must be cancelled first.

Workflow access

Like agents, a workflow can be restricted to members and roles, everyone else neither sees nor starts it. Authors, admins, and the creator always retain access.

Export and import a workflow bundle

Export downloads the workflow, its definition and the agents it uses, knowledge documents included, as one portable bundle; Import brings a bundle into any workspace as drafts. One deliberate reset on import: review steps arrive assigned to admins, because the bundle never carries people from another workspace. Reassign reviewers before promoting.

The API

On the Automation plan, workflows are also a machine surface: list them, start runs, stream progress, upload input documents, and collect results. Used with API keys your admin issues. Start at the API guide.