Social platforms
Social publishing in Postwright is how the video engine (free in Studio) and Pro’s social cadence reach your audience: twelve destinations you can post to, plus Substack Notes, which Postwright drafts for you to post by hand. Some need only a one-time browser login; others need API credentials or a token you set up once. All of them post from your own accounts – there’s no middleman.
Platform support
| Platform | Setup | How it connects |
|---|---|---|
| LinkedIn (personal + company) | Works out of the box | A one-time login in a browser profile Postwright keeps on your machine. No developer app, no API keys — you just log in once. |
| YouTube (long-form + Shorts) | Some setup | Uploads via the YouTube Data API. You create your own Google Cloud OAuth client (a Desktop app) and sign in once from the app. See Connections. |
| Facebook Page | Some setup | Meta Graph API. Needs a Meta app and a long-lived Page token (FB_PAGE_ID, FB_PAGE_ACCESS_TOKEN). |
| Instagram (Reels + feed) | Some setup | Meta Graph API on a Business/Creator account (IG_BUSINESS_ACCOUNT_ID + an access token). Tokens auto-refresh. |
| Threads | Some setup | Threads Graph API (THREADS_ACCESS_TOKEN + THREADS_USER_ID). Tokens auto-refresh. |
| Bluesky (Pro) | Some setup | An app password you create on Bluesky (never your account password), pasted with your handle into Connections. The post carries a clickable link and a link card. |
| Mastodon (Pro) | Some setup | An access token from your own server (Preferences, then Development), with its address. Works with any server that speaks Mastodon’s API. |
| Telegram, Discord, and Slack channels (Pro) | Some setup | Broadcasts that announce a blog post to a community. Telegram: a bot that is the channel’s admin. Discord: a channel webhook (nobody is pinged). Slack: your own Slack app’s bot token. None of the three lets an app read views or reactions, so they have no performance numbers. |
| X (Pro) | Some setup | Through your own X developer app, signed in once from Connections. X charges $0.20 for each post with a link, billed to your X developer account; Postwright shows a running estimate. Posts go through X’s API only, never a browser. |
| Pinterest (Pro) | Some setup | Through your own Pinterest app, which needs Pinterest’s approval (Standard access) before pins are public. Until then a Trial app can only pin to Pinterest’s sandbox, where only you see them, and those are never recorded as published. Each pin is the post’s public hero image on a board you pick, linking to the post. |
| Substack Notes (Pro) | Not supported | Postwright never posts to Substack. As of October 2026 it still has no API for individual developers, and automating its site isn’t allowed. Instead Postwright drafts the Note and hands it to you once the blog post is live, with a Copy button. You post it, paste its address back, and only then is it recorded as published. |
Not supported: TikTok, Reddit, and Medium. Postwright doesn’t post to them, and there’s no workaround to set up.
Why some use a login and others use APIs
Where a platform offers a clean publishing API (YouTube, Facebook, Instagram, Threads, Bluesky, Mastodon, X, Pinterest, and the channel broadcasts), Postwright uses it — that’s the most reliable path. LinkedIn doesn’t offer that for the kind of posting Postwright does, so it drives a real, logged-in browser session on your machine instead. Either way, posts go out as you, from your account.
Per-platform copy
Postwright doesn’t cross-post the same text everywhere. It drafts copy tuned to each connected platform — a LinkedIn post, a Facebook post, an Instagram caption, a Threads reply, a 300-character Bluesky post, a short X post, a Pinterest title and description, and an announcement for each channel — from the same source, then routes each out with the right link and timing. You approve from the dashboard, or let the cadence run.
Replies and back-links
Comments on your posts can be read and answered from one Inbox, and the blog post can end with a line linking to the conversation on each platform. See Comment inbox and Back-links on the blog.