Watch the video with chapters & transcript →
AUTOMATION
In short: Sora 2's API can be called from an n8n HTTP Request node with OpenAI header authentication — "Bearer", a space, then your API key — and it works from Europe without a VPN.
Sora 2 now has a public API, which means video generation can be wired into an n8n workflow and triggered from a simple form — no code required. Ani Björkström, a tech consultant based in Stockholm, built exactly that: a workflow that takes a prompt and a reference image, sends them to Sora 2, waits for rendering, and downloads the finished MP4, ready for TikTok or YouTube Shorts.
The form collects exactly the parameters listed in Sora 2's API documentation: the prompt, the model, the video size, the length in seconds, and an input reference image. The documentation is the single source of truth for what to build. The prompt uses a text-area field so longer descriptions fit, the size is a dropdown, and the length is set to 8 seconds. Only specific image file types are accepted as reference files, which is why the form restricts uploads to those formats.
The HTTP Request node uses generic header authentication: the form presents an API key that Sora 2 checks against your profile on the OpenAI platform. The value must be written as "Bearer", then a space, then the key — not the key alone. You also need credits loaded on the platform, even one or two dollars, because Sora 2 is a paid offering. Saving the credential in n8n means every future OpenAI workflow can reuse it.
Because video creation is not instant, the API first returns a status rather than a video. The switch node routes each status to the right action instead of assuming the clip is done.
| Status | Meaning | Workflow action |
|---|---|---|
| Queued | Video accepted, waiting to start | Wait one minute, check again |
| In progress | Rendering has begun but is unfinished | Wait one minute, check again |
| Completed | Video is ready | Download the MP4 via a GET request |
| Anything else | Something went wrong | Return an error so it appears in the logs |
One detail matters: when passing the reference image to the HTTP node, use the binary reference — typing the form field's name — rather than dragging the image value from the form output. Sora 2 requires the binary format; the drag-and-drop shortcut silently produces the wrong input.
Check that your image's dimensions exactly match the size parameter before submitting. If they differ, Sora 2 rejects the request with a size-mismatch error, because the picture is used as the opening scene. Open the file's properties locally to read the dimensions, and use a simple tool such as the Windows snipping utility to resize it.
The consumer product is only open in the US and Canada, requiring a VPN and an invite code. The API has no such restriction — this workflow runs from Stockholm with no VPN.
Yes. Sora 2 is highly censored and does not allow the use of various characters, so plan prompts accordingly.
Yes — like the video and leave a comment, and the workflow template is sent to you at no cost.
Read the full video transcript, with chapters, on the video page →
Want this working inside your finance team?