Workflows Overview

Current workflow routes for CRUD, deployment, execution, metrics, node definitions, and plugin discovery. Workflow APIs live under /workflows.

Endpoint Areas

Area	Endpoints
Workflow CRUD	`GET/POST /workflows`, `GET/PUT/DELETE /workflows/{id}`
Deployment lifecycle	`POST /workflows/{id}/deploy`, `POST /workflows/{id}/undeploy`
Execution	`POST /workflows/{id}/execute`, `POST /workflows/execute-in-memory`
Execution history	`GET /workflows/{id}/executions`, `GET /workflows/{id}/executions/{executionId}`, `POST /workflows/{id}/executions/{executionId}/cancel`
Metrics	`GET /workflows/{id}/metrics`, `GET /workflows/{id}/metrics/timeseries`
Definitions and plugins	`GET /workflows/node-definitions`, `GET /workflows/node-definitions/{type}`, `GET /workflows/plugins/trusted`

Webhook-trigger endpoints also exist outside the /workflows prefix under /webhooks/v1/{workflowId}/{nodeId} and /webhooks/v1/{workflowId}/{nodeId}/*.
GET /workflows, POST /workflows, and POST /workflows/execute-in-memory are workspace-scoped and currently use the X-Workspace-ID request header.
Workflow payloads include serialized webhookEndpoints metadata when webhook registrations exist for the definition.
The OpenAPI schema is the source of truth for request and response shapes, including execution payloads and node-definition resources.
Workflow node definitions are runtime data from GET /workflows/node-definitions. Clients should treat that endpoint as the source of truth instead of relying on static provider/tool inventories.