Short answer: Drop the "Runway → Runway Image to Video" 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 | Model. Options: Gen-4 Turbo, Gen-3 Alpha Turbo |
Image URL prompt_image | string | Required | https://example.com/image.jpg |
Prompt (optional motion description) prompt_text | string | Optional | Prompt (optional motion description) |
Duration duration | options | Optional | Duration. Options: 5s, 10s |
Aspect Ratio ratio | string | Optional | Aspect Ratio |
{"model": "{{trigger.model}}","prompt_image": "https://example.com/image.jpg","prompt_text": "{{trigger.prompt_text}}","duration": "{{trigger.duration}}","ratio": "{{trigger.ratio}}"}
{"id": "task-abc123"}
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.