Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Workflow Authoring, Validation, and Publishing

Workflow authoring operations let supported clients create or change workflow structure. Validate the proposed changes before making a release available to users.

Validate the current workflow before release

Inspect validation findings, correct the workflow, and run representative inputs before using the supported publication process. A structural check does not establish answer quality.

Copy the example
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "projects_validate",
    "arguments": {
      "project_id": "<project-id>",
      "severity_filter": "all"
    }
  }
}

Before you begin

An authoring-capable public API or MCP tool and permission to edit the project.

Key concepts

Term
Definition

Schema

A definition of fields, types, required values, and supported constraints. Use it to validate the shape of data; it does not establish factual correctness.

Validation

A check against supported structure and constraints. Passing validation does not prove that generated answers meet every quality requirement.

Revision conflict

A response indicating that the resource changed since the version used for an edit. Read current state and reconcile changes before resubmitting.

Draft

The editable project configuration before or apart from a selected published release. Saving a draft does not necessarily change what published users run.

Published release

The selected project version made available through a published execution path. Confirm the active release after a publication or promotion action.

Edit and publish a workflow through MCP

  1. Read the current project and its available node schemas.

  2. Submit supported changes and inspect validation findings.

  3. Review the updated project, then publish through its supported release process.

The project contains valid connections and configuration before publication.

Behavior and limitations

Use only authoring operations listed in the public API or MCP catalog. Use the documented MCP authoring tools when the public REST catalog has no authoring operation for the task. When a contract supplies a revision check, refresh after a conflict instead of overwriting newer edits. Structural validation does not prove the workflow meets every business requirement.

API Versions and Compatibility

Was this helpful?