Short answer: Drop the "OpenAI → Edit 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 |
|---|---|---|---|
Image URL or base64 image_url | string | Required | Source image (PNG, max 25MB) |
Mask URL (optional) mask_url | string | Optional | PNG mask — transparent areas are edited |
Prompt prompt | string | Required | Add a sunset behind the mountain |
Model model | options | Optional | Model. Options: gpt-image-1 (best), dall-e-2 |
Size size | options | Optional | Size. Options: 1024×1024, 1536×1024, 1024×1536 |
Num Images n | string | Optional | Num Images |
{"image_url": "e.g. https://example.com/path","mask_url": "e.g. https://example.com/path","prompt": "Add a sunset behind the mountain","model": "{{trigger.model}}","size": "{{trigger.size}}"}
{"data": [{"url": "https://example.com/edited.png"}],"created": 1700000000}
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.