The Stable Audio 1.0: Text to Audio workflow offers a groundbreaking approach to generating audio content from text prompts. Utilizing the powerful Stable Audio model, this workflow transforms simple textual descriptions into rich, dynamic audio experiences. The process leverages advanced nodes like KSampler and CLIPTextEncode to accurately interpret text and generate corresponding audio textures. This workflow is perfect for those looking to explore creative audio production without the need for extensive technical expertise. By using the CLIPLoader and VAEDecodeAudio nodes, users can expect high-quality audio outputs that capture the essence of their textual inputs. Whether it's creating ambient soundscapes or electronic dance music, the possibilities are vast and exciting. Furthermore, with tools like the MarkdownNote and SaveAudioMP3 nodes, users can easily annotate and save their audio creations for future use, making this workflow a versatile and valuable asset for creators.
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 "Stable Audio 1.0: Text to Audio" (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("audio_stable_audio_example_api.json");
wf.setInput("6", "text", "heaven church electronic dance music"); // CLIPTextEncode
const job = await client.run(wf);
await job.getOutputs("19")[0].toFile("output.png"); // SaveAudioMP3The 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
