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:

1. Go to the Workflows page and click Create Workflow, or open /workflows/new. From a project's Workflows page, Create workflow files the new workflow in that project.
2. Describe what you want to the builder agent—or fill the form yourself using the fields below.
3. Review the model and effort the builder agent proposes, and add context files yourself where needed; the builder agent cannot set context for you.
4. Click Create (or Save when editing). New workflows start as Invited people only. Sharing, promotion, and scope live on the Sharing tab, not on this form.

For first-time setup of integrations and projects, see the Quickstart.

Configuration fields​

The form opens with one card — what the workflow is called, the instructions the agent runs, and the model that runs them. Tools follow. Context and catalog details are folded at the bottom.

Workflow Name​

The title at the top of the card. A short, descriptive name (for example, “RFP Response Drafter”, “Drawing Review Checklist”). This is what users see when browsing workflows.

Description​

The line under the title. A brief explanation of what the workflow does and when to use it. Shown as the workflow summary when browsing.

Instructions​

Custom instructions merged into the Nomic agent’s system prompt. This is the most important field for consistency and quality. Click the preview (or Edit) to open the full editor. See Authoring instructions.

Model​

The model picker sits at the bottom-left of the card. It decides which foundation model powers runs. The builder agent recommends a model and effort as part of its design and sets them once you confirm; you can change them at any time.

Where the model supports it, pick Low, Medium, High, or Extra High effort. The closed list is Auto, everyday models, and Sonnet 5.5 Extra High for exhaustive work — not every model × effort combination. Extra High also runs until the task is complete. Used Deep Research before? That's Medium. Used Background Agent? That's High.

Tools​

The tools the workflow may use when it runs, one row each. Add Tool or MCP opens the same menu as the agent composer; the trash icon on a row removes it. What you can add, when available on your instance:

• Web search — Search the public web for current information.
• Codes Search — Search regulatory codes and standards. The pencil on the row sets the jurisdiction. See Code Compliance.
• MCPs — Specific organization or personal MCPs (for example Linear). Each row shows Login, Reconnect, Connect, Log out, or Disconnect depending on your own connection to that MCP, and the pencil opens its settings. Private MCPs only apply when that user runs the workflow; other runners skip MCPs they do not have connected.

Tools are off unless you turn them on, including on cloned Nomic workflows. On Business and Enterprise, an admin can disable a capability org-wide from Admin → Settings → Agent, in which case it does not appear here.

Context​

A collapsed section below Tools; its header summarizes what's inside (for example, “2 files, 1 requested file”). It holds three kinds of files:

Context files — 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.

Details​

A collapsed section at the bottom of the form. None of these change how a run behaves; they appear on the workflow card and in search. It opens automatically when any of them is already filled in.

• Inputs — short comma-separated labels for what the workflow takes in, e.g. “Research topic, URL, file”
• Outputs — what it produces, e.g. “Summary, report, analysis”
• Category — an optional label for the type of work (for example, Drafting, Review, Discovery, Research)

The Workflow Builder agent​

The builder's right panel is an agent that helps you design workflows through conversation. Instead of filling in every field manually, you describe the task you want to automate; the builder agent asks questions, proposes a design, and populates the form on your behalf. It reads the current form state before every change, so your manual edits and its 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​

1. You describe the task — what the workflow should do, what files are involved, and what the output should look like.
2. The builder agent asks follow-up questions — gathering details about inputs, outputs, steps, standards, and constraints.
3. The builder agent summarizes its understanding — it presents a proposed design and asks for confirmation before making changes.
4. The builder agent populates the form — once you approve, it fills in the relevant fields.
5. You iterate together — continue the conversation to refine the design, adjust instructions, or add detail.

What the builder agent can and can't set​

Field	Builder agent 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 builder agent's strongest area
Linked Artifacts	Yes	Can create or update attached markdown documents
Tools	Yes	Turns on web search, Codes Search, or specific MCPs only when you ask for them, and only tools available to you
Model	Yes	Recommends a model and effort and sets them after you confirm
Context files	No	You add context files/folders using the form
Sharing / scope	No	Invite people, promote to everyone, and change organization vs project on the Sharing tab after you save

The builder agent reminds you to add context files when they're relevant. Before you save, review the fields it can't set. Sharing is never part of the builder form.

Working together on the form​

The builder is collaborative—you and the builder agent can both change the form at any time:

• The builder agent 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 builder agent is available on the edit page too, so you can keep collaborating after the workflow is created.

Related​

• Workflows overview
• Authoring instructions
• Run a workflow
• Workflow management