Short answer: Drop the "Straico → Straico 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 |
|---|---|---|---|
Model model | options | Required | Single Straico image-model slug. This is one string, not an array (Chat Completion uses `models` as an array, but Image Generation takes ONE model). Slug list curated from Straico's catalog as of May 2026; if a new model appears in Straico, fetch the latest via List Models. |
Prompt description | string | Required | Text description of the image to generate. |
Size size | options | Optional | Aspect ratio of the generated image. |
{"model": "{{trigger.model}}","description": "e.g. A photorealistic golden retriever puppy on a moss-covered log, soft morning light","size": "{{trigger.size}}"}
{"data": {"zip": "https://straico-cdn.example.com/.../images.zip","price": {"total": 0.04},"images": ["https://straico-cdn.example.com/.../image-1.png","https://straico-cdn.example.com/.../image-2.png"]},"success": true}
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.