Short answer: Drop the "Stability AI → Stability AI Generate Image" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Prompt prompt | string | Required | Text description of the image to generate |
Negative Prompt negative_prompt | string | Optional | What to exclude from the image |
Aspect Ratio aspect_ratio | options | Optional | Aspect Ratio. Options: 1:1 (Square), 16:9 (Landscape), 9:16 (Portrait), 4:3, 3:2, 21:9 (Ultrawide) |
Output Format output_format | options | Optional | Output Format. Options: PNG, JPEG, WebP |
Seed seed | string | Optional | Random seed for reproducible results. Leave empty for random. |
{"prompt": "e.g. A photorealistic sunset over mountains, 4K, dramatic lighting","negative_prompt": "e.g. blurry, low quality, text, watermark","aspect_ratio": "{{trigger.aspect_ratio}}","output_format": "{{trigger.output_format}}","seed": "e.g. 42"}
{"seed": 42,"image": "base64-encoded-image-data...","finish_reason": "SUCCESS"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.