Point an RSS automation at your blog's feed, connect your X and LinkedIn accounts, and each new article goes out as a post with its title and link. dlvr.it and IFTTT can still do that on X. Zapier and Make no longer have an X integration, though both still post to LinkedIn. Buffer's content feeds work differently: they list new articles, and you choose which ones become posts.
Most of these routes publish the moment they notice a new item, without anyone reading the post first. That is what they're for, and it is also the risk: the post is built from whatever your feed says at that moment, including a typo in a title, an article published by mistake or an old item whose identity changed.
Each tool's own help and integration pages were checked on October 26, 2026. This is a documentation check, not a live posting test. The sources are linked beside the claims below.
The routes at a glance
| Route | X | How often it checks your feed | Does anyone read the post first? | |
|---|---|---|---|---|
| IFTTT | Post a tweet (Pro) | Your personal profile (Pro) | Every hour on Free, 15 minutes on Starter, 5 minutes on Pro and Pro+ | No: the applet posts when the trigger fires |
| Zapier | No integration since August 31, 2023 | Your profile or a Page | 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise | Only if you add its paid approval step |
| Make | No X app since May 30, 2025 | User or company text, image and video posts | Every 15 minutes by default; the shortest interval depends on the plan | No step for it in its RSS and LinkedIn modules |
| dlvr.it | X profiles | Profiles, Pages and Showcase Pages | Every 6 hours on Free, 5 minutes on Pro and Plus, 2 on Agency | No: it publishes when an item appears |
| Buffer content feeds | Through Buffer's X channel | Through Buffer's LinkedIn channels | When you open the feed or refresh it | Yes: nothing becomes a post until you choose it |
| Flaghand feed drafts | An X draft per new item | A personal-profile draft with a link card | Every hour | Yes: the owner approves each post with a passkey. Sign-up isn't open yet |
IFTTT: one applet per network
IFTTT's RSS Feed service has two triggers: New feed item, and New feed item matches for items containing a keyword or simple phrase. Pair one with X's Post a tweet or with LinkedIn's Share a link or Share an update, and put the item's title and URL in the text.
- IFTTT marks both RSS triggers, Post a tweet and all four LinkedIn actions as Pro features. Check its plans before you build.
- These are polling triggers. IFTTT checks the feed every hour on Free, every 15 minutes on Starter and every 5 minutes on Pro and Pro+, so on Free a post can go out up to an hour after the article.
- The LinkedIn actions share on your LinkedIn profile. The service lists no action for a company Page.
- IFTTT's X action warns that affiliate URLs in the text end in an action error.
Zapier: LinkedIn yes, X no
RSS by Zapier starts a Zap with New Item in Feed (or New Items in Multiple Feeds). Its recommended setting, Different Guid/URL, fires when a new URL appears in the feed. Different Content and Anything is Different also fire when an existing item changes, which can post the same article again.
- Zaps trigger only for new data, not for anything in the feed before you turned the Zap on. Polling runs every 15 minutes on Free, 2 on Professional and 1 on Team and Enterprise.
- On LinkedIn, Zapier's LinkedIn integration has Create Share Update for your profile and Create Company Update for a Page.
- On X there is nothing to connect. Zapier's own help says its Twitter integration stopped working on August 31, 2023, because of X's API policy and pricing, and points to social media tools such as Buffer and Hootsuite instead.
Of the four automations, Zapier's help is the one that documents a built-in way to stop and read. Its Human in the Loop Request Approval step pauses the Zap so a reviewer can approve, decline or change the content first. It is a premium app that needs a paid Zapier account. Watch its On timeout choice: Skip and continue runs the rest of the Zap without a response, so choose End run if nothing should post unread.
Make: LinkedIn modules, no X app
Make's RSS app starts a scenario with Watch RSS feed items: the URL of an RSS or Atom feed and the most items to return per run. Follow it with one of the LinkedIn app's modules: Create a User Text Post, Create a User Image Post or Create a User Video Post for your profile, or the matching Company modules for a Page.
- A polling trigger's Choose where to start setting applies only to the first run. Starting from the current moment sends only new articles; an earlier start can send old ones through too.
- A scenario runs every 15 minutes by default, and the shortest interval depends on your plan.
- Make discontinued its X app: no new scenarios from April 3, 2025, and existing ones stopped working on May 30, 2025. It suggests social media tools such as Buffer and Hootsuite instead.
dlvr.it: built for RSS, posts as it finds items
dlvr.it is an RSS-to-social service first. Add a feed and connect your accounts, and in its own words it "automatically publishes new content to your X / Twitter profile when items appear in your connected source". On LinkedIn it publishes to profiles, Pages and Showcase Pages, but not Groups.
- Its plans check feeds every 6 hours on Free, every 5 minutes on Pro and Plus and every 2 minutes on Agency. Free allows 10 posts a month per profile.
- Its X posts carry your link as plain text, not a tappable link, because X charges $0.20 for each post with a tappable link sent through its API. It offers a hosted link page and QR codes instead.
- Its LinkedIn page warns that LinkedIn monitors personal profiles for automated or duplicate content, and calls Pages the safer choice for high-volume automated publishing. It publishes up to 50 posts per 24 hours to one LinkedIn account.
- When it stops posting new items, the usual causes are feed caching, missing or repeated GUIDs and rate limits. Its "Republish items with updated timestamps" setting works around missing GUIDs, but it can post duplicates when timestamps change on their own.
The help pages we read describe no step where someone reviews each post before it goes out.
Buffer content feeds: you pick each one
Buffer's content feeds live in its Create space. Add a feed by URL or an OPML file, open it, hover over an article and choose Create Post (or Save as idea). The post then goes through Buffer's normal composer and queue for your X and LinkedIn channels.
- Nothing posts by itself. Buffer describes feeds as inspiration and a starting place for your own posts.
- Free connects up to 3 feeds and paid plans up to 50. A feed shows what the site provides, typically 10 to 20 recent articles, and refreshes when you open it.
It is the slowest route and the one where every post is one you chose.
Flaghand: each new item becomes a draft, not a post
Flaghand's feed subscriptions sit between those two. It reads each subscribed RSS, Atom or GitHub releases feed every hour, and each new item becomes two drafts: an X post and a LinkedIn post, each holding the item's plain-text title, a blank line and its link. The LinkedIn draft also gets a link card built from the item's own title and description.
- Feeds only create drafts. They never choose an account or a time, request approval, schedule or post.
- No backlog. The first successful read records what is already in the feed and makes no drafts. An item it has seen never makes another pair, even if its title changes, and never overwrites your edits.
- Someone reads it first. You, or an agent such as Claude Code through Flaghand's API or MCP, turn the title-and-link draft into a post, choose the account and time, check it and request approval. Only the owner can approve the exact post and time, with a passkey. No agent token can approve, schedule or post.
- Slower by design. An hourly read plus an approval won't beat a two-minute check, and on LinkedIn it posts to personal profiles, not company Pages.
Flaghand sign-up is not open yet, so this is not an account you can create by following this guide today. Join the Flaghand waitlist. The feeds reference documents each call, and the agent documentation explains the approval boundary.
Before you turn any of them on
- Read your feed's titles as posts. "Release notes v2.3.1" is fine in a feed reader and flat on X. Check what an automation will actually send, and that long titles still fit X's 280 characters with the link.
- Give every item a stable GUID. Tools use it, or the URL, to decide what is new. A missing or changing one is how the same article posts twice, or never.
- Start from now. On a first run, choose the option that skips what is already in the feed.
- Budget for links on X. Through X's pay-per-use API a post with a link costs $0.20, against $0.015 without one (see X API pricing). Every RSS post has a link.
- LinkedIn shows the card you send. Its Posts API doesn't scrape a link's page: the tool has to supply the card's title, description and thumbnail. Preview a post in the free LinkedIn post preview or X post preview, no account needed.
- Decide who reads it. If the answer is nobody, watch the first few posts go out and know how to delete one.