Runway Aleph (Video Edit): Runway action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Source Video URI video_uri	string	Required	Source Video URI (required)
Edit Prompt prompt_text	string	Required	make it sunset, add cinematic grading
Aspect Ratio ratio	string	Optional	Aspect Ratio

Sample request

{
  "video_uri": "{{trigger.video_uri}}",
  "prompt_text": "make it sunset, add cinematic grading",
  "ratio": "{{trigger.ratio}}"
}

Returns

{
  "id": "task_abc"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Runway Aleph (Video Edit).

What does the Runway Aleph (Video Edit) action do in Runway?

Takes a source video plus an edit instruction. Aleph preserves the source while applying the requested change ("change the season to winter", "remove the person on the left"). For programmatic video editing workflows.

What inputs does Runway Aleph (Video Edit) require?

Required: Source Video URI, Edit Prompt. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Runway returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Runway Aleph (Video Edit) support batch operations?

Yes. Run Runway Aleph (Video Edit) inside a Loop node to process arrays. Tiny Command handles Runway's rate limits automatically so you don't have to throttle manually.

More actions