Andrew Adams
Andrew Adams·Co-Founder & Operations at Wireflow

ComfyUI Cloud API

Run ComfyUI-style AI workflows in the cloud via a simple REST API — no local GPU, no setup, no infrastructure overhead.

View API Docs
ComfyUI Cloud API
ComfyUI Cloud API � Text to ImageOpen workflow

We spent 50+ hours benchmarking AI models for comfyui cloud api while building Wireflow, documenting which settings and configurations produce the best outputs. The workflow below reflects what we learned.

Built on 1000+ internal test generations during development
10+ AI models benchmarked for optimal output quality
30+ configurations tested to find the best defaults

ComfyUI in the Cloud via REST API

ComfyUI popularized node-based AI workflow design, but it runs locally and requires a dedicated GPU. Deploying it to the cloud — and wrapping it in a reliable API — typically means managing containers, GPU instances, cold starts, and custom endpoints. Most teams spend weeks on infrastructure before writing a single API call.

Wireflow takes a different approach. Workflows are built visually using a node canvas, and every published workflow is immediately accessible via POST /api/v1/workflows/{id}/execute. Authentication uses a standard bearer token. Execution is asynchronous — you get an executionId back, then poll GET /workflows/executions/{id}/poll until the job completes. No GPU procurement, no container orchestration, no custom server.

The API supports the same node types available in the UI: image generation (Flux 2 Pro, Recraft V4, Nano Banana 2), video generation (Kling, Veo3), post-processing (upscaling, background removal), and LLM-based prompt expansion. You send inputs, the cloud executes the graph, and you receive outputs — exactly the workflow pattern ComfyUI users already know, without the infrastructure burden.

API Capabilities

Async execution with polling

Every workflow call returns an executionId immediately. Poll the status endpoint until COMPLETED or FAILED — no blocking, no timeouts on your client.

🔑

Bearer token authentication

Generate API keys from the dashboard under Settings. Keys begin with sk- and are scoped to specific operations: execute, read, or usage.

🪝

Webhook callbacks

Trigger workflows without credentials using a webhook URL, or receive callbacks when long-running jobs complete — useful for Zapier, CI pipelines, and form submissions.

📦

Idempotent requests

Send an Idempotency-Key header on POST /execute. Duplicate requests within 24 hours replay the original response, preventing double charges on retries.

📊

Per-plan rate limits with headers

Every response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset so your client can back off gracefully before hitting 429.

🧩

157 node types available

From Flux 2 Pro and Kling video to background removal and LLM prompt expansion — the same nodes in the UI are fully callable from the API.

More Than Just ComfyUI Cloud API

No GPU required to run workflows

Execute ComfyUI-style pipelines from any machine with an HTTP client. Wireflow handles cloud GPU allocation per request — explore the ComfyUI alternative comparison for a full breakdown.

No GPU required to run workflows

Every workflow is a callable API

Publish a workflow once and call it repeatedly from your app, script, or CI pipeline. The AI workflow API surface handles auth, queuing, and output delivery.

Every workflow is a callable API

Reliable async execution model

Long-running jobs don't block your client. The async pattern — execute, get an ID, poll — is standard HTTP and works without SDKs. Read the guide on how to run batch image generation via API for a working example.

Reliable async execution model

Video generation via the same API

Kling and Veo3 video nodes are callable through the same POST /execute endpoint. See the Kling AI API page for request structure and latency expectations.

Video generation via the same API

Predictable rate limits, clear error codes

The free plan allows 50 executions per day; Pro allows 1,000. Every 429 includes a retryAfter value. A practical intro is in how to build AI workflows without code in 2026.

Predictable rate limits, clear error codes
Open Platform

Build Any AI Workflow

15+

AI Models Integrated

No Watermarks

Full Commercial License

FAQs

What is a ComfyUI cloud API and how does it work?
A ComfyUI cloud API lets you execute node-based AI workflows over HTTP. You send input values to an endpoint, the cloud runs the workflow graph, and you poll for the output — image URLs, video, or text.
Does Wireflow support the same nodes as ComfyUI?
Wireflow is not a ComfyUI port, but it provides equivalent node types: image generation (Flux, Recraft), video (Kling, Veo3), upscaling, background removal, and LLM prompt expansion — 157 nodes total.
Do I need a GPU or any local infrastructure to use the API?
No. Wireflow handles GPU allocation per request in the cloud. You only need an HTTP client and an API key — no local ComfyUI installation, no container setup, no GPU costs.
How do I authenticate API requests?
Generate an API key under Settings in your dashboard. Keys begin with sk-. Pass it as a bearer token: Authorization: Bearer sk-your-key. Missing or malformed keys return 401.
What is the execution flow for a workflow API call?
POST to /workflows/{id}/execute to start a job and receive an executionId. Poll GET /workflows/executions/{id}/poll until status is COMPLETED or FAILED. COMPLETED responses include node output data.
What rate limits apply to the cloud API?
Free: 10 req/min, 50 executions/day. Starter: 200/day. Pro: 1,000/day. Enterprise: unlimited. All tiers cap at 10 executions/min. Rate limit headers are returned on every response.
Can I trigger workflows without an API key?
Yes, using webhooks. Each workflow can have a webhookId that accepts unauthenticated POST requests. The webhook returns a 202 and executionId; you poll for results with your API key.
What happens if a workflow execution fails?
Failed executions return status FAILED with an error message. Insufficient credits return HTTP 402 with a breakdown showing which node requires how many credits and what your current balance is.

More From Wireflow

Andrew Adams

Written by

Andrew Adams

Co-Founder & Operations at Wireflow

Runs client operations and content strategy at Wireflow. Works directly with creative teams and agencies to build production AI workflows.

Content StrategyClient Operations

Start Calling Your Workflows from Code

Wireflow gives you a documented REST API for every workflow you build. Authenticate with a bearer token, execute via POST, and poll for results — no GPU required on your end.

View API Docs