Free scheduling with n8n: post everywhere while you sleep

Free scheduling automation means an n8n workflow with a cron trigger, a queue of content, and a node per destination — running on your own Mac instead of a metered cloud plan. Self-hosted n8n has no execution limits and no per-task pricing, and ReDock gets it running in one click. The result: posts go out on schedule, and the bill stays at zero.

The anatomy of a scheduling workflow

Every scheduler, paid or homemade, is the same three pieces:

1. A queue. Somewhere your upcoming content lives — a Google Sheet, an Airtable base, a Notion database, or n8n’s own data store. Each row: text, optional media link, target platform, publish time.
2. A trigger. n8n’s Schedule Trigger node fires on a cron expression. Every 15 minutes is a sensible default: the flow wakes up, checks the queue for anything due, and goes back to sleep.
3. Dispatch nodes. One branch per destination. n8n ships nodes for most major platforms, and a generic HTTP Request node covers anything with an API.

That’s the whole machine. A Switch node routes each due item to the right branch, a final node marks the row as posted, and an error branch pings you if a platform rejects something.

Setting it up on your Mac

If you already have n8n running, skip ahead. If not, the fastest path is the one in n8n on your Mac, one click: ReDock — a free (alpha) native macOS app — runs n8n as a built-in stack with a real HTTPS .test domain and no Docker or terminal setup. Install steps live in the install docs.

Once n8n is up:

1. Create a new workflow and add a Schedule Trigger (*/15 * * * *).
2. Add a node to read your queue and filter for items where publish_at <= now and status = queued.
3. Add a Switch on the platform field, with one posting branch per destination.
4. Close the loop: mark the item posted, and route failures to a notification.

Building the queue itself — and deciding what counts as a platform worth automating — is covered in more depth in build your own free social media scheduler.

The honest constraints

Two things a homemade scheduler makes you deal with directly.

Your Mac must be awake. A cron trigger can’t fire on a sleeping laptop. If you schedule posts for 3 a.m., either keep the machine awake or shift your publish times into hours it’s on. For most people, “posts go out during my workday, queued the night before” covers the real need.

Platform APIs have rules. Each network has its own OAuth dance, rate limits, and content policies. n8n’s credential system stores tokens in your local instance — they never sit on a third-party scheduler’s servers, which is a genuine privacy win of self-hosting.

Some platforms confirm posts via callback rather than a synchronous response. That’s a webhook, and it can reach your laptop through ReDock’s Cloudflare tunnel — the mechanics are in webhooks on localhost.

Where this beats a paid scheduler

• Cost. Zero, at any volume. Paid tools meter by posts, profiles, or seats.
• Ownership. The workflow is a JSON export you can version, copy, and modify. No feature is behind a higher tier.
• Extensibility. Your scheduler can do things no SaaS offers: pull the day’s post from your WordPress drafts, run text through a local model first, or generate an image variant per platform. It’s a workflow, not a product — you can keep adding nodes.

And if writing the queue is the part you’d rather delegate, an agent can plan and load it for you — that’s AI scheduling.

FAQ

Is this actually free, or free-with-asterisks?

The software is free: n8n’s fair-code license permits free self-hosting, and ReDock is free. The only real costs are the ones every scheduler has — some platform APIs have paid access tiers.

How many posts can I schedule?

There’s no imposed limit. Self-hosted n8n doesn’t meter executions, so the queue can hold ten posts or ten thousand; the constraint is platform rate limits, not your tooling.

What happens if my Mac is asleep at publish time?

The trigger doesn’t fire until the machine wakes. A common pattern is a catch-up filter — “anything due in the last 12 hours and still queued” — so late items post on wake instead of silently dropping.

---

A scheduler is a queue, a clock, and a loop — and you can own all three. Download ReDock and build yours this week. New here? Start with the first site guide.