Platform Settings
Enable platforms and set default content types in Settings → Platforms.
Platform settings live in Settings → Platforms. Here you control which platforms are active and what content type each platform uses by default.
Enabling platforms
Toggle platforms on or off. Disabled platforms are excluded from calendar slot generation: if you disable LinkedIn, no LinkedIn slots will be created and no LinkedIn content will be generated.
Plan limits:
- Starter: up to 2 platforms
- Pro / Team / Lifetime: up to 10 platforms
Default content types
Each platform has a default content type that's used when creating calendar slots.
| Platform | Available content types | Notes |
|---|---|---|
| X (Twitter) | x-post, x-thread | Threads require Postiz to publish as a thread sequence |
linkedin-post | Single format | |
| Farcaster | farcaster-cast | Single format |
| Paragraph | paragraph-essay | All plans; publishes via Paragraph API |
You can mix content types per platform by creating separate calendar slots. For example, X threads on Monday/Wednesday/Friday and X posts on Tuesday/Thursday.
Platform-specific constraints
x-post: ≤280 characters. Borker counts characters during generation and trims if needed.
x-thread: No hard length limit per thread, but individual tweets in the thread must be ≤280 characters. Borker generates the thread in the 1/ tweet\n\n2/ tweet format. Postiz handles posting each tweet in sequence.
linkedin-post: 150–300 words recommended. LinkedIn doesn't enforce a strict word limit (3,000 character limit on posts), but engagement drops sharply on very long or very short posts. Borker targets 200 words as the default.
LinkedIn suppresses reach on posts with external links. Best practice: put any links in the first comment, not the post body.
farcaster-cast: ≤320 characters. Borker generates casts for a web3-native audience and adjusts technical depth upward automatically.
paragraph-essay: 600–1,200 words. Structured as a proper blog post with intro, headers, and conclusion. Requires a Paragraph API key. Published directly via Paragraph API, not through Postiz.
Connecting social accounts
Borker doesn't directly connect to your social accounts. Postiz does. Before scheduling content to a platform, make sure you've connected that platform's account in your Postiz dashboard.
If you schedule content to X in Borker but haven't connected an X account in Postiz, the post will sit in Postiz's queue but fail to publish.
Always verify platform connections in Postiz after enabling a new platform in Borker. The preflight check won't catch a missing Postiz platform connection: it only validates the API key.