You publish an article and it should reach the people following you elsewhere. Doing that by hand means writing four versions of the same announcement while you’d rather be writing the next article, so it stops happening.
Here’s the automated version, and the parts that decide whether it looks deliberate or automated.
Two ways in
The RSS route. WordPress publishes a feed at /feed by default. If all you need is “new article becomes a post”, you may not need n8n at all: BulkPublish reads RSS natively, polls with conditional requests, and turns new items into posts.
- Feeds: Free: 1. Pro: 10. Business: 50.
- Auto-publish: paid plans. On Free, items arrive as drafts for review.
The n8n route. Worth building when you want more than the feed carries: filtering by category, different accounts for different content types, rewritten text per platform, or the featured image handled properly.
The workflow
1. Trigger. Either the WordPress trigger node, or an RSS Feed Trigger on your /feed URL. RSS is simpler and needs no credentials. The WordPress node gives you more fields, including categories and the featured image, which is usually why you’d choose it.
2. Filter by category or tag. Most sites publish more than one kind of thing, and not all of it warrants an announcement. Release notes, say, probably shouldn’t go to the same places as an essay.
3. Build the text. This is the step that separates a useful automation from a bot.
The default is to post the title and the link, and it’s why automated accounts read the way they do. A title is written to work as a headline on your site, sitting above the article. On social it arrives with no context and asks nothing of the reader.
Write something else: one line saying why the piece exists, then the link. You can template it, or hand the title and excerpt to an AI node and have it draft the line, but review what it produces before trusting it.
4. Handle the image. WordPress featured images are usually the right shape for social. Pass the URL through. Decide what happens when a post has no featured image, since some platforms require media.
5. BulkPublish node, Post → Create. Text, channels, optional schedule.
6. Schedule, don’t publish instantly. You publish an article when it’s finished, which is rarely a good posting time. Scheduling it for the next reasonable slot costs nothing and looks considered.
Per-platform text
The same announcement rarely works everywhere. A professional network wants the “why this matters” framing. A short-form network wants the single interesting claim. A community server may want a more casual note.
You can either branch in n8n and send different text per platform, or send one draft and adjust per platform in the composer. The second is less workflow to maintain, which matters for something you set up once and want to forget about.
The failure to design against
An account that only announces its own articles is a feed, and people stop reading feeds. If this automation is most of what an account posts, the automation isn’t the problem, the content mix is.
Use it as a reliable floor rather than the whole output.
Run it into drafts first
For the first few articles, create posts as drafts. You’ll see what the workflow actually produces, and the things worth fixing are obvious in a list of five drafts in a way they aren’t in a workflow editor.
Plan limits
- Channels: Free: 3 (1 per platform). Pro: 30 (2 per platform). Business: 75 (5 per platform).
- Posts: Free: 3/day. Pro: 30/day. Business: unlimited.
- API requests/day: Free: 30. Pro: 5,000. Business: 50,000.
BulkPublish publishes to 15 platforms: Facebook, Instagram, TikTok, YouTube, X, Threads, Bluesky, Pinterest, Google Business Profile, LinkedIn, Mastodon, Discord, Telegram, Tumblr and Snapchat.
The short version
If you just want new articles announced, point the built-in RSS reader at your /feed and stop. Build the n8n workflow when you need category filtering, per-platform text or the featured image handled. Whatever you build, write a real line rather than posting the headline, and schedule instead of relaying.