Sawir Social Scheduler turns WordPress into a social media scheduler. Connect your channels with the tokens each platform gives you, write a post, pick channels, set a date, and publish. Every send runs in the background and reports back with a link or the platform's own error message.<\/p>\n\n
There is no hosted service in between. Credentials are encrypted with your site's salts and never leave your server.<\/p>\n\n
Add as many channels as you like, several accounts per platform. Each channel has a Test connection<\/strong> button that fetches the account name and avatar and confirms the token really works before you rely on it.<\/p>\n\n Social:<\/strong> X (Twitter), Facebook Page, Instagram, Threads, LinkedIn Page, Bluesky, Mastodon, TikTok, YouTube, Pinterest, Tumblr, Dribbble, Google Business Profile<\/p>\n\n Community:<\/strong> Telegram, Discord, Slack, Reddit, Lemmy, VK, Kick, Twitch, Whop<\/p>\n\n Blog and newsletter:<\/strong> WordPress, Medium, Dev.to, Hashnode, Listmonk<\/p>\n\n Group channels by client or brand with nested groups, then select a whole group with one click.<\/p>\n\n Every post fans out into one send per channel, and the calendar shows each as a card colored by state: scheduled, sent, failed, held, draft, in progress. Drag a card to move that channel's time. Click a card for the error, a Retry button, the live link, and engagement numbers. Click an empty slot to start a post at that time. Month, week, day, and list views, filterable by group and status.<\/p>\n\n Likes, comments, shares, views and impressions are collected 1 hour, 1 day and 1 week after each send, plus on demand, on 16 platforms. Follower counts are recorded daily per channel with a 30-day sparkline. Numbers appear on the calendar cards, in the post's Analytics box, and in the Channels list. The Analytics page sums it up for the last 7, 30 or 90 days against the period before: posts sent, engagement, reach and followers with their change, a followers chart, engagement by channel, and your top posts.<\/p>\n\n Tick \"Hold sends until approved\", copy the preview link, and send it to your client. They see the post as it will look on every channel, with no login, and click Approve or Request changes with a note. Approval releases the sends. Every decision is kept as history.<\/p>\n\n Large video uploads to X, YouTube and TikTok run in short slices that resume across background jobs, so they survive host time limits and never load a whole file into memory.<\/p>\n\n Everything the admin does is available at Create a post with The same operations are registered with the WordPress Abilities API as Sends run in the background through Action Scheduler when your site has it (WooCommerce and many other plugins provide it) and through WP-Cron otherwise. On WordPress's built-in cron they only progress when the site gets traffic. For prompt sends, add a system cron, the Calendar screen shows the exact command for your site.<\/p>\n\n Media must be reachable from the internet for platforms that fetch by URL (Instagram, Threads, Facebook, Pinterest, Telegram). A local development site cannot deliver images to them.<\/p>\n\n Bundles FullCalendar (MIT), the WordPress Abilities API library (GPL), and brand marks from Simple Icons (CC0). Uses Action Scheduler when another plugin provides it.<\/p>\n\n This plugin exists to publish your content to third-party social networks, so it talks to their APIs. Nothing is sent anywhere until you add a channel and post to it. There is no Sawir Studio server in between: your site talks to each platform directly.<\/p>\n\n What is sent, and when<\/strong><\/p>\n\n Credentials are stored encrypted on your server and are only ever sent to the platform they belong to.<\/p>\n\n Services, by platform<\/strong><\/p>\n\n Client approval links are served by your own site; they contain the post as it will appear and are public to anyone holding the link.<\/p>\n\n Trademarks<\/strong><\/p>\n\n Platform names and logos are trademarks of their respective owners and are used only to identify the service a channel connects to. This plugin is not affiliated with or endorsed by any of them.<\/p>\n\n\n Each platform's developer settings. The channel form names the exact credential it needs, for example a Facebook Page access token, a Telegram bot token, or a Bluesky app password. Long-lived tokens are best; Meta and LinkedIn tokens expire after about 60 days and need re-pasting.<\/p><\/dd>\n Private channels have no @username. Leave the Chat ID blank and click Test connection: the plugin lists every chat the bot has been added to, with the numeric ID to paste.<\/p><\/dd>\n The background queue has not run yet. Visit the site, or set up the system cron shown on the Calendar screen.<\/p><\/dd>\n No. Instagram fetches media by URL and needs a public address. Everything else about the plugin works locally.<\/p><\/dd>\n Not in this version. MeWe has no public posting API, Skool has no API at all, and Nostr needs a WebSocket relay client and Schnorr signing that PHP does not ship with.<\/p><\/dd>\n\n<\/dl>\n\n\nPosts<\/h4>\n\n
\n
\"date\": \"next\"<\/code>.<\/li>\n@handle<\/code> and the network resolves it on X, Instagram, Threads, Mastodon, Telegram, Reddit and Bluesky, where links and handles become real facets. LinkedIn company pages are @[Name](org:12345)<\/code> with the ID from the page URL; Facebook pages are @[12345]<\/code>.<\/li>\n{n}<\/code> in the text to number runs, since X, Threads and Bluesky reject identical text.<\/li>\n<\/ul>\n\nCalendar<\/h4>\n\n
Analytics<\/h4>\n\n
Client approval<\/h4>\n\n
REST API<\/h4>\n\n
\/wp-json\/sawir-social\/v1<\/code> for automations, mobile apps, and other sites. Authenticate with an application password; permissions follow the plugin's capabilities and channel credentials are never returned.<\/p>\n\n\n
GET \/platforms<\/code>, GET \/channels<\/code>, GET \/channels\/{id}<\/code>, POST \/channels\/{id}\/test<\/code><\/li>\nGET|POST \/posts<\/code>, GET|PATCH|DELETE \/posts\/{id}<\/code>, POST \/posts\/{id}\/duplicate<\/code>, GET \/posts\/{id}\/analytics<\/code><\/li>\nGET \/sends<\/code>, GET \/sends\/{id}<\/code>, POST \/sends\/{id}\/retry<\/code>, POST \/sends\/{id}\/stats<\/code><\/li>\n<\/ul>\n\n{\"title\",\"content\",\"status\":\"future\",\"date\":\"2026-12-25 09:00\",\"media\":[12],\"parts\":[{\"text\",\"media\",\"delay\"}],\"channels\":[{\"id\":38,\"parts\":[{\"text\",\"media\",\"delay\"}],\"date\":\"\u2026\"}],\"groups\":[\"Client A\"],\"hold\":false}<\/code>. A channel's parts<\/code> replace the post for that channel; text<\/code> is shorthand for a single part.<\/p>\n\nAI agents<\/h4>\n\n
sawir-social\/list-channels<\/code>, create-post<\/code>, update-post<\/code>, list-posts<\/code>, list-sends<\/code>, retry-send<\/code>, test-channel<\/code>, get-analytics<\/code> and list-platforms<\/code>, with typed input and output schemas. Any agent connected through the WordPress MCP adapter sees them as tools, and they are also callable at \/wp-json\/wp-abilities\/v1\/abilities\/{name}\/run<\/code>. The Abilities API is part of WordPress 6.9 and newer; for older versions the plugin bundles it, so the abilities are available everywhere the plugin runs.<\/p>\n\nRequirements<\/h4>\n\n
Credits<\/h4>\n\n
External services<\/h3>\n\n
\n
\n
\n
\/wp-content\/plugins\/<\/code> and activate it.<\/li>\n\n
Where do I get the tokens?<\/h3><\/dt>\n
My Telegram test says \"chat not found\"<\/h3><\/dt>\n
Why is a send stuck on \"In progress\u2026\"?<\/h3><\/dt>\n
Can I post a video to Instagram from a local site?<\/h3><\/dt>\n
Is Nostr, MeWe or Skool supported?<\/h3><\/dt>\n
0.1.0<\/h4>\n\n
\n