Chapter 2 — Generate a Workflow¶
Your first hands-on chapter. By the end, you'll be able to take an existing workflow file (.nbflow) and produce finished videos from it — no scripting, no prompt writing, just running and reviewing.
This is the easiest task in the pipeline. Get comfortable here before moving to variants and creating from scratch.
Chapter at a glance¶
flowchart LR
A[Set up<br/>G-Labs + tunnel] --> B[Open<br/>.nbflow]
B --> C[Run<br/>nodes]
C --> D[Review<br/>candidates]
D --> E[Rerun<br/>any failures]
E --> F[Export<br/>final clips]
A single workflow run from open to export — the minimum loop.
What you'll learn¶
- How to start the G-Labs backend and a cloudflared tunnel
- How to load an existing
.nbflowfile into PatchWork - How to run the Generation Runner
- How to review candidates in PatchWork and pick the best ones
- How to rerun individual nodes when something didn't land
- How to handle B-roll (which runs separately from the main
.nbflow) - How to export final assets for post-production
Before this chapter¶
Read Chapter 1 — Foundations. You should know what a workflow is, what a prompt is, what PatchWork is, and who the agents are before starting here.
Sections¶
- Setup & per-session checklist — get G-Labs and the tunnel running
- G-Labs Setup — the local backend in detail
- Cloudflared Tunnel Setup — quick tunnels (per-session) + named tunnels (permanent URL)
- PatchWork overview — the tool you'll be using
- PatchWork node types — every node type you'll see
- Running a workflow manually through PatchWork — click through the graph node by node
- Reviewing in PatchWork — pick candidates, navigate tabs
- Rerunning failed nodes — re-roll seeds, edit prompts, single-node reruns
- Manual B-roll generation — B-roll runs separately from the
.nbflow - Exporting final assets — handoff to post-production
Automation comes later
Once you understand manual generation, Chapter 13 introduces the Generation Runner agent — the automated executor that does all of this in one shot. Learn manual first; automation will make sense after.
Try this¶
Pick an existing approved workflow (e.g. one from projects/{month}/{brand}/{growth|sales}/approved/) and run it end-to-end.
Steps:
- Start G-Labs locally + start a cloudflared tunnel (G-Labs + cloudflared)
- Open the
.nbflowin PatchWork. Set the G-Labs URL in PatchWork's settings to the tunnel URL - Walk the graph node by node (Running a workflow manually). For each generation node, click Run, wait for candidates
- In each Approve gate, pick the strongest candidate (Reviewing in PatchWork)
- If any node didn't produce something usable, re-run it (Rerunning failed nodes)
- Export the final clips (Exporting final assets)
If you hit:
- G-Labs won't connect / tunnel URL not accepted → G-Labs + cloudflared
.nbflowwon't import / shows red errors → Chapter 14 — PatchWork import bugs- All 4 candidates have the same issue → mark it and read Chapter 5 — Prompt Tuning before re-rolling
- One node failed but the rest worked → Rerunning failed nodes
- Output looks wrong but you can't articulate why → Reviewing in PatchWork
When you're ready¶
→ Next: Chapter 3 — Lvl 1-2 Variants. Take a finished workflow and produce a variation of it — a dialogue swap or a wardrobe change. Low risk, auto-approved.