Deploy Workflow

Deploy the workflow's saved state as a new active version. Trigger webhooks, schedules, and MCP tools are synced the same way as the Deploy button. The request has no body. Requires admin access to the workflow's workspace, the same permission the Deploy button needs. The key acts as its owner, so the owner's current workspace role must allow it. A scoped or organization key also needs an admin grant on the workspace or workflow; a key without one is rejected with 401.

POST/api/workflows/{id}/deploy
X-API-Key<token>

Your SteelEngine API key (personal, workspace, or organization). Create personal and workspace keys under Settings > API Keys. Create organization keys under Organization Settings > API Keys.

In: header

Path Parameters

id*string

The unique identifier of the workflow.

Response Body

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/api/workflows/string/deploy"
{  "apiKey": "Workspace API keys",  "isDeployed": true,  "deployedAt": "2026-10-21T15:04:05.000Z",  "warnings": []}