New WordPress post to LinkedIn, X and Facebook

Every time you publish a WordPress post, this webhook sends it to one n8n webhook, which fans it out to 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, add a Webhook node — method POST, path of your choosing — and copy its production URL.
2. Wire a LinkedIn, an X and a Facebook Pages node after it, connecting each account inside n8n.
3. Protect the node with header auth, and store that token in the Credentials Vault. The import asks you for it; it is never part of a shared build.

What gets sent

{
  "title": "Hello world",
  "summary": "A short excerpt.",
  "url": "https://example.com/hello-world/",
  "image_url": "https://example.com/wp-content/uploads/2026/08/hero.jpg"
}

publish_post hands over the post ID and the WP_Post object, so title and summary map straight across. The permalink and the featured image are not in that payload, so a pre-dispatch Code Glue snippet resolves them with get_permalink() and get_the_post_thumbnail_url(), falling back to get_the_excerpt() when the excerpt is empty. Nothing else travels — unmapped fields are dropped, so the rest of the post object stays in WordPress.

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.