A one-person content pipeline: agent drafts, n8n schedules, Remotion renders
Build an automated content pipeline on one Mac: an agent drafts, n8n schedules, Remotion renders video, all local, all free, no subscriptions.
A one-person content operation can run a real pipeline — draft, schedule, render, publish — without a stack of subscriptions. The trick is putting the pieces in one place: an agent that drafts, n8n that schedules, and Remotion that renders video, all running locally in ReDock (free, no terminal). This is a workflow guide about what such a pipeline lets you ship on a regular cadence, not a passive-income pitch. There are no numbers here because the honest version doesn’t have any — just a repeatable system.
What “pipeline” means for one person
For a solo creator, a pipeline is less about scale and more about not dropping the ball. The recurring work of publishing — writing, formatting, scheduling, making the companion clip, remembering to post — is where consistency dies. A pipeline turns that from willpower into a system:
- Draft the post or script.
- Render a companion video from the same source.
- Schedule the publish so it goes out whether or not you’re at the desk.
- Publish to your site.
ReDock runs all three engines as local sites side by side, which is what makes wiring them together practical rather than a five-SaaS integration project.
The three engines
The agent drafts. ReDock’s whole surface is MCP tools on localhost:47200, so Claude Desktop, Claude Code, Cursor, or the built-in agent can write directly into a WordPress site — draft a post, set its content, create the pages. If you’d rather avoid API keys, the local-LLM catalog runs a model on your Mac. What is MCP? covers the mechanism.
n8n schedules. n8n runs as one of your ReDock sites and handles the cadence — trigger on a schedule, transform data, call other steps, post when it’s time. Because it runs on your Mac, executions are unmetered; you’re not counting them against a monthly SaaS allowance. The n8n-on-a-Mac one-click guide covers getting it running.
Remotion renders. For the video leg, Remotion turns React code into an MP4 on Bun inside ReDock’s toolchain. This is programmatic video, not generative AI video — the agent writes the scene, Remotion renders deterministic frames. A reusable intro composition means every episode’s clip is a prop change, not a re-edit. See make YouTube videos without paid tools.
Wiring it together
The pipeline is n8n at the center calling the other two. A plausible flow:
- A schedule trigger fires each week.
- n8n hands the agent a topic; the agent drafts a WordPress post and saves it as a draft.
- The same source drives a Remotion render for the companion clip.
- n8n flips the post to published at the chosen time and surfaces the rendered file for upload.
You review before anything goes live — the pipeline drafts and schedules, you approve. Every ReDock change is visible and reversible, so an automated draft is never an unaccountable one. Setup for the agent side is at /docs/mcp, and the stacks each engine runs on are at /docs/stacks.
Why local-first is the right call here
A hosted pipeline meters you at every step: executions, render minutes, API calls. A one-person budget feels each of those. Local-first removes the meters — your Mac is hardware you own, and n8n executions plus Remotion renders cost time, not credits. Every runtime installs into ReDock’s own toolchain, never onto macOS, so uninstalling leaves your Mac clean.
The honest trade-off: your Mac has to be awake for scheduled jobs to run, and you’re your own ops team. For a solo publisher, that’s usually the right trade — you control the whole thing and pay nothing to run it.
Where this fits
This post is the “wire it all together” chapter of the $0 creator stack. If you’re starting from nothing, start a site with no money is the on-ramp, and when a piece is ready to be public, deploy a website for free takes it to Cloudflare Workers.
FAQ
Does the whole pipeline really run on one Mac?
Yes. The agent, n8n, and Remotion all run locally in ReDock as sites side by side. The only external touch is publishing or deploying, which use Cloudflare’s free tiers.
Will it publish things without me checking?
Only if you design it that way. The recommended pattern is draft-and-schedule with a human approval step — the agent drafts, n8n schedules, you review before it goes live. Every change is reversible.
Is the video part AI-generated footage?
No. Remotion renders video from React code the agent writes — deterministic and repeatable. It’s programmatic video, not a text-to-video model.
Ready to run your pipeline on your own Mac? Download ReDock.