> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/technical-reference/apis-and-mcp/workflow-authoring-validation-and-publishing.md).

# 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](https://1957915746-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FQdgrQrQni1rBiYvvFfcv%2Fworkflow-authoring-validation-and-publishing.png?alt=media)

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

<details>

<summary>Copy the example</summary>

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

</details>

## 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.

## Related resources

[API Versions and Compatibility](https://docs.stackai.com/technical-reference/apis-and-mcp/api-versions-and-compatibility.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/technical-reference/apis-and-mcp/workflow-authoring-validation-and-publishing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
