Workflows and Artifacts

Running a workflow

Pick a workflow on a title (or on a series for collection workflows) and run it. The run shows its progress; when it finishes, the result opens as an artifact and lands in the title’s artifact list. Some workflows take inputs, like a target budget range for a finance plan; those are recorded with the run.

Artifacts

Artifacts are durable documents and tables: Coverage reports, character breakdowns, schedules, and finance or production tables. Most document and table artifacts can be edited through a Draft, with history and saved versions. View source exposes Markdown for document artifacts when you need exact control. Coverage keeps its dedicated report layout and is locked against edits.

Generated and Saved versions stay immutable. Your first change creates or resumes one Draft, autosave updates that Draft, and Save version adds an immutable snapshot without closing it. History can restore an older version into the Draft or discard the Draft without deleting saved work.

Export creates native files from the selected version, not a printout of the browser view. Documents offer PDF, Word, Google Docs, and text; tables offer Excel, CSV, Google Sheets, and text. Google exports are editable native Docs or Sheets files, and pending Draft changes finish saving first.

Building your own workflows

Pro and Max can build and run custom workflows. Existing custom workflow definitions and results remain readable after a downgrade. The builder supports document and table outputs: documents can generate freeform Markdown or use an outline for named sections, while tables keep typed columns and rows. You can duplicate a supported built-in workflow as a starting point; you do not need to author JSON Schema.