Free social media scheduler: build your own with n8n in an afternoon
Skip the monthly SaaS bill, build a self-hosted social media scheduler with n8n on your Mac using ReDock, with real HTTPS and no terminal.
You can build a free, self-hosted social media scheduler in an afternoon using n8n running on your Mac. Instead of paying a SaaS tool per month to queue posts, you own the workflow: a spreadsheet or a folder of drafts feeds a cron-triggered n8n flow that posts to each platform’s API on schedule. ReDock ships n8n as a one-click stack with real HTTPS and webhook-ready tunnels, so there’s no Docker and no terminal between you and a running scheduler.
What “build your own scheduler” actually means
A scheduler is three moving parts: a place to hold queued posts, a trigger that fires on a schedule, and a step that publishes to each platform. n8n gives you all three visually. You drop a Cron node, a node that reads your queue (a Google Sheet, an Airtable, a local file, a WordPress custom post type), and one HTTP or platform node per destination.
The reason people pay for this is setup, not capability. Self-hosting n8n the usual way means Docker Compose, a reverse proxy for HTTPS, and a tunnel so OAuth callbacks work. ReDock — a free (alpha) native macOS app — collapses that into creating an n8n site. It warm-starts, gets an https://something.test domain with a trusted certificate, and can open a Cloudflare tunnel when you need public reachability.
The afternoon build
Here’s the shape of it, start to finish:
- Hold the queue. Pick where drafts live. A Google Sheet with columns for text, image URL, platform, and post time is the simplest. n8n reads rows where the time has passed and the status is empty.
- Trigger on a schedule. A Cron node every 15 minutes checks the queue. This is the whole “scheduler” — no magic, just a clock.
- Publish per platform. Each social API is an HTTP request with an auth token. n8n has nodes for common platforms and a generic HTTP node for the rest. The real HTTPS domain matters here because OAuth callbacks refuse plain
http://localhost. - Mark it done. Write the status back to your sheet so the same post doesn’t go out twice.
The OAuth step is where a .test domain with a real certificate earns its keep — see the stacks reference for how ReDock provisions it. Setup basics are in the install guide.
Why local-first is the right default here
A cloud scheduler holds your platform tokens on someone else’s server and meters you by post count or connected account. A self-hosted n8n keeps those tokens in your local instance and runs as many posts as your machine can handle at zero marginal cost. If you already run other automations, this is the same pattern covered in free scheduling with n8n and AI scheduling.
One honest limit: your Mac has to be awake for the cron to fire. For a solo creator or small team posting during working hours, that’s fine. If you need round-the-clock posting, the workflow exports as a JSON file you can move to a server later — same n8n, same flow.
Let an agent wire the tedious parts
The per-platform HTTP nodes are fiddly — auth headers, body shapes, rate limits. Because ReDock exposes its whole app as MCP tools on localhost:47200, you can have an agent draft those nodes for you. Describe “post this text and image to platform X,” and the agent proposes the request. The full pattern is in n8n + Claude via MCP, and ReDock’s built-in agent can do it with no API keys.
FAQ
Is this really free?
The software is. n8n’s fair-code license allows free self-hosting with no execution limits, and ReDock is free. Your only costs are whatever the social platforms charge for API access, which for most personal use is nothing.
Which platforms can I post to?
Any platform with an API. n8n has dedicated nodes for several, and its generic HTTP node covers the rest. You supply the auth token per platform; the workflow handles the timing.
What happens if my Mac is asleep at post time?
The cron won’t fire until the machine wakes. For scheduling during your working day that’s fine; for 24/7 posting, export the workflow JSON and run the same flow on a server.
Owning your scheduler means no per-post fees and no tokens on someone else’s server. Download ReDock and build it this afternoon.