Quick overview
Quick overview Every time a post goes live on your WordPress site, this workflow shares it on LinkedIn, X and a Facebook Page. WordPress calls the workflow once per post, so there is no schedule to tune and no table of already-posted IDs to keep. How it works New Post Webhook receives {"post_id": 123} from WordPress. Header Auth keeps the endpoint private. Settings holds your site URL. Get Post reads /wp-json/wp/v2/posts/123?_embed=wp:featuredmedia on your site. Published posts are public, so no WordPress credentials are needed. Post Fields is a short Code node that turns the REST response into title, summary, url and image_url: it strips the HTML from the excerpt, decodes entities and takes the featured image if there is one. Get Featured Image downloads the post's featured image and Has Featured Image checks that there was one. Publish on LinkedIn shares the image with the title, the summary and the permalink in the text. A post without a featured image goes to Publish Link on LinkedIn instead, which shares it as a link card. Publish on X posts the title and the link, Publish on Facebook posts the title, the summary and the link to your Page, and both show the image from your page's Open Graph tags, which any SEO plugin adds. On a site without those tags the X and Facebook posts appear as plain text. Each publish node continues if another one fails, so a LinkedIn outage does not stop the X and Facebook posts. Setup Open Settings and enter your site URL. Open New Post Webhook, add a Header Auth credential (for example X-Webhook-Token) and copy the production URL. Create an app in the X developer console, enable User authentication settings (Read and write, Web App) and connect the OAuth 2.0 Client ID and Secret as an X OAuth2 credential on Publish on X. X has had no free tier since February 2026: load credits under Billing first, or the node answers 402 Payment required. A post with a link costs $0.20, so a weekly article is about $10 a year. Create a LinkedIn app with the w_member_social scope (LinkedIn Posts API) and connect it on Publish on LinkedIn and Publish Link on LinkedIn. The app needs two products: Share on LinkedIn and Sign In with LinkedIn using OpenID Connect. In the n8n credential, turn off Legacy and Organization Support before you connect, or LinkedIn rejects the scopes they add. Then pick your profile under Person on both LinkedIn nodes. To post as a company page, switch both nodes to Organization, keep Organization Support on and get the Community Management API approved for your app. Get a Page access token from your Meta app (access tokens), connect it on Publish on Facebook and replace YOUR_PAGE_ID with your Page ID. It must be the Page token, not your user token: with a user token the node fails with a plain "Forbidden". If me/accounts comes back empty for a Page owned by a business portfolio, read the token from the Page itself with GET /{page-id}?fields=access_token. In WordPress, send {"post_id": 123} to the webhook URL when a post is first published. The free Webhook Actions plugin does it without code: new webhook on publish_post, map args.1.ID to post_id, attach the header credential, and add the condition args.2 not equals publish so editing a live post does not share it again. A short PHP snippet that does the same is under Additional info. Activate the workflow and publish a test post. Requirements A public WordPress site (the REST API is read anonymously) X OAuth2, LinkedIn OAuth2 and Facebook Graph API credentials in n8n X API credits (pay-per-use, see step 3) Customization Add a model node (OpenAI, Gemini) between Post Fields and the publish nodes to write a caption per network from title and summary. Add Mastodon, Bluesky or Slack as another branch after Post Fields; the four fields are already there. To always share a link card on LinkedIn instead of the image, connect Post Fields straight to Publish Link on LinkedIn and delete the image branch. If your site blocks anonymous REST access, give Get Post a WordPress application-password credential. Additional info Who is this for. Anyone who publishes on WordPress and wants each new article shared on the three networks without a per-network WordPress plugin. It also fits agencies that run n8n for several client sites: the only per-site value is the URL in the Settings node. WordPress side without a plugin. Put this in functions.php or a custom plugin. Replace the URL and the token with yours (the token must match the Header Auth credential in n8n): add_action( 'publish_post', function ( $post_id, $post, $old_status ) { if ( 'publish' === $old_status ) { return; // editing an already published post must not share it again } $payload = []; $payload['post_id'] = $post_id; $args = []; $args'headers' = 'application/json'; $args'headers' = 'YOUR-TOKEN'; $args['body'] = wp_json_encode( $payload ); $args['blocking'] = false; // do not make the editor wait for n8n wp_remote_post( 'https://YOUR-N8N/webhook/wordpress-post-published', $args ); }, 10, 3 ); `. An n8n automation workflow template by Mateusz Skorupa.
Mateusz Skorupa
web
free
Others in the same category, ranked by how often they are opened.
