Create a pipeline
create_pipelineCreate a new pipeline from a JSON definition and optionally validate its schema before saving, so you can add pipelines to Orchestra-backed or Git-based storage.
Instructions
Create a new pipeline. The request body includes the pipeline definition as JSON.
Use Validate pipeline schema before creating a pipeline if you want to check the payload without saving it.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"data": "<data>",
"published": "<published>"
},
"name": "create_pipeline"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | Pipeline definition as JSON, matching the pipeline YAML structure (required top-level keys: version, name, pipeline). Validate it with the validate_pipeline tool before submitting. | |
| alias | No | ||
| folder | No | Folder path for an Orchestra-backed pipeline, such as `finance/daily`. Omit it on update to keep the current folder; send null or an empty string to clear it. | |
| message | No | ||
| yamlPath | No | ||
| published | Yes | ||
| repository | No | ||
| defaultBranch | No | ||
| workingBranch | No | ||
| messageIsCustom | No | ||
| storageProvider | No | ORCHESTRA | |
| X-Orchestra-Account-Id | No | Act on this account rather than the one the credential resolves to. Omit it to use the credential's own account. An API key is issued to a single account, so it may only name that account; an OAuth token may name any account its grant covers. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||