Sawir Social Scheduler

By Ricardo Sawir

0+ active installationsVersion 0.2.3

Write once, schedule to 27 networks from wp-admin. Per-channel edits, threads, media, previews. Your tokens stay on your server.

Description

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.

There is no hosted service in between. Credentials are encrypted with your site’s salts and never leave your server.

Channels

Add as many channels as you like, several accounts per platform. Each channel has a Test connection button that fetches the account name and avatar and confirms the token really works before you rely on it.

Social: X (Twitter), Facebook Page, Instagram, Threads, LinkedIn Page, Bluesky, Mastodon, TikTok, YouTube, Pinterest, Tumblr, Dribbble, Google Business Profile

Community: Telegram, Discord, Slack, Reddit, Lemmy, VK, Kick, Twitch, Whop

Blog and newsletter: WordPress, Medium, Dev.to, Hashnode, Listmonk

Group channels by client or brand with nested groups, then select a whole group with one click.

Posts

  • One body, many channels. Pick channels with checkboxes. Untouched channels get the post as written.
  • Customize per channel. Tick “Customize” on any channel to give it its own parts: text, media and delays, prefilled from the post so you edit a copy. Other channels keep the post as written.
  • Threads. Add parts to post a thread on X, Threads, Bluesky, Mastodon and Telegram, each with its own media. Platforms without threads receive the parts joined.
  • Media. Attach images and video once. Each platform gets what it supports: albums, carousels, Reels, resumable video uploads.
  • Schedule. Use the normal WordPress “Publish on” date, or give any channel its own time.
  • Posting times. Give a channel its usual times of day. “Next free slot” fills the next unused one, the calendar shows empty upcoming slots you can click to fill, and the API accepts "date": "next".
  • Preview. A live preview per channel that looks like the real platform, with character limits and media rules applied so you see exactly what will go out.
  • Comments and delays. On platforms without threads, extra parts post as comments under the post. Any part can wait a set number of minutes after the previous one.
  • Share a blog post. A box on the normal post editor posts to your channels when the post publishes, with its own text and media.
  • Duplicate. Copy a post with its channels, parts and overrides as a new draft. Keep drafts as templates.
  • Mentions. Type @handle 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) with the ID from the page URL; Facebook pages are @[12345].
  • Repeat. Resend evergreen posts every N days or weeks, until a date or a number of times. Each run is its own post with its own sends and stats. Put {n} in the text to number runs, since X, Threads and Bluesky reject identical text.

Calendar

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.

Analytics

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.

Client approval

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.

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.

REST API

Everything the admin does is available at /wp-json/sawir-social/v1 for automations, mobile apps, and other sites. Authenticate with an application password; permissions follow the plugin’s capabilities and channel credentials are never returned.

  • GET /platforms, GET /channels, GET /channels/{id}, POST /channels/{id}/test
  • GET|POST /posts, GET|PATCH|DELETE /posts/{id}, POST /posts/{id}/duplicate, GET /posts/{id}/analytics
  • GET /sends, GET /sends/{id}, POST /sends/{id}/retry, POST /sends/{id}/stats

Create a post with {"title","content","status":"future","date":"2026-12-25 09:00","media":[12],"parts":[{"text","media","delay"}],"channels":[{"id":38,"parts":[{"text","media","delay"}],"date":"…"}],"groups":["Client A"],"hold":false}. A channel’s parts replace the post for that channel; text is shorthand for a single part.

AI agents

The same operations are registered with the WordPress Abilities API as sawir-social/list-channels, create-post, update-post, list-posts, list-sends, retry-send, test-channel, get-analytics and list-platforms, 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. The Abilities API is part of WordPress 6.9 and newer, so the abilities are available on those versions. On older WordPress everything else works as usual.

Requirements

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.

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.

Credits

Bundles FullCalendar (MIT) and brand marks from Simple Icons (CC0). Uses Action Scheduler when another plugin provides it.

External services

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.

What is sent, and when

  • When you click Test connection: the channel’s credentials, to confirm they work and fetch the account name and avatar.
  • When a send goes out: the post text, the title where the platform uses one, and your media (uploaded as files, or as public URLs for platforms that fetch media themselves), together with the channel’s credentials.
  • When analytics run, 1 hour, 1 day and 1 week after a send, once a day per channel, or when you click Refresh: the credentials and the ID of the post, to read engagement and follower counts.
  • Never: your visitors’ data, your site’s users, or anything from posts you did not choose to share.

Credentials are stored encrypted on your server and are only ever sent to the platform they belong to.

