Skip to main content

Workflows

Workflows constrain the Assistant to execute with a fixed set of tools, files, and context. Nomic has pre-built workflows for common project delivery tasks and a Workflow Builder with an integrated AI assistant to help you design your own.

Nomic Workflows

How Workflows Work​

Workflows provide a structured way to solve specific project delivery tasks by constraining Assistant's capabilities. Each workflow defines:

  • Fixed tools - A specific set of tool calls Assistant can use
  • Defined files and context - Specific files, integrations, or data sources the workflow can access
  • Task constraints - Boundaries that keep Assistant focused on the workflow's objective

This constraint-based approach ensures consistent, reliable results for repetitive project tasks like code compliance checks, submittal reviews, and QA/QC processes.

Pre-Built Workflows​

Nomic provides pre-built workflows optimized for common project delivery tasks:

  • Drawing Standards Check - Perform quality assurance and quality control checks on drawings and documentation
  • Submittal Review - Review contractor submittals against project specifications and drawings
  • Drawing Detail Search - Search past projects for similar drawings and examples to reference for your current work
  • Code Compliance - Check drawings against building codes and standards with cited compliance results

Each pre-built workflow is configured with the right tools and context to deliver accurate, consistent results for its specific task. Learn how to customize these pre-built workflows or use them as a jumping off point for your own custom workflows in the Best Practices section.

Workflow Builder​

The Workflow Builder is a two-panel interface for creating and editing custom workflows. The left side is a configuration form where you define every aspect of the workflow. The right side is an AI assistant that helps you design the workflow through conversation — describe what you want to automate and it will populate the form for you.

Workflow Builder

Builder AI Assistant​

The right panel is a conversational AI assistant purpose-built for workflow design. Instead of filling in every field manually, you can describe the task you want to automate and the assistant will:

  1. Ask follow-up questions to understand your process, inputs, and expected outputs
  2. Summarize its understanding and ask for confirmation
  3. Populate the form fields on your behalf
  4. Iterate with you until the workflow design is right

You and the assistant can work on the form together — any manual edits you make are visible to the assistant, and any fields the assistant fills in appear in the form immediately. When you're satisfied, click Create (or Save) in the header to finalize.

For detailed guidance on working with the builder assistant, see Using the Builder Assistant.

Configuration Fields​

The form on the left side of the Workflow Builder contains the following fields:

Workflow Name​

A short, descriptive name for the workflow (e.g., "RFP Response Drafter", "Drawing Review Checklist"). This is the name users will see when browsing and selecting workflows.

Category​

An optional label that describes the type of work this workflow performs (e.g., "Drafting", "Review", "Discovery", "Research"). Categories help organize workflows in lists and search.

Description​

A brief explanation of what the workflow does and when to use it. This appears as a summary when users browse available workflows.

Inputs and Outputs​

Short labels (up to 30 characters each) that describe what the workflow takes in and produces. These appear on the workflow card to give users a quick sense of what the workflow does.

  • Inputs — e.g., "Research topic, URL, file"
  • Outputs — e.g., "Summary, report, analysis"

Access​

Controls who can see and use the workflow:

  • Public to organization — Visible to all users in your organization with a shareable link
  • Private to user — Only visible to you, with admin metadata access

Project​

Optionally associate the workflow with a specific project. Only projects you are a member of are listed.

Context​

Files, folders, and tagged collections that provide persistent background knowledge for the workflow. The assistant can always search and read these, regardless of what users provide when running the workflow.

Use context for reference material that applies to every run — company standards, specification templates, internal guidelines, or other documents the workflow should always have access to.

Requested Files​

Files that users will be prompted to select or upload each time they start the workflow. Unlike context (which is the same every run), requested files are per-run inputs specific to the task at hand.

Each requested file slot includes a description so users know exactly what to provide. For example, a QA workflow might request "Drawing Set — Upload the architectural floor plan you want to check."

Linked Artifacts​

Documents attached to the workflow that the assistant can reference during execution. Artifacts are best used for static reference data like legends, terminology tables, or standards definitions. You can create artifacts directly in the builder before saving the workflow.

The assistant can create its own tables and documents at runtime, so there is no need to pre-populate artifacts as output templates. See Best Practices for detailed artifact guidance.

Instructions​

Custom instructions that guide the assistant's behavior during workflow execution. These are included in the assistant's system prompt to ensure consistent, task-focused execution. Click the instructions block to open a full editor.

This is the most important field in your workflow — the clearer and more specific your instructions, the more consistent your results. See the Best Practices guide for tips on writing effective instructions.

Assistant Mode​

Controls how the assistant executes the workflow:

  • Standard — Faster responses, suitable for simpler or interactive tasks
  • Deep Research — More thorough analysis with extended reasoning, good for complex review tasks
  • Background Agent — Runs autonomously until complete, ideal for long-running tasks like reviewing an entire drawing set

Model​

Which language model powers the workflow. Different models have different capabilities and trade-offs. The model selection is always a manual choice — the builder assistant will not set this for you.

Custom URL Slug​

When a workflow is set to public, you can define a custom URL slug (e.g., my-workflow) that creates a shareable link at /chat/my-workflow.

Getting Started​

To start building a workflow:

  1. Navigate to the Workflow Builder — Go to the Workflows page and click Create Workflow, or navigate directly to /workflows/new
  2. Describe your workflow to the assistant — Tell the AI assistant what task or process you want to automate, and it will help you design the workflow through conversation
  3. Review and adjust the form — Check the fields the assistant has populated, make any manual adjustments, and add context files or set the model and visibility yourself
  4. Click Create — When you're satisfied with the design, click Create in the header to save your workflow

Alternatively, you can fill in the form fields manually without using the assistant.

For detailed setup instructions, see the Quickstart guide or visit the Admin section to configure integrations.