> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enginy.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Run workflow

> Start a run of a published workflow. The workflow must be published first. Provide `input` only when the workflow declares a runtime input (see `runtimeInputContract` on `GET /v1/workflow/{workflowId}`).

Responses include direct Enginy app URLs when available. The response includes an `appUrl` to the run detail. MCP agents should return those URLs to users whenever they are present in the response.

    > **Required scope:** `WORKFLOWS_WRITE`
    >
    > **Rate limit:** 30 requests per minute



## OpenAPI

````yaml https://openapi.enginy.ai/definitions.json post /v1/workflow/{workflowId}/run
openapi: 3.1.0
info:
  title: Enginy API
  version: 1.0.0
  description: Public API for Enginy platform
servers:
  - url: https://openapi.enginy.ai
    description: Configured server
security: []
tags:
  - name: AI Variables
    description: >-
      Manage AI variables and discover the entity fields you can reference in
      prompts and entity requests.
  - name: Inbox
    description: >-
      Inbox endpoints for listing contact threads, reading thread messages,
      managing tags, and sending manual replies.
  - name: Workflows
    description: >-
      Build, validate, publish, run, and inspect advanced (graph) workflows,
      plus the block/condition catalog needed to author a workflow plan.
paths:
  /v1/workflow/{workflowId}/run:
    post:
      tags:
        - Workflows
      summary: Run workflow
      description: >-
        Start a run of a published workflow. The workflow must be published
        first. Provide `input` only when the workflow declares a runtime input
        (see `runtimeInputContract` on `GET /v1/workflow/{workflowId}`).


        Responses include direct Enginy app URLs when available. The response
        includes an `appUrl` to the run detail. MCP agents should return those
        URLs to users whenever they are present in the response.

            > **Required scope:** `WORKFLOWS_WRITE`
            >
            > **Rate limit:** 30 requests per minute
      parameters:
        - schema:
            type: string
          required: true
          name: workflowId
          in: path
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                input:
                  type: object
                  additionalProperties: {}
              additionalProperties: false
      responses:
        '201':
          description: Run started
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: string
                    enum:
                      - success
                  message:
                    type: string
                  data:
                    type: object
                    properties:
                      runId:
                        type: string
                      appUrl:
                        type: string
                        format: uri
                        description: Direct Enginy app URL for the run detail.
                      status:
                        type: string
                      sequenceNumber:
                        type: number
                    required:
                      - runId
                      - appUrl
                      - status
                      - sequenceNumber
                required:
                  - status
                  - message
                  - data
        '400':
          description: >-
            Invalid run input, or a webhook-with-declared-inputs workflow that
            cannot be run manually.
        '403':
          description: >-
            Advanced workflows are not enabled for this workspace. Ask your
            workspace admin to enable the feature.
        '404':
          description: Workflow not found or not accessible.
        '409':
          description: >-
            Either the workflow is not published (publish it first with POST
            /v1/workflow/{workflowId}/publish) or its published version changed
            while the run was starting (re-read the workflow and retry).
        '500':
          description: The run could not be started in the workflow engine.
      security:
        - apiKey: []
components:
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: x-api-key

````