
Your solo creator content workflow has two halves. Automate one.
A solo creator content workflow splits into human judgement hours and machine render work. Hand the render half to FFmpeg Micro as one API call. Free tier.
73 articles about automation.

A solo creator content workflow splits into human judgement hours and machine render work. Hand the render half to FFmpeg Micro as one API call. Free tier.

Most n8n automation ideas lists are beginner text workflows. If yours already run, the next one to build is the media step n8n can orchestrate but not execute.

Unverified n8n 3.0 community nodes stop loading, including every local-FFmpeg node. Use the env-var stopgap, or replace the video step with one HTTP call.

n8n execution crashed with startedAt null is a 2.45.0 queue mode race, not your workflow. Fix: upgrade to 2.45.1+, then stop blocking the worker event loop.

n8n Convert to File base64 writing a corrupt video? The data URI prefix shifts every byte. The 2.45.0 fix, a Set node workaround, and the safer pattern.

The n8n 3.0 breaking changes that kill FFmpeg steps: the 60-second task timeout, Docker-only self-hosting, Compression caps, and removed nodes, in fix order.

Black Friday is Nov 27. Produce bulk video ad variants from one master clip: burn hook text with FFmpeg drawtext, then reframe to 9:16, 1:1, 4:5 and 16:9.

A TikTok Shop Black Friday video ships as four formats, three hooks and burned captions. The dated calendar, FFmpeg commands, and one API call per format.

n8n 3.0 breaking changes that kill a self-hosted FFmpeg workflow: removed binary file nodes, a 60-second runner timeout, a 256 MiB cap, and what to change.

"No usable ffmpeg was found" in n8n means the server has no FFmpeg binary, and n8n's installer makes it impossible for a community node to ship one. Three real fixes.