Sonata

Documentation · For administrators

Administering workflows

Building workflows is an admin activity; running them is for everyone who can see them. The builder is no-code, and the safety rules are structural.

Building

A workflow is an ordered list of steps: run an agent, take an action, or pause for human approval. Lead with agents; give an agent step a plain-language instruction and it composes with the agent’s own role. Available actions come live from your connected systems, so a newly connected tool appears automatically, with anything that writes marked as requiring approval. A live readback panel describes what the workflow does in plain language as you build.

Templates

Starter templates ship with the product and appear alongside My Workflows. A template is never run directly: using one forks it into your own draft to adapt, so the starting points stay clean. The exception is a watcher template: it is adopted rather than forked, one step that creates the active watcher and the schedule that runs it together. Adopting visibly moves it: while your organization runs that watcher, its card leaves the gallery and the watcher’s single home is the Your watchers section; delete the watcher and the template card returns. Each watcher asks for its own scope: the renewal watcher takes the collection to watch and a lookahead window (60 days by default); the Federal Register monitor takes the agencies, search terms, and document types to watch; the legislative monitor takes policy areas (Library of Congress suggestions) and keywords, both matched as plain text against bill titles and latest summaries; the Comment-cycle monitor takes the agencies and search terms to watch on Regulations.gov, where the matching is done by Regulations.gov’s own search. All take a daily or weekly cadence and the autonomy their runs use; a watcher is owned by whoever adopted it, and its runs are attributed to them. Pause or resume it any time from Your watchers.

Autonomy, honestly

Autonomy is chosen per run, not built into the workflow; for a watcher it is chosen once at adoption and applied to every scheduled run. The line that never moves: writes pause for a person, at every autonomy level. Deleting a workflow never deletes its history; every run keeps its own copy of the steps it executed, and cost records are kept as accounting facts.

How to

Build a workflow

Authoring is org admin and super admin; running is for everyone who can see the workflow.

  1. From My workflows, select New workflow.
  2. Name it, describe it, and choose its department, or Whole organization.
  3. Add steps in order: Run an agent, Human approval, or Take an action. Give agent steps a plain-language instruction; reorder with the arrows.
  4. Read the What this workflow does panel; it describes the workflow in plain language as you build.
  5. Set Status to Active when it’s ready (drafts stay editable but can’t run), then Save workflow, or Save and run.

Start from a template

  1. Find the starter templates alongside My workflows and select Use this template.
  2. Sonata forks it into your own draft to adapt; templates are never run directly, so the starting points stay clean.

Edit or delete a workflow

  1. Select Edit on the workflow’s row to reopen the builder.
  2. Delete workflow lives at the bottom of the editor. Past runs are kept and remain viewable; each run stores its own copy of the steps it executed.

All documentation · Everything above describes the product as it ships today. If something here doesn’t match what you see, tell us.

← Back to documentation