
This workflow demonstrates style-controlled image generation with Recraft inside ComfyUI. It centers on RecraftTextToImageNode for raster image synthesis and uses dedicated style selector nodes—RecraftStyleV3LogoRaster, RecraftStyleV3DigitalIllustration, and RecraftStyleV3RealisticImage—to quickly switch aesthetics without rewriting prompts. RecraftColorRGB lets you lock brand hues, while RecraftControls aggregates global parameters that the generator uses to keep outputs consistent. Results are saved via SaveImage, and MarkdownNote provides in-graph guidance.
For brand-ready deliverables, the optional Convert into SVG (need credits) group routes raster outputs through RecraftVectorizeImageNode and exports clean vectors using SaveSVGNode. This is especially useful for logos and flat graphics that need to scale. Note: in these Recraft nodes, the seed value only determines whether the node should re-run; it does not make results deterministic. To explore new variations, change the seed to trigger a fresh run or refine the style and color inputs.
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.
Run it from TypeScript or Python with the Comfy SDK. The same code targets Comfy Cloud or a ComfyUI you host yourself — only the base URL changes.
// Install (beta)
npm i @comfyorg/sdk
// Run "Recraft: Style Control Image Generation" (TypeScript)
import { Comfy } from "@comfyorg/sdk";
const client = new Comfy({ apiKey: "comfyui-..." });
// This workflow, exported in API format (see note below)
const wf = await client.workflows.fromFile("api_recraft_image_gen_with_style_control_api.json");
const job = await client.run(wf);
await job.getOutputs("26")[0].toFile("output.png"); // SaveSVGNodeThe SDK takes a workflow in API format: open this workflow in ComfyUI and use File → Export Workflow (API).
Comfy Cloud API access requires a plan with an API key.
FAQ













