Update a pipeline by selector
update_pipelineUpdate an existing Orchestra-backed pipeline by providing its ID or alias in the request. Git-backed pipelines cannot be modified via this endpoint.
Instructions
Update an existing Orchestra-backed pipeline. Select it with pipeline_id or alias in the request body. Git-backed pipelines cannot be updated through this endpoint.
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": "update_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 | ||
| published | Yes | ||
| pipelineId | No | ||
| 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 | |||