Short answer: Drop the "Runway → Runway Text 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 (fast), Gen-4 Aleph, Gen-3 Alpha Turbo |
Prompt prompt_text | string | Required | e.g. A cinematic drone shot over a forest |
Duration (sec) duration | options | Optional | Duration (sec). Options: 5, 10 |
Aspect Ratio ratio | options | Optional | Aspect Ratio. Options: 16:9 Landscape, 9:16 Portrait, 1:1 Square |
{"model": "{{trigger.model}}","prompt_text": "e.g. A cinematic drone shot over a forest","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.