How do I change the number of styles from 12 to more or fewer?

Duplicate or delete GrokImageEditNodeV2 → SaveImage branches as needed. Each branch represents one style prompt. Keep filename prefixes unique to prevent overwriting.

Do I need an API key or special setup for GrokImageEditNodeV2?

If your GrokImageEditNodeV2 relies on an external Grok service, you may need to configure credentials in the node or its settings. Check the node’s documentation or the node UI for any required keys or endpoints.

How can I control how strongly the style changes the image?

Use more or less assertive language in your prompt (e.g., "subtle film grain" vs. "heavy grain, high contrast"). If the node exposes a strength or similar control in your setup, lower it for gentler edits and raise it for bolder changes.

Why do some outputs look similar even with different prompts?

Overlapping style terms can converge to similar looks. Make prompts more distinctive, avoid repeating the same base descriptors, and vary seeds if available. Ensuring the input image has clear subject/background separation can also help.

1 input multiple styles from prompt

This ComfyUI tutorial shows you how to turn a single image into a gallery of 12 distinct styles using prompt-driven editing. The workflow is simple and fast: LoadImage imports your source, the image fans out to twelve GrokImageEditNodeV2 instances (each driven by a different style prompt and the Grok Imagine Quality engine), and each result is written to disk by a SaveImage node. The result is a quick style board that’s ideal for exploration, A/B testing, or presenting options to a client.

Technically, the graph duplicates the same input image across parallel branches. Each GrokImageEditNodeV2 applies the style instructions you provide (e.g., “watercolor sketch,” “cyberpunk neon,” “studio portrait retouch”) while preserving the core content and composition of the original. SaveImage nodes handle file naming and output paths so every variant is saved separately. Because each branch is independent, ComfyUI can schedule work efficiently, and the Grok Imagine Quality model is optimized for rapid, consistent edits—making it practical to generate a dozen variations in a single run.

API

Use this workflow from code

Every Comfy workflow is a JSON graph. The payload below is this workflow, exactly as ComfyUI runs it — fetch it from the URL, keep it in version control, or load it in ComfyUI and run it node by node.

GET https://comfy.org/workflows/download/1043317e75c9.json

Fetching workflow JSON…

Run it from Python or TypeScript with the Comfy SDK. The same code targets Comfy Cloud or a ComfyUI you host yourself — only the base URL changes.

# Install (beta)
pip install comfy-sdk        # Python
npm i @comfyorg/sdk          # TypeScript

# Run this workflow (Python)
from comfy_sdk import Comfy

client = Comfy(api_key="comfyui-...")
wf = client.workflows.from_file("workflow_api.json")
job = client.run(wf)
for output in job.get_outputs("<output-node-id>"):
    output.to_file(output.name)

The SDK takes a workflow in API format: open this workflow in ComfyUI and use File → Export Workflow (API). API access requires a Comfy Cloud plan with an API key. SDK docs · Get an API key

FAQ

Frequently Asked Questions

View all workflows