ActionLuma AIUpdated September 2026
How do I retrieve a Luma generation result?
Short answer: You can get luma generation in Luma AI by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Luma AI Get Luma Generation action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 |
|---|---|---|---|
Generation ID generation_id | string | Required | Generation ID (required) |
Sample request
{"generation_id": "{{trigger.generation_id}}"}
Returns
{"id": "gen-abc123","state": "completed","assets": {"video": "https://example.com/v.mp4"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Get Luma Generation.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Get Luma Generation.
What does the Get Luma Generation action do in Luma AI?
Polls a generation by ID; returns the video URL once status is complete. Typical wait 30 seconds to several minutes depending on duration.
What inputs does Get Luma Generation require?
Required: Generation ID. 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 Luma AI returns an error?
The run history shows the failed step with its input and the error message Luma AI returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Get Luma Generation support batch operations?
Run Get Luma Generation inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Luma AI's rate limits.
More actions