Recipe·4 workflows

Storyboard to Trailer

Name: NodeTool
Author: NodeTool

A logline becomes a beat sheet, a numbered shot list, a cut teaser, and a score under it.

For: Directors, agencies, and anyone pitching a film that does not exist yet.

Download all 4 workflows Download NodeTool

What it produced

Not a mockup. The chain below was run end to end and this came back. The list under the caption is every model that ran: green where it is the model the workflow names, reached through whichever provider this render held a key for, blue where a better one was chosen deliberately, and amber where a different model had to stand in — each with the reason.

Output from running the Storyboard to Trailer recipe — One logline — a lighthouse keeper finds a message in a bottle dated forty years from now — through steps three and four: five shots directed, rendered, animated, cut, and scored. The first two steps produce documents, so they are not in the picture; the style bible holding these five together is written in step three.

The two text steps come first because they are the ones you will rewrite. A beat sheet and a shot list are cheap to redo and expensive to skip — prose cannot be iterated over by a generation pipeline, numbered shots can.

Only the third step spends. It runs each shot through a video model metered per second, which is why the two documents in front of it are worth arguing over first.

Keys this chain needs

Read out of the workflows themselves, so this list is what the graphs actually call. You bring the keys and pay each provider directly — NodeTool takes no cut and adds no markup.

OpenAI
OPENAI_API_KEY
Google Gemini
GEMINI_API_KEY
Kie
KIE_API_KEY
fal.ai
FAL_API_KEY

The chain, in order

01
Write the structure before buying footage
In: the premise. Out: hook, escalation, turn, title card. The shape a trailer needs, settled while it still costs one text call to change.
gpt-5-mini
Trailer Beats from a Premise — see the graph
02
Turn prose into something a pipeline can walk
In: the synopsis. Out: numbered shots with framing and duration. This is the document the next step iterates over.
gpt-5-mini
Shot List from a Synopsis — see the graph
03
Film it and cut it
In: the logline. Out: a cut teaser. A Director node writes the storyboard and one style bible, each shot becomes an image prompt, and the frames are rendered, animated, and assembled. The per-second video model is the expensive step.
gemini-3.1-pro-previewgpt-image-2-text-to-imageveo-3.1-generate-preview
Movie Trailer Generator — see the graph
04
Put music under it
In: the cut and a mood. Out: a bed written to the clip's own length, mixed under the original audio. One audio generation per run.
fal-ai/stable-audio-25/text-to-audio
Score a Silent Clip — see the graph

What it does not do

Steps three and four both hold their own storyboard. Rewriting the beat sheet does not reach back into a teaser you already rendered — re-run the chain.
Continuity across shots comes from a shared style bible, not from a persistent character model. Faces drift over a long cut.
For a rough cut you can keep editing rather than a finished teaser, swap step three for Directed Film to Timeline, which ends in an editable sequence.

Running it

01
Install Studio
The desktop app is free and runs on your own machine. No account is needed to open a workflow.
02
Import the bundle
Open the command menu and choose Import Workflow as Bundle. All the workflows in this recipe land in your library at once.
03
Add your keys
Paste each key above into Settings. Studio stores them in your OS keychain and sends them only to that provider.
04
Run the chain
Work down the list. Each step takes what the one before it produced, so you can stop and change your mind at any point.