Auto-posting to LinkedIn that does not quietly fail.
Most “share to social” plugins fire an HTTP request during the publish request and hope. When LinkedIn rate-limits you, or is briefly down, or your token has expired, the post is simply gone — no retry, no record, and nobody notices for a week.
This one treats publishing as a job. WordPress stays the scheduler of record: when a post goes live, the plugin queues a background job and calls the LinkedIn Posts API from there. Your editor never waits on LinkedIn, and LinkedIn being slow never delays publishing on your site.
No license key. No activation. No phone-home.
Nothing to register and no remote check of any kind. The only service contacted is LinkedIn, with your own LinkedIn app credentials. Nothing is sent to us, ever — there is no “us” in the request path at all.
Retries that make sense
Transient failures back off: 5 minutes, 30 minutes, 2 hours, 12 hours. A Retry-After header from LinkedIn is honoured when it asks for longer. Permanent failures — bad credentials, a rejected payload, a missing scope — are never retried on a timer, because repeating the same request until the attempt cap just wastes a day; those need an administrator, and the plugin says so instead of churning.
It will not post twice
A double post on a company page is embarrassing and cannot be undone, so there are three guards: a content hash so a repeated status transition cannot queue the same post twice, a short-lived per-post lock so two workers cannot overlap, and the stored LinkedIn post URN checked immediately before every send. On a site with a persistent object cache the lock is an atomic add; without one it is best effort, which is exactly why the stored URN is the real backstop rather than the lock.
Credentials handled properly
The client secret, access token and refresh token are encrypted at rest with AES-256-GCM, keyed from your site’s own authentication salts. They are stored with autoloading off, never rendered back into HTML, and never written to a log. If you would rather they were not in the database at all, pin them in wp-config.php with two constants and the plugin uses those instead.
The OAuth state value is single-use, bound to the administrator who started the flow, and expires after 15 minutes.
Every attempt is on the record
A log table with the HTTP status, the detail LinkedIn returned, the retry count and the resulting post URN. Filter by post, status or message. Resend a row. Prune on a retention schedule you set. When something has not published, the status code names the problem in one glance instead of sending you to a server error log.
Control where it belongs
- Per-post: a share checkbox, custom commentary that overrides the template, live status with a link to the published post, and manual *Post now* / *Resend*.
- Site-wide: eligible post types, share-by-default, commentary template with placeholders, default hashtags with a cap, attempt limit, logging level and log retention.
- In code: ten documented filters, including
ibuilder_social_post_textfor the commentary,ibuilder_social_share_urlfor UTM parameters,ibuilder_social_linkedin_payloadfor the raw API payload andibuilder_social_retry_delayfor the backoff schedule. - From the shell:
wp ibuilder_social statusreports connection, token expiry, queue and cron health in one command;wp ibuilder_social publish <id>sends immediately.
Also
- Uses Action Scheduler automatically when another plugin provides it, otherwise WP-Cron.
- Multisite: each site keeps its own connection, settings and logs — one network, many pages.
- Namespaced, autoloaded PHP with no bundled third-party code of any kind and nothing from a CDN.
- Deleting the plugin removes the log table, every option and all stored credentials.
Before you buy, know this
LinkedIn does not grant posting access by default. You need to create an app in the LinkedIn Developer Portal, add the Community Management API product, and complete LinkedIn’s review before the w_organization_social scope is available to it. No plugin can bypass that, and this listing does not pretend otherwise. Budget for LinkedIn’s review before you plan a launch around it.
Featured images are not uploaded in this version — LinkedIn requires images to be registered as separate assets first, which is a different API flow. Posts are shared as link posts with a title, description and permalink.
Requirements
WordPress 6.3+, PHP 7.4+ with OpenSSL, a LinkedIn app approved for the Community Management API, and a LinkedIn organization page you administer. Full documentation ships inside the zip.