The 25-year-old protocol
that still works.
Every workspace exposes RSS 2.0 feeds at predictable URLs. No setup, no toggle - the moment you publish, the feed updates. Subscribe in any reader, pipe into Zapier / IFTTT / Make, generate Mailchimp digest emails, or embed in another site.
How it works
Three steps,
under five minutes.
- 01
Find the feed URL
Two feeds per workspace: https://<your-slug>.usedrumroll.com/changelog.xml and /guides.xml. Public pages also advertise the feed via <link rel="alternate">, so most readers auto-discover from the page URL.
- 02
Subscribe
Paste the URL into Feedly, Inoreader, NetNewsWire, Reeder, or whichever feed reader you prefer. Or use it as a Zapier / IFTTT / Make trigger.
- 03
Pipe it anywhere
RSS triggers are first-class in every automation platform. Wire it to Mailchimp RSS-to-email, an internal Slack channel via the Slack RSS app, a Notion database row, a tweet thread - whatever your workflow needs.
What syncs
Capabilities & limits.
We’re explicit about what RSS sync handles and what it doesn’t. Most teams find the first list covers their actual use; the second is the part vendors usually hide.
Supported
- RSS 2.0 with Atom self-link (validates clean on feedvalidator.org)
- Per-entry: title, link, GUID, pubDate, full HTML body in CDATA, category tags
- Edge-cached for 10 minutes with stale-while-revalidate
- Auto-discovered via <link rel="alternate" type="application/rss+xml"> on public pages
- No setup, no toggle, no auth - feeds are public, just like the pages they mirror
- Tags on entries and guides become <category> elements
Not yet supported
- Private / draft entries - feeds expose only published content
- Atom 1.0 format (RSS 2.0 only; ~all readers consume both)
- Per-tag filtered feeds (workspace-wide feed only for v1)
- Push notifications via WebSub / PubSubHubbub
Try it on a real project.
Two minutes to sign up, one click to connect, your team’s shipping rhythm becomes a public page. Always free.
Create a workspace