Services, by platform

  • X (Twitter): api.twitter.com, upload.twitter.com. Terms · Privacy
  • Facebook Pages, Instagram, Threads (Meta): graph.facebook.com, graph.threads.net. Terms · Privacy
  • LinkedIn: api.linkedin.com. Terms · Privacy
  • Bluesky: the service URL you enter, bsky.social by default. Terms · Privacy
  • Mastodon: the instance URL you enter. Terms and privacy: the terms of your instance.
  • TikTok: open.tiktokapis.com. Terms · Privacy
  • YouTube, Google Business Profile (Google): googleapis.com, oauth2.googleapis.com, mybusiness.googleapis.com. Terms · Privacy
  • Pinterest: api.pinterest.com. Terms · Privacy
  • Tumblr: api.tumblr.com. Terms · Privacy
  • Dribbble: api.dribbble.com. Terms · Privacy
  • Telegram: api.telegram.org. Terms · Privacy
  • Discord: the webhook URL you enter on discord.com. Terms · Privacy
  • Slack: the webhook URL you enter on hooks.slack.com. Terms · Privacy
  • Reddit: www.reddit.com, oauth.reddit.com. Terms · Privacy
  • Lemmy: the instance URL you enter. Terms and privacy: the terms of your instance.
  • VK: api.vk.com. Terms · Privacy
  • Kick: api.kick.com, id.kick.com. Terms · Privacy
  • Twitch: api.twitch.tv, id.twitch.tv. Terms · Privacy
  • Whop: api.whop.com. Terms · Privacy
  • WordPress (another site): the site URL you enter. Terms and privacy: the terms of that site.
  • Medium: api.medium.com. Terms · Privacy
  • Dev.to: dev.to. Terms · Privacy
  • Hashnode: gql.hashnode.com. Terms · Privacy
  • Listmonk: the Listmonk URL you enter. Terms and privacy: your own installation.

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.

Trademarks

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.

Installation

  1. Upload the plugin folder to /wp-content/plugins/ and activate it.
  2. Go to Social → Channels → Add Channel, pick a platform, paste the credentials it asks for, and click Test connection.
  3. Go to Social → Posts → New Social Post, write, pick channels, publish or schedule.

FAQ

Where do I get the tokens?

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.

My Telegram test says “chat not found”

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.

Why is a send stuck on “In progress…”?

The background queue has not run yet. Visit the site, or set up the system cron shown on the Calendar screen.

Can I post a video to Instagram from a local site?

No. Instagram fetches media by URL and needs a public address. Everything else about the plugin works locally.

Is Nostr, MeWe or Skool supported?

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.

Is there a hosted version?

Yes: SawirPost, from the same team. It is a paid service (from $29/month, with a 7-day free trial) that publishes to 25+ channels from its own servers, so posts do not depend on your site’s cron or traffic, and it is built for agencies: client preview links with comments, channels grouped by client, and staggered or repeating posts. This plugin stays free and complete; choose SawirPost if you would rather not run the publishing yourself.

Screenshots

Changelog

0.2.3

  • Changed: the AI agent abilities now use the Abilities API built into WordPress 6.9 and newer. The plugin no longer bundles its own copy, so on older WordPress versions the abilities are not offered; everything else works as before.
  • Code: main classes renamed to the plugin’s SWSS_ prefix. No change in behavior.

0.2.2

  • New: a link to SawirPost, our hosted service, in the plugin row, the FAQ, and a dismissible one-line note on the channel screen. Nothing is sent to Sawir Studio.

0.2.1

  • Improved: when an edit to a client-approved post cancels the approval, its sends are moved to “held” immediately (instead of looking scheduled until they fail to post), the editor sees a notice with the approval link, and the post’s author gets an email.
  • New: a “Minor edit — keep the client’s approval” checkbox in the approval box for typo or link fixes. Keeping an approval is recorded in the approval history.
  • New: held sends due within 24 hours (or past due) are flagged “Needs approval” on the calendar, with a warning on the calendar and post lists.

0.2.0

  • Fix: trashing a campaign now stops sends that are queued or still uploading. Unstarted sends are kept as drafts, so restoring the campaign restores its channels.
  • Fix: every send has an explicit delivery state (queued, sending, uploading, posting thread, sent, sent with incomplete thread, failed, unknown), changed atomically — two background runners can never post the same send twice, and re-saving a published send never re-sends it.
  • Fix: a send interrupted mid-call (timeout, crash) is marked “Unknown — check the channel” instead of showing as Sent; it is never retried automatically because it may already be live.
  • Fix: a failed reply in a thread marks the send “Sent, thread incomplete” with the error, instead of plain Sent.
  • Fix: client approval is tied to the exact content approved — editing the post afterwards holds its sends until it is approved again, and “Request changes” after an approval pulls back sends that have not gone out.
  • Fix: publishing, scheduling or unpublishing a campaign from Quick Edit, the REST API or after restoring it from the trash now updates its sends and repeat schedule, keeping each channel’s own send time.
  • New: a background watchdog every 15 minutes publishes sends whose scheduled time was missed by WP-Cron and re-queues lost background actions.

0.1.0

  • Initial release: 27 platforms, threads and comments with delays, per-channel overrides and times, media, live previews, calendar with drag to reschedule, analytics, client approval links, blog post sharing, duplicate, roles and capabilities, resumable uploads, background sends with retry.