Building a creative
Build, review, approve, render and download the results of a flow.
Building compiles the flow into creatives: one for every valid combination of your dimensions, content and media. Nothing renders until a human approves it.
Before the build: the rings
The editor checks the graph continuously:
- A red ring is an error that blocks building; the node's label says exactly what to fix (a missing template, an empty required field, an unconnected output).
- An orange ring is a warning; the build proceeds, but that node may be ignored (for example a node with no downstream connection).
If you click Build while red nodes remain, the build refuses and points you at them.
Build
Click Build (top right). The flow compiles server-side: dimensions multiply, gates and data prune impossible combinations, duplicates collapse, and any uncached AI work runs first behind a warm-up confirmation (see Using AI nodes).
The results land in the flow's Outputs table as creatives awaiting review, each row showing its name, platform and placement, market, language and version, and, once rendered, duration, dimensions and file size.
Review and approve
Nothing renders until you approve it:
- Approve one creative from its row menu (Approve), or
- Select several and use Approve (N).
Approved creatives move to Queued, then Processing and Rendering as the render engine picks them up, and finally Rendered.
Download and deliver
- Download a rendered creative from its row menu, or select several and use Download (N).
- Every rendered creative also appears on the Renders page, searchable across campaigns.
- Outputs piped to a Meta Ads or Google Ads node upload automatically after render, always as paused ads for a final check inside the platform.
Failures and re-builds
- A failed render shows Failed with the reason on its badge; other rows carry on unaffected. Fix the cause and approve again.
- Editing the flow and building again creates new rows for anything that changed; queued and rendered creatives are never overwritten.
- Closing the tab doesn't lose a build: server-side work completes in the background and you're notified when it's done.