Skip to main content
POST
Create Runner

Overview

Register a new ComfyUI runner instance to execute workflows. Runners represent your own ComfyUI installations that ComfyControl can communicate with.
Your ComfyUI instance must be accessible via HTTP/HTTPS and have the ComfyUI API enabled.

Request Body

string
required
A descriptive name for your runner (1-100 characters).
string
required
The URL where your ComfyUI instance is accessible. Must be a valid HTTP or HTTPS URL.Example: https://my-comfy.example.com or http://192.168.1.100:8188
object
Custom HTTP headers to include when communicating with your runner. Use this for authentication or other custom headers. Optional - can be an empty object if no headers are needed.Example: {"Authorization": "Bearer token123", "X-Custom-Header": "value"}
string[]
Array of tags for organizing and selecting runners (maximum 10 tags). Tags are used to match runners with workflows. Optional - can be an empty array.Example: ["production", "gpu-a100", "image-generation"]

Response

string
required
Unique identifier (UUID) for the runner.
string
required
UUID of the user who owns this runner.
string
required
The runner’s name.
string
required
Current status of the runner. Values: active, disabled
string
required
The URL where the runner is accessible.
string[]
required
Array of tags associated with the runner.
object
required
The custom headers configured for this runner.
string
required
ISO 8601 timestamp when the runner was created.
string
required
ISO 8601 timestamp when the runner was last updated.

Example Response

Example with empty headers and tags:

Error Responses

error
Bad request - validation error in the request body.Common causes:
  • Name is empty or too long
  • Invalid endpoint URL format
  • Too many tags (max 10)
  • Invalid headers format
error
Unauthorized - invalid or missing authentication token.
error
Forbidden - runner limit exceeded for your tier.

Notes

  • Runners are created with active status by default
  • The endpoint URL must be reachable from ComfyControl’s infrastructure