workflow_definition_create

Tool

workflow_definition_create

Create a workflow from a definition.

Create a workflow from a definition. It lands as a draft with version 0; the validator runs and its issues come back, so a draft with issues is still saved — including one with no `trigger` and no nodes yet, which is refused at publish rather than here. The definition's `id`, `product_id`, `name`, `description`, `status`, `version` and `dependencies` are server-owned: send them or not, they are overwritten. `grants`, `config_refs` and `owner` are yours.

Behavior

HTTP: POST /workflow/definition

Arguments

Name	Type	Required	Description
name	string	•	No description in the catalog.
definition	object	•	A workflow definition: trigger, nodes, edges, grants, config_refs.
description	string	—	No description in the catalog.

Response

Field	Type	Always	Description
live	object	•
draft	object	•
grants	object	•	The workflow principal's grants; null when Governance could not be reached.
health	object	•	What the dependency check found; null when nothing is unknown.
issues	array	•	Validation of the draft as it stands right now.
timeline	array	•	The last 20 health entries, newest first; `workflow_health_list` pages the rest.
workflow	object	•
dependencies	array	•	What the live version was validated against, with the hashes it saw.

Try it

Create a workflow from a definition.

When to use

Example

Ask your agent something like this:

Create a workflow from a definition.

The agent will invoke workflow_definition_create with these arguments:

{
  "name": "<name>",
  "definition": "<definition>"
}