RSS to email

What it does

Most sites already publish a feed — a blog's /rss.xml, a changelog, a podcast, a releases page. RSS to email watches that feed and, when something new appears, sends it to the audience you chose as an ordinary campaign: it shows up under Campaigns, it has open and click statistics, it carries the unsubscribe and view-in-browser links, and it counts against your monthly emails like any other send.

You add a feed under Messaging → RSS to email, pick who receives it and how often, and that is it. Nothing goes out when nothing is new.

How a send is decided

• As posts appear — the feed is checked every 15 minutes; anything new is sent at once.
• Daily — sent in the hour you choose (UTC), only if there are new posts since the last send.
• Weekly — the same, on the weekday you choose.

"New" means published since the last send: SendBeam remembers the newest post it sent and takes everything above it in the feed, up to the posts per email limit you set. The very first send takes only the newest few posts, never the whole archive. If a post you sent has since been deleted from the feed, the post dates decide instead.

Send now on the feed's page sends whatever is new straight away; Send latest anyway re-sends the newest posts even if they went out before. Pause stops the checks without deleting anything.

What the email looks like

With no template chosen, the built-in digest layout is used: the feed's title, an optional intro line you write once, then each post as a linked heading, its date, a short plain-text summary and a Read more → link. The subject defaults to the newest post's title; you can write your own with {{item_title}}, {{feed_title}} and {{item_count}}.

To use your own design, save a template that contains the Latest posts block (in the email builder) — or the {{rss_items}} tag in HTML — and pick it on the feed. The posts are dropped in where the block is. A template without the block gets the posts just before the end.

Post text is treated as untrusted: HTML from the feed is reduced to plain text and escaped, and only http(s) links are kept, so a feed can never inject markup into your email.

One feed per site

Each workspace is a site, so each site's blog gets its own feed, its own list and its own sending domain, while the account holds one plan and one bill. An agency running client newsletters sets up one feed per client workspace; a person with four blogs sets up four feeds and forgets about them.