Black Friday: 40% off everything from November 23 with code BF40 See the deals →

Aluleth Social documentation

Everything you need to set up Aluleth Social, the free plugin that plans and publishes your social posts from WordPress, and its add-on Aluleth Social Pro: Facebook Pages, Instagram, Threads, LinkedIn, X and Pinterest through your own apps, a queue, evergreen posts, RSS feeds, CSV import, AI captions, approval and reports.

Contents

Requirements

  • WordPress 7.0 or newer, PHP 7.4 or newer.
  • WordPress cron must run: posts go out with it, every minute. On a quiet site, or when your host turned it off (DISABLE_WP_CRON), ask for a server task that calls wp-cron.php every minute.
  • For Pro networks: a site served over HTTPS (the networks only send you back to an https:// address) and a developer app on each network you use.
  • For Instagram and Threads: a site that can be reached from the internet, as these networks fetch the image from it.

Installation

  1. Download Aluleth Social (free) from its page, then go to Plugins › Add New › Upload Plugin, upload aluleth-social-x.y.z.zip as it is and activate it.
  2. For Pro, download aluleth-social-pro-x.y.z.zip from My account › Downloads on Aluleth Market (the free plugin is in the same download list), upload it the same way and activate it.
  3. Enter your licence key in Aluleth › Settings › Licences. It turns on the Pro networks and features and one-click updates.
  4. Open Aluleth › Social.

With Aluleth Suite, the same Suite key works for Aluleth Social Pro.

Updates

With an active licence, new versions of Aluleth Social Pro show in Dashboard › Updates and install in one click. Without one, download the new zip from My account › Downloads and upload it with Replace current with uploaded. Your accounts, posts and settings are kept, and database changes run by themselves.

First steps

  1. Go to Aluleth › Social › Accounts and connect a first account: each network says where to find what it needs.
  2. Write a post in New post: tick the accounts, publish it now or choose a date.
  3. To share your new articles and products by themselves, choose them in Settings › Share on publish.
  4. Look at the Calendar and at Posts: each post shows how it went on each account, with a link to the published post.

Bluesky, Mastodon, Telegram, Discord and webhooks

  • Bluesky: your handle and an app password (Bluesky › Settings › Privacy and security › App passwords), never your account password. Links are shown short and stay clickable, hashtags work, an image goes with its alternative text, a link shows as a card. An account on another server: enter its address.
  • Mastodon: your server and an access token (Preferences › Development › New application, scopes read:accounts, write:statuses, write:media). The server’s own character limit is read when you connect; each link counts as 23 characters.
  • Telegram: make a bot with @BotFather, add it to your channel or group as an admin that may post, then paste the bot token and the @name of the channel (or the number of a private one).
  • Discord: in the channel’s settings › Integrations › Webhooks, make a webhook and paste its address. Posts never ping @everyone.
  • Webhook: every post sent as JSON (text, link, image_url, image_alt…) to Zapier, Make, n8n or your own code. With a secret, each call has an X-Aluleth-Signature header (sha256 HMAC of the body). A test call is sent when you connect.
  • The free plugin has one account per network; Pro adds as many as you need.

Writing a post

  • One text for every account, and an own text for any account that needs it.
  • A character counter for each ticked account, counted as that network counts (short links on Bluesky, 23 per link on Mastodon and X, campaign tags included). The post is checked again when you save it.
  • A link, with the title and summary of its card, and an image from the media library (its alternative text is sent with it).
  • Publish now, Schedule at a date and time (in the site’s time zone) or Save as draft. A post can be changed until it starts going out.

Calendar and posts

The Calendar shows the month with every post: planned, published, failed and drafts; the + of a day starts a post on that day. On phones it shows as a list. Posts lists them by status. Open one to see, for each account, when it went out, the link to the published post, or what the network said when it refused it. From there: publish a planned post now, try again where it failed, cancel, copy as a new draft, or delete it here (what was published on the networks stays there).

How posts go out

  • Every minute, the posts that are due are sent, one account after the other.
  • A network that is busy or out of reach is tried again after 5 and 30 minutes; after 3 tries the post is marked as failed on that account.
  • A refused password, token or permission marks the account as “does not answer” at once: connect it again in Accounts.
  • A post can never be sent twice: each delivery is taken by one request only, and the networks that accept it get a key against doubles.

Share on publish

  • Choose what is shared in Settings: posts (on by default), pages, WooCommerce, Aluleth Commerce and FluentCart products.
  • A text for each type, with {title}, {excerpt}, {url}, {price} (products) and {site}. A text too long for a network is made shorter there: the excerpt first, then the title.
  • The featured image goes with the post; accounts that need an image are skipped when there is none.
  • The post goes out a few minutes after publishing (2 by default), so you can still change it: the Aluleth Social box of the editor turns it off for one content, gives it its own text, or stops it before it goes.
  • Each content is shared once, when it is first published.

Campaign tags and statistics

Links to your own site get utm_source (the network), utm_medium=social and utm_campaign (the name you choose in Settings). Links to other sites and links that already have a utm_source stay as they are. Aluleth Insights and other statistics tools then show which network brought each visit and each sale.

Pro: connecting with your own apps

Facebook, Instagram, Threads, LinkedIn, X and Pinterest only let a site publish through a developer app of its own. Each card in Accounts says how to make it and gives the redirect address to paste in the app. Paste the app id and secret, save, click Connect with …, allow the app on the network, and back on your site tick the Pages, profiles or boards to connect. Connecting again later gives an account its new login instead of a copy.

  • App ids, secrets and tokens are encrypted in your database and never shown again.
  • Each connection starts with a one-time code tied to the person who clicked; a link that was used or is older than 15 minutes does nothing.
  • For your own Pages and profiles, the apps work as soon as they are made; a review by the network is needed only to post for other people.
  • The redirect address must be exactly the one shown, on HTTPS. With “Plain” permalinks it has a “?”, which some networks refuse.

Pro: Facebook Pages and Instagram

One Meta app serves both. At developers.facebook.com › My Apps, make an app with the use cases to manage your Pages (and Instagram if you post there), add the redirect address in Facebook Login for Business › Settings › Valid OAuth Redirect URIs, and copy the App ID and App secret (App settings › Basic). While the app stays in development mode, it posts for the people who have a role in it.

  • One login gives every Page you manage (with the right to create content) and the Instagram professional accounts linked to them.
  • Facebook: a photo with its text, or the text with its link. Page logins do not end; they stop if you leave the Page or remove the app.
  • Instagram: a post needs an image, at most 30 hashtags and 2,200 characters. Instagram downloads the image from your site: a JPEG is used as it is; other formats get a JPEG copy for two days in uploads/aluleth-social-public/.

Pro: Threads

Make a Meta app with the use case “Access the Threads API”, add the redirect address as Redirect Callback URL, add your Threads profile as a tester and accept the invitation in Threads (Settings › Account › Website permissions), then copy the Threads app ID and secret. A post is a text with a link preview, or an image with its text (500 characters). The login lasts 60 days and is renewed by itself while the site posts.

Pro: LinkedIn

At linkedin.com/developers, make an app linked to a company page you manage, add the products “Share on LinkedIn” and “Sign In with LinkedIn using OpenID Connect”, add the redirect address under Auth, then copy the Client ID and Primary Client Secret. Posts go on the profile of the person who connects (company pages need LinkedIn’s approval of the Community Management API). Your #tags become LinkedIn hashtags; a link shows as a card, or an image goes with the post. The login lasts 60 days: the account list says until when, then click Connect again.

Pro: X

At developer.x.com, open your app, set up User authentication with the permission “Read and write”, the type “Web App, Automated App or Bot” and the redirect address as Callback URI, then copy the OAuth 2.0 Client ID and Client Secret. Posts have 280 characters as X counts them (links 23, some scripts and emoji count twice) and an image with its alternative text. The login is renewed by itself. X bills its API to your developer account: a post refused for lack of credits says so and is not tried again.

Pro: Pinterest

At developers.pinterest.com, make an app, add the redirect address under Redirect URIs, and copy the App ID and secret key. After the login, tick the boards to post on: each becomes an account, and they share the login. A pin needs an image; its title is the link title or the first line of the text, its description the text (800 characters). While your app only has Trial access, tick “Trial access”: pins go to Pinterest’s sandbox, seen only by you.

Pro: queue and evergreen

Queue: in the Queue tab, choose the days and times (24 h, in the site’s time zone). In the composer, Add to the queue plans the post at the next time that no other planned post uses.

Evergreen: shares an older content again, now and then, with the text of Share on publish. Choose the content types and the categories of posts, how old they must be, one content every how many hours, and never the same content again within how many days. One content each time, picked at random among those that fit. Share one older content now tries the rules at once.

Pro: RSS feeds and CSV import

RSS feeds: add the address of a feed (a blog, a podcast, a YouTube channel), its text ({title}, {excerpt}, {url}, {site}) and its accounts. Each hour, its new items become posts, three at most per feed, ten minutes apart. What is already in the feed when you add it is not shared; accounts that need an image are skipped.

CSV import: first row with the column names: text (needed), link, date (2026-12-01 09:30, in the site’s time zone; empty = a draft), accounts (ids or network names such as bluesky|linkedin; empty = every account) and image (an id or the address of an image of your media library). UTF-8, comma or semicolon, 500 rows at most. The rows that could not be imported are listed with the reason.

Pro: AI, hashtag sets and groups

  • AI buttons under the text: write a post from its link, improve it, make it shorter, add hashtags. They use Aluleth AI Writer and its providers (Settings › Connectors) when it is set up, or your own OpenAI key and model in Social › Settings. Nothing is published without you.
  • Hashtag sets: saved in Settings, added at the end of the text in one click.
  • Account groups: a button in the composer ticks every account of a group.

Pro: approval

Turn on approval in Settings and give the access Social: approve posts to your approvers in Aluleth › Settings › Access (administrators always have it). The posts of the others go to To approve with the date they asked for, and the approvers get an email. An approver publishes the post (or plans it at that date) or sends it back to its author with a note. Shared on publish, evergreen and RSS posts follow the rules an approver set; while approval is on, only approvers change these rules.

Pro: reports

The Reports tab shows, for 7, 30, 90 or 365 days, the posts published and failed on each account and where the posts came from (by hand, on publish, evergreen, RSS, import). With Aluleth Insights, it adds the visits and goals each network brought, read from the campaign tags of your links (per network, not per account). Download every delivery as a CSV file.

Security and privacy

Passwords, tokens, app secrets and the OpenAI key are encrypted in your database with a key made from your site’s own secret keys, and are only sent to the service they belong to. Aluleth Social keeps nothing about your visitors; a suggested text for your privacy policy is added in Settings › Privacy. Only people with the Social access of the Aluleth suite (and administrators) use the screens.

Translating the plugin

English and French are included in full. The POT files are in the languages/ folder of each plugin: translate them with Loco Translate or Poedit.

Uninstalling

Deactivating keeps everything. Deleting the plugin deletes nothing either, unless you choose it in Aluleth › Settings › When you delete a plugin. Tick Aluleth Social to delete the posts, the accounts and the settings with the free plugin; what was published on the networks stays there. Deleting Pro always removes the app keys, the logins, the OpenAI key and the public image copies; tick Aluleth Social Pro to delete the Pro settings too.

Troubleshooting

  • A planned post did not go out on time: WordPress cron is not running often enough; ask your host for a server task that calls wp-cron.php every minute.
  • “Connect with …” comes back with an error: check that the redirect address is pasted exactly in your app, that the site uses HTTPS, and that the permalinks are not “Plain”.
  • An account is marked “does not answer”: its password, token or login stopped working or was removed on the network. Connect it again.
  • Instagram or Threads cannot fetch the image: the site must be online and not protected by a password.
  • The text is too long for an account: write an own text for that account, or let the counter guide you.
  • A post failed: open it in Posts: the reason given by the network is shown for each account, with Try again where it failed.