Guides

RSS to social

Auto-post from any feed

Ship a blog post — and have it automatically tweeted, LinkedIn-ed, and threaded. This guide walks through a real setup end to end using an RSS feed as the trigger.

Scenario

Say your company blog lives at example.com/blog and publishes an RSS feed at example.com/rss.xml. You want every new post to:

  • Tweet a punchy one-liner with the link.
  • Post a longer summary to LinkedIn.
  • Create a draft for Instagram (so the designer adds a visual before sending).

1. Build the template

Templates are the bridge between a feed item’s fields and what actually gets posted. Create one at Templates → + New.

http
Title: Blog → social (auto)
Channels: X, LinkedIn, Instagram
 
# X version
New post ↓
 
{{title}}
 
Read → {{url}}
 
# LinkedIn version
{{title}}
 
{{description}}
 
Full write-up: {{url}}
 
# Instagram version (draft — designer adds image)
{{title}}
 
{{description}}
 
Link in bio → {{url}}
The per-channel copy fields in the template are the same feature as per-channel overrides in the composer — they just happen automatically for every feed item.

2. Connect the feed

1

Settings → Integrations → RSS → Add feed

Paste https://example.com/rss.xml. We fetch and show you the last 5 items so you can confirm fields look right.

2

Map the template

Pick the template you just made.

3

Pick per-channel behavior

X + LinkedIn— Queue mode (drops into your normal time slots).

Instagram— Review mode (creates a draft, requires approval).

4

Turn it on

OpenPost polls the feed every 15 minutes. First scheduled post will appear within the next poll window.

3. Test before you trust it

Publish a test blog post — something harmless, maybe a hidden changelog entry. Watch the calendar. Within 15 minutes, you should see three new items: two scheduled (X, LinkedIn), one draft (Instagram).

If your blog platform sends an RSS ping the instant a post goes live, you might see the OpenPost post land before the blog post itself is fully cached behind your CDN. Pad your schedule by 5 minutes on the template if this matters.

4. Handle edge cases

  • Draft posts accidentally published to RSS— set the RSS feed to Review mode for the first week. Approve manually until you trust the pipeline.
  • Re-published edits — if your CMS updates the RSS guid on edit, OpenPost re-posts. Most CMSes don’t do this by default. Check once and disable GUID-regen if needed.
  • Backfilled history— OpenPost only posts items it sees live in the feed. If you switch a feed on and there are already 50 items visible, we won’t retro-post them. Only items that become new after connection.

More feeds worth connecting

  • Your YouTube channel — https://www.youtube.com/feeds/videos.xml?channel_id=UC... auto-posts every new upload.
  • Your podcast— most hosts emit a standard RSS feed with enclosures. OpenPost picks up episode art automatically.
  • A competitor/industry feed— combine with Review mode to surface worth-resharing items in your team’s approval queue.
PreviousMigrate from BufferNext Bulk import from CSV
Last updated April 2026 Edit this page