New WordPress post to LinkedIn, X and Facebook

Simplified after publishing. This build now sends only post_id, so it matches the n8n template exactly. The AI transcript below shows the original build, which also mapped the title and excerpt and used a Code Glue snippet to add the permalink and featured image. The template now fetches all of that itself.

Every time you publish a WordPress post, this webhook sends its ID to one n8n webhook. The n8n workflow reads the post from your site's REST API and shares it on LinkedIn, X (Twitter) and Facebook: three networks from one delivery, no per-network plugin and no Zapier task cost.

Why it goes through n8n

None of the three social APIs accept a plain API-key POST — LinkedIn, X and Facebook all require OAuth on your app's behalf, and an OAuth dance is not something a webhook can perform. n8n holds those connections, so WordPress only ever talks to one URL.

That URL is the only thing you maintain. Add Mastodon or Bluesky later and nothing changes in WordPress.

What you need first

1. In n8n, import the template, Share new WordPress posts on LinkedIn, X and Facebook via webhook, and set your site's address in its Settings node.
2. Connect your LinkedIn, X and Facebook accounts inside n8n. The template's notes link each network's API access page; note that X is pay-per-use.
3. Open the New Post Webhook node, add a Header Auth credential with the name X-Webhook-Token and a long random token as the value, and copy the node's production URL.
4. Import this build. The webhook arrives disabled: replace its endpoint URL with that production URL, give the import the same token when it asks for the credential, then enable it. The token lives in the Credentials Vault and is never part of a shared build.

What gets sent

{
  "post_id": 123
}

publish_post hands over the post ID and the WP_Post object; args.1.ID is mapped to post_id and nothing else travels, because unmapped fields are dropped. The template fetches the title, excerpt, permalink and featured image from /wp-json/wp/v2/posts/{post_id}, which WordPress serves publicly for published posts. If a security plugin blocks anonymous REST access, switch the template's Get Post node to an application-password credential.

It only fires on a real publish

publish_post is not a "new post" hook. WordPress fires it on every save where the status is publish, so editing a live article would announce it a second time. A condition on the old status — args.2 must not equal publish — keeps this to genuine first publications.

If a delivery fails

Delivery is asynchronous, so publishing a post never waits on n8n. A failed POST is retried 5 times — 1m, 2m, 4m, 8m — and every attempt is kept in the delivery log with the full request and response. If n8n was down for the whole ladder, hit Replay once it's back and the post goes out without republishing it.

A 200 from the webhook node only means n8n accepted the payload. Check n8n's own execution list to confirm all three social nodes succeeded.