Social publishing · part of the n4n fleet
Compose once. Publish once.
Write a post, pick the accounts, send it now or schedule it. n4n Social publishes to every account you have linked — and is built so that a server dying halfway through can never turn one post into two.
7 platforms · threads · scheduling · one login across the n4n fleet
Shipping the new routing dashboard today. Here is what changed →
Shipping the new routing dashboard today. Here is what changed →
Weekly digest: what the fleet shipped this week.
Reddit AMA announcement — r/selfhosted
the queue, as your team sees it
Why this exists
A post cannot be unsent.
Most scheduling tools treat a failed send like a failed email: retry it and move on. But a duplicate email lands in one inbox, while a duplicate post is public, permanent, and the first thing your audience sees. So n4n Social treats the two cases as completely different problems.
We never guess
If a worker dies mid-publish, the post is not sent again on a hunch. It moves to a state that means we do not yet know what happened.
We go and look
Where the platform can tell us what you recently posted, we ask it. If the post is already there, we record it and stop. If it is genuinely absent, we send it.
And we admit it
When a platform gives us no way to check, we stop and say so plainly rather than risk a duplicate. A person decides. That is the honest answer, so it is the one we give.
How it works
Four steps, then it runs itself.
- STEP 01
Link your accounts
Connect each platform once. Your tokens are held by n4n Connect, the fleet's connector — n4n Social never stores a platform credential of its own.
- STEP 02
Write the post
One composer for every account. Leave a blank line to start a new part and it becomes a thread wherever threads exist.
- STEP 03
Get told immediately
Anything a platform will refuse is refused while you are still looking at it — not silently at 3am. Every problem at once, so you fix them in one edit.
- STEP 04
Send or schedule
Publish now, or pick a time. The queue shows each account separately, with a link to the live post the moment it lands.
Platforms
Seven platforms, and their real limits.
These are the exact limits the composer enforces. We would rather you know before you sign up than discover it in a failed post.
X posting
X goes out through your own browser.
X's write API is priced in a way that makes routine scheduled posting uneconomic for a small team. So instead of billing you for it, n4n Social drives a Chrome profile you are already signed into — through n4n Connect, the same paired-browser machinery the rest of the fleet uses.
It checks it is on the right account before it types a single character, and it writes the post the way you would.
What it cannot do
A driven browser can only upload a file that already exists on that machine — and your media lives on our servers, not yours. There is no route between the two, soX posts are text only.
The composer refuses an X post with media attached, at the moment you attach it. We would rather say this on the pricing page than in a 3am failure.
every other platform · media supported
One account
It already knows who you are.
n4n Social signs in with the same n4n account as every other app in the fleet — the AI gateway, hosting, mail, the team console. One login, one balance, one place your workspace lives.
See the whole n4n fleet →Your tokens stay put
Every platform token, OAuth grant and refresh belongs to n4n Connect. n4n Social holds one sealed key and nothing else.
Revoke in one place
Disconnect an account in Connect and this console loses it immediately — there is no second copy to forget about.
Pricing
Included with your n4n account.
n4n Social has no separate subscription. Sign in with your n4n account and start publishing; if you later use paid fleet services, they draw on the same prepaid balance you already have.