Short answer: Drop the "fal.ai → Run fal.ai Model" 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 ID model_id | string | Required | fal model id |
Prompt prompt | string | Required | Prompt (required) |
Image Size image_size | string | Optional | Image Size |
Num Images num_images | string | Optional | Num Images |
{"model_id": "e.g. fal-ai/flux/schnell, fal-ai/flux-pro/v1.1, fal-ai/runway-gen3","prompt": "{{trigger.prompt}}","image_size": "{{trigger.image_size}}","num_images": "{{trigger.num_images}}"}
{"status": "IN_QUEUE","request_id": "req-abc123","status_url": "https://...","response_url": "https://..."}
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.