Create and edit workflows
A workflow is a reusable, named procedure that turns a real task — code compliance, RFI drafting, drawing review — into something one click can run. This page covers the basics of building and updating them.
Create a new workflow
- Open Workflows from the left nav.
- Click New workflow.
- Give it a clear, task-shaped name like "ASHRAE 90.1 envelope check" — names live on the Workflows list and inside Assistant, so write them for the person who will run them.
- In the builder, describe what the workflow should do, what files it needs, and what output it should produce.
- Save it as private while you test.
Once saved, the workflow shows up in the Workflows list and inside Assistant's workflow picker.
Edit a workflow
Open any workflow and click Edit. Saving creates a new version. You can:
- Update instructions and standards.
- Add or remove requested files (slots a user fills in when they run it).
- Add context files that should be included on every run.
- Change visibility (private vs. shared with your org).
Visibility: private vs. shared
Each workflow has a visibility setting:
- Private — only you can see and run it. Use this while drafting.
- Shared with org — visible to everyone in your Nomic tenant. Use this when the workflow is ready for teammates.
You can flip visibility from the workflow's settings. Changing a shared workflow back to private does not delete other people's run history.
Use private workflows for drafting and shared workflows for approved team processes. If several people are building workflows for the organization, agree on naming, ownership, and review before sharing broadly.
Best practices
- Start small. Get the workflow doing one task well before adding more.
- Use requested files rather than hardcoded context when the input changes each run.
- Test on one sample drawing or spec before sharing — it's much easier to spot bad instructions on a single page than on a full set.
- Ask a subject matter expert to review the first few outputs before making a workflow visible to the whole organization.
- Retire or rename old versions so teammates do not run the wrong workflow.