Workflow Builder
The Workflow Builder is the two-panel editor where you create and edit workflows: a configuration form on the left and an optional builder agent chat on the right. Fill the form in yourself, design it in conversation with the builder agent, or mix both. Use this page as a field-by-field reference and a guide to working with the agent.
Getting started
To create a workflow:
- Go to the Workflows page and click Create Workflow, or open
/workflows/new. - Describe what you want to the builder agent—or fill the form yourself using the fields below.
- Set access, model, and context yourself where needed; the builder agent cannot set these for you.
- Click Create (or Save when editing).
For first-time setup of integrations and projects, see the Quickstart.
Configuration fields
Workflow Name
A short, descriptive name (for example, “RFP Response Drafter”, “Drawing Review Checklist”). This is what users see when browsing workflows.
Category
An optional label for the type of work (for example, Drafting, Review, Discovery, Research). Categories help organize lists and search.
Description
A brief explanation of what the workflow does and when to use it. Shown as the workflow summary when browsing.
Inputs and Outputs
Short comma-separated labels describing what the workflow takes in and produces. These appear on the workflow card, so keep them scannable.
- Inputs — e.g. “Research topic, URL, file”
- Outputs — e.g. “Summary, report, analysis”
Capabilities
Optional tools the workflow may use, shown when your organization has them available:
- Code search — Search regulatory codes and standards. See Code Compliance.
- Web search — Search the public web for current information.
Capabilities are off unless you turn them on, including on cloned Nomic workflows. An admin can disable either one org-wide from Admin → Settings → Agent, in which case it does not appear here.
Access
Who can see and use the workflow:
- Public — Visible to everyone in the scope the workflow belongs to. When the workflow is tied to a project, that means project members; otherwise it means your whole organization.
- Private — Only you (with admin metadata access where applicable).
The scope comes from the Project field, not from a third Access option. To invite specific collaborators or promote a workflow to everyone in its scope, see Workflow management.
Project
Optionally tie the workflow to a specific project. Only projects you belong to are listed. Setting it also determines what Public access means, as above.
Context
Files and folders available on every run—the persistent background knowledge for this workflow (company standards, spec templates, guidelines).
Requested Files
Files users must provide each run (for example, today's drawing set). Unlike context, these change per execution. Each slot should have a clear description so users know what to attach. Slots that allow multiple inputs can accept folders; single-file slots accept documents only.
Linked Artifacts
Markdown documents attached to the workflow. They are best for stable reference material the workflow should keep available across runs, such as legends, terminology tables, or standards excerpts. The agent can create tables and documents at runtime; see Use artifacts wisely in the authoring guide.
Instructions
Custom instructions merged into the assistant’s system prompt. This is the most important field for consistency and quality. See Authoring instructions.
Assistant Mode
How the workflow executes—set by the author, not something runners change at launch. A workflow with no mode set falls back to Deep Research, so choose deliberately.
- Standard — Fast, conversational turns. Best for simpler or interactive tasks, like a focused review of a single document or a straightforward generation task.
- Deep Research — More thorough reasoning and tool use across sources. Best when the workflow cross-references multiple files, applies detailed standards, or produces thorough reports.
- Background Agent — Runs autonomously until complete. Best for long-running work—full drawing sets, submittal packages, or multi-step reviews that dispatch sub-agents—and is the preferred mode for most review and compliance workflows.
Model
Which foundation model powers runs. You choose this explicitly—the builder agent does not set it.
The Workflow Builder agent
The builder's right panel is an AI assistant that helps you design workflows through conversation. Instead of filling in every field manually, you describe the task you want to automate; the assistant asks questions, proposes a design, and populates the form on your behalf. It reads the current form state before every change, so manual edits and assistant updates never conflict.
A good opening message covers the task or process to automate, what inputs users will provide each run, what outputs the workflow should produce, and any standards or steps your firm follows—but you don't need all of it upfront.
How it works
- You describe the task — what the workflow should do, what files are involved, and what the output should look like.
- The assistant asks follow-up questions — gathering details about inputs, outputs, steps, standards, and constraints.
- The assistant summarizes its understanding — it presents a proposed design and asks for confirmation before making changes.
- The assistant populates the form — once you approve, it fills in the relevant fields.
- You iterate together — continue the conversation to refine the design, adjust instructions, or add detail.
The assistant is designed to ask follow-up questions. A short description like "I want a workflow that checks drawings against our internal standards" is a perfectly fine starting point.
What the assistant can and can't set
| Field | Assistant can set? | Notes |
|---|---|---|
| Name | Yes | |
| Description | Yes | |
| Category | Yes | |
| Inputs | Yes | |
| Outputs | Yes | |
| Requested Files | Yes | Defines per-run file prompts (including optional/multiple slots) |
| Instructions | Yes | The assistant's strongest area |
| Assistant Mode | Yes | Standard, Deep Research, or Background Agent |
| Linked Artifacts | Yes | Can create or update attached markdown documents |
| Access | No | You set public/private yourself |
| Model | No | You choose the model yourself |
| Context files | No | You add context files/folders using the form |
The assistant reminds you to set access, model, and context files when they're relevant. Before you save, review the fields it can't set.
Working together on the form
The builder is collaborative—you and the assistant can both change the form at any time:
- The assistant reads before writing. Before every update it checks the current form state to detect any manual changes you've made.
- Manual edits are respected. If it notices you changed a field it previously set, it asks whether to keep your version or use its suggestion.
- Confirmation before overwriting. When it would change existing content, it shows the proposed change and waits for approval.
The assistant is available on the edit page too, so you can keep collaborating after the workflow is created